ecosystem
stringclasses 11
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
220
⌀ | details
stringlengths 34
13.5k
| aliases
stringlengths 17
87
⌀ | modified_date
stringdate 2019-03-26 14:13:00
2022-05-10 08:46:52
| published_date
stringdate 2012-06-17 03:41:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 581
values | refs
stringlengths 82
11.6k
| introduced
stringclasses 843
values | code_refs
stringlengths 46
940
| commits
stringlengths 46
940
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GHSA | GHSA-5xvc-vgmp-jgc3 | Improper Access Control in jupyterhub-firstuseauthenticator | ### Impact
When JupyterHub is used with FirstUseAuthenticator, the vulnerability allows unauthorized access to any user's account if `create_users=True` and the username is known or guessed.
### Patches
Upgrade to jupyterhub-firstuseauthenticator to 1.0, or apply patch https://github.com/jupyterhub/firstuseauthenticator/pull/38.patch
### Workarounds
If you cannot upgrade, there is no complete workaround, but it can be mitigated.
If you cannot upgrade yet, you can disable user creation with `c.FirstUseAuthenticator.create_users = False`, which will only allow login with fully normalized usernames for already existing users prior to jupyterhub-firstuserauthenticator 1.0. If any users have never logged in with their normalized username (i.e. lowercase), they will still be vulnerable until you can patch or upgrade. | {'CVE-2021-41194'} | 2022-03-22T18:08:53Z | 2021-10-28T23:13:57Z | CRITICAL | 9.1 | {'CWE-284'} | {'https://github.com/jupyterhub/firstuseauthenticator/pull/38.patch', 'https://github.com/jupyterhub/firstuseauthenticator/pull/38/commits/32b21898fb2b53b1a2e36270de6854ad70e9e9bf', 'https://github.com/jupyterhub/firstuseauthenticator/pull/38', 'https://github.com/jupyterhub/firstuseauthenticator/security/advisories/GHSA-5xvc-vgmp-jgc3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41194', 'https://github.com/jupyterhub/firstuseauthenticator/pull/38/commits/9e200d974e0cb85d828a6afedb8ab90a37878f28', 'https://github.com/advisories/GHSA-5xvc-vgmp-jgc3'} | null | {'https://github.com/jupyterhub/firstuseauthenticator/pull/38/commits/9e200d974e0cb85d828a6afedb8ab90a37878f28', 'https://github.com/jupyterhub/firstuseauthenticator/pull/38/commits/32b21898fb2b53b1a2e36270de6854ad70e9e9bf'} | {'https://github.com/jupyterhub/firstuseauthenticator/pull/38/commits/9e200d974e0cb85d828a6afedb8ab90a37878f28', 'https://github.com/jupyterhub/firstuseauthenticator/pull/38/commits/32b21898fb2b53b1a2e36270de6854ad70e9e9bf'} |
GHSA | GHSA-q54r-r9pr-w7qv | XSS in Hexo | Hexo versions 0.0.1 to 5.4.0 are vulnerable against stored XSS. The post “body” and “tags” don’t sanitize malicious javascript during web page generation. Local unprivileged attacker can inject arbitrary code. | {'CVE-2021-25987'} | 2021-12-01T18:27:44Z | 2021-12-01T18:27:44Z | MODERATE | 4.6 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25987', 'https://github.com/advisories/GHSA-q54r-r9pr-w7qv', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25987', 'https://github.com/hexojs/hexo/commit/5170df2d3fa9c69e855c4b7c2b084ebfd92d5200'} | null | {'https://github.com/hexojs/hexo/commit/5170df2d3fa9c69e855c4b7c2b084ebfd92d5200'} | {'https://github.com/hexojs/hexo/commit/5170df2d3fa9c69e855c4b7c2b084ebfd92d5200'} |
GHSA | GHSA-qwpp-fgrj-h78q | Exposure of Sensitive Information to an Unauthorized Actor | Shopware is an open source eCommerce platform. Versions prior to 5.6.10 are vulnerable to system information leakage in error handling. Users are recommend to update to version 5.6.10. You can get the update to 5.6.10 regularly via the Auto-Updater or directly via the download overview. | {'CVE-2021-32712'} | 2021-09-08T17:59:46Z | 2021-09-08T17:59:46Z | MODERATE | 5.3 | {'CWE-200'} | {'https://github.com/advisories/GHSA-qwpp-fgrj-h78q', 'https://docs.shopware.com/en/shopware-5-en/security-updates/security-update-05-2021', 'https://github.com/shopware/shopware/security/advisories/GHSA-9vxv-wpv4-f52p', 'https://github.com/shopware/shopware/commit/dcb24eb5ec757c991b5a4e2ddced379e5820744d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32712'} | null | {'https://github.com/shopware/shopware/commit/dcb24eb5ec757c991b5a4e2ddced379e5820744d'} | {'https://github.com/shopware/shopware/commit/dcb24eb5ec757c991b5a4e2ddced379e5820744d'} |
GHSA | GHSA-g4m9-5hpf-hx72 | Firewall configured with unanimous strategy was not actually unanimous in Symfony | Description
-----------
On Symfony before 4.4.0, when a `Firewall` checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only if *all* calls to the `accessDecisionManager` decide to grant access.
As of Symfony 4.4.0, a bug was introduced that prevents the check of attributes as soon as `accessDecisionManager` decide to grant access on one attribute.
Resolution
----------
The `accessDecisionManager` is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf) for the 4.4 branch.
Credits
-------
I would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue. | {'CVE-2020-5275'} | 2022-04-19T19:02:24Z | 2020-03-30T20:09:44Z | HIGH | 7.6 | {'CWE-285'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C36JLPHUPKDFAX6D5WYFC4ALO2K7RDUQ/', 'https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf', 'https://github.com/symfony/symfony/security/advisories/GHSA-g4m9-5hpf-hx72', 'https://github.com/advisories/GHSA-g4m9-5hpf-hx72', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5275'} | null | {'https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf'} | {'https://github.com/symfony/symfony/commit/c935e4a3fba6cc2ab463a6ca382858068d63cebf'} |
GHSA | GHSA-rqwh-c535-j9hw | Downloads Resources over HTTP in js-given | Affected versions of `js-given` 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 `js-given`.
## Recommendation
Update to version 0.0.18 or later. | {'CVE-2016-10638'} | 2021-01-08T01:57:56Z | 2019-02-18T23:47:09Z | HIGH | 0 | {'CWE-311'} | {'https://github.com/jsGiven/jsGiven/commit/92f750739c7b9b6e704e562ad34e2ad148acad64)', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10638', 'https://github.com/advisories/GHSA-rqwh-c535-j9hw', 'https://www.npmjs.com/advisories/241', 'https://nodesecurity.io/advisories/241'} | null | {'https://github.com/jsGiven/jsGiven/commit/92f750739c7b9b6e704e562ad34e2ad148acad64)'} | {'https://github.com/jsGiven/jsGiven/commit/92f750739c7b9b6e704e562ad34e2ad148acad64)'} |
GHSA | GHSA-3p4q-x8f3-p7vq | Moderate severity vulnerability that affects notebook | Jupyter Notebook before 5.7.2 allows XSS via a crafted directory name because notebook/static/tree/js/notebooklist.js handles certain URLs unsafely. | {'CVE-2018-19352'} | 2021-08-31T21:18:00Z | 2018-11-21T22:19:22Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-19352', 'https://pypi.org/project/notebook/#history', 'https://github.com/jupyter/notebook/blob/master/docs/source/changelog.rst', 'https://github.com/jupyter/notebook/commit/288b73e1edbf527740e273fcc69b889460871648', 'https://github.com/advisories/GHSA-3p4q-x8f3-p7vq'} | null | {'https://github.com/jupyter/notebook/commit/288b73e1edbf527740e273fcc69b889460871648'} | {'https://github.com/jupyter/notebook/commit/288b73e1edbf527740e273fcc69b889460871648'} |
GHSA | GHSA-vh6r-g38f-q3w8 | Validation bypass in jpv | jpv (aka Json Pattern Validator) before 2.2.2 does not properly validate input, as demonstrated by a corrupted array. | {'CVE-2020-17479'} | 2021-05-06T17:27:58Z | 2021-05-06T17:27:58Z | CRITICAL | 9.8 | {'CWE-20'} | {'https://blog.sonatype.com/cve-2020-17479', 'https://www.npmjs.com/package/jpv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17479', 'https://github.com/advisories/GHSA-vh6r-g38f-q3w8', 'https://github.com/manvel-khnkoyan/jpv/commit/e3eec1215caa8d5c560f5e88d0943422831927d6', 'https://github.com/manvel-khnkoyan/jpv/issues/10'} | null | {'https://github.com/manvel-khnkoyan/jpv/commit/e3eec1215caa8d5c560f5e88d0943422831927d6'} | {'https://github.com/manvel-khnkoyan/jpv/commit/e3eec1215caa8d5c560f5e88d0943422831927d6'} |
GHSA | GHSA-mwm4-5qwr-g9pf | Keycloak is vulnerable to IDN homograph attack | A flaw was found in keycloak, where IDN homograph attacks are possible. This flaw allows a malicious user to register a name that already exists and then tricking an admin to grant extra privileges. The highest threat from this vulnerability is to integrity. | null | 2022-05-02T22:35:44Z | 2022-04-28T21:00:31Z | LOW | 0 | {'CWE-284'} | {'https://github.com/keycloak/keycloak/security/advisories/GHSA-mwm4-5qwr-g9pf', 'https://github.com/keycloak/keycloak/commit/ac79fd0c23c6947a04073afc61e30d341498438e', 'https://github.com/advisories/GHSA-mwm4-5qwr-g9pf'} | null | {'https://github.com/keycloak/keycloak/commit/ac79fd0c23c6947a04073afc61e30d341498438e'} | {'https://github.com/keycloak/keycloak/commit/ac79fd0c23c6947a04073afc61e30d341498438e'} |
GHSA | GHSA-pw4v-gr34-2553 | Denial of service (via resource exhaustion) due to improper input validation | ### Impact
Missing input validation of some parameters on the endpoints used to confirm third-party identifiers could cause excessive use of disk space and memory leading to resource exhaustion.
### Patches
Fixed by 3175fd3.
### For more information
If you have any questions or comments about this advisory, email us at security@matrix.org. | {'CVE-2021-29433'} | 2021-06-09T22:13:24Z | 2021-04-16T19:53:37Z | MODERATE | 4.3 | {'CWE-20', 'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29433', 'https://github.com/matrix-org/sydent/commit/3175fd358ebc2c310eab7a3dbf296ce2bd54c1da', 'https://pypi.org/project/matrix-sydent/', 'https://github.com/advisories/GHSA-pw4v-gr34-2553', 'https://github.com/matrix-org/sydent/security/advisories/GHSA-pw4v-gr34-2553'} | null | {'https://github.com/matrix-org/sydent/commit/3175fd358ebc2c310eab7a3dbf296ce2bd54c1da'} | {'https://github.com/matrix-org/sydent/commit/3175fd358ebc2c310eab7a3dbf296ce2bd54c1da'} |
GHSA | GHSA-59qh-g7m4-j9m9 | Cross-site Scripting in livehelperchat | Stored XSS attacks exist in new the form creation flow. New forms can be given a title which will render javascript. | {'CVE-2022-0374'} | 2022-02-02T16:05:02Z | 2022-01-28T23:06:12Z | MODERATE | 6.5 | {'CWE-79'} | {'https://github.com/advisories/GHSA-59qh-g7m4-j9m9', 'https://github.com/livehelperchat/livehelperchat/commit/bbfaa26ce54a2a86ce1a42a16496038f5bdfc102', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0374', 'https://huntr.dev/bounties/f8b560a6-aa19-4262-8ae4-cf88204310ef'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/bbfaa26ce54a2a86ce1a42a16496038f5bdfc102'} | {'https://github.com/livehelperchat/livehelperchat/commit/bbfaa26ce54a2a86ce1a42a16496038f5bdfc102'} |
GHSA | GHSA-m5vr-3m74-jwxp | Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS | > ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2)
> * CWE-325, CWE-20, CWE-200, CWE-502
### Problem
It has been discovered that an internal verification mechanism can be used to generate arbitrary checksums. This allows to inject arbitrary data having a valid cryptographic message authentication code (HMAC-SHA1) and can lead to various attack chains as described below.
* [TYPO3-CORE-SA-2020-007](https://typo3.org/security/advisory/typo3-core-sa-2020-007), [CVE-2020-15099](https://nvd.nist.gov/vuln/detail/CVE-2020-15099): Potential Privilege Escalation
+ the database server used for a TYPO3 installation must be accessible for an attacker (either via internet or shared hosting network)
+ `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (7.5, high)
* [TYPO3-CORE-SA-2016-013](https://typo3.org/security/advisory/typo3-core-sa-2016-013), [CVE-2016-5091](https://nvd.nist.gov/vuln/detail/CVE-2016-5091): Insecure Deserialization & Remote Code Execution
+ an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation
+ `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (9.1, critical)
The overall severity of this vulnerability is **high (8.2)** based on mentioned attack chains and the requirement of having a valid backend user session (authenticated).
### Solution
Update to TYPO3 versions 9.5.20 or 10.4.6 that fix the problem described.
### Credits
Thanks to TYPO3 security team member Oliver Hader who reported and fixed the issue.
### References
* [TYPO3-CORE-SA-2020-008](https://typo3.org/security/advisory/typo3-core-sa-2020-008) | {'CVE-2020-15098'} | 2022-04-19T19:02:36Z | 2020-07-29T16:15:19Z | HIGH | 8.8 | {'CWE-325', 'CWE-200', 'CWE-20', 'CWE-327', 'CWE-502'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-5091', 'https://github.com/advisories/GHSA-m5vr-3m74-jwxp', 'https://typo3.org/security/advisory/typo3-core-sa-2020-008', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15098', 'https://github.com/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99ef53f4b561114acfa9e5c47e1', 'https://typo3.org/security/advisory/typo3-core-sa-2016-013', 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-m5vr-3m74-jwxp'} | null | {'https://github.com/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99ef53f4b561114acfa9e5c47e1'} | {'https://github.com/TYPO3/TYPO3.CMS/commit/85d3e70dff35a99ef53f4b561114acfa9e5c47e1'} |
GHSA | GHSA-j3mj-fhpq-qqjj | Reachable Assertion in Tensorflow | ### Impact
When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes.
### Patches
We have patched the issue in GitHub commit [5b491cd5e41ad63735161cec9c2a568172c8b6a3](https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2022-23571'} | 2022-02-11T20:48:17Z | 2022-02-09T23:28:57Z | MODERATE | 6.5 | {'CWE-617'} | {'https://github.com/advisories/GHSA-j3mj-fhpq-qqjj', 'https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23571', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j3mj-fhpq-qqjj'} | null | {'https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3'} | {'https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3'} |
GHSA | GHSA-p3w6-jcg4-52xh | High severity vulnerability that affects django-rest-registration | ## Misusing the Django Signer API leads to predictable signatures used in verification emails
### Impact
The vulnerability is a high severity one. Anyone using Django REST Registration library versions `0.2.*` - `0.4.*` with e-mail verification option (which is recommended, but needs [additional configuration](https://django-rest-registration.readthedocs.io/en/latest/quickstart.html#preferred-configuration)) is affected.
In the worst case, the attacker can take over any Django user by resetting his/her password without even receiving the reset password verification link, just by guessing the signature from publicly available data (more detailed description below).
### Patches
The problem has been patched in version `0.5.0`. All library users should upgrade to version `0.5.0` or higher.
The fix will invalidate all previously generated signatures , and in consequence, all verification links in previously sent verification e-mails. Therefore semi-major version `0.5.0` was released instead of version `0.4.6` to mark that incompatibility.
### Workarounds
The easiest way way is to disable the verification options by using something like the minimal configuration described [here](https://django-rest-registration.readthedocs.io/en/latest/quickstart.html#minimal-configuration). This will unfortunately disable checking whether the given e-mail is valid and make unable to users who registered an account but didn't verify it before config change.
Less harsh way is to temporarily disable just the the reset password functionality:
```python
REST_REGISTRATION = {
# ...
'RESET_PASSWORD_VERIFICATION_ENABLED': False,
# ...
}
```
Which should disallow the worst case, which is account takeover by an attacker. The attacker can still use the register-email endpoint to change the email to its own (but it is less critical than resetting the password in this case).
If one already set `'RESET_PASSWORD_VERIFICATION_ONE_TIME_USE'` setting key to `True` in `REST_REGISTRATION` Django setting (which is not the default setting) then it should mitigate the security issue in case of password reset (in this case, the signature is much harder to guess by the attacker). But even in this case upgrade to newest version is highly recommended.
### Technical description
After the code [was refactored](https://github.com/apragacz/django-rest-registration/commit/b6d921e9decc9bb36a4c6d58bc607471aa824a2e) to use the [official Signer class](https://docs.djangoproject.com/en/dev/topics/signing/) the salt
was passed wrongly as secret key, replacing the `SECRET_KEY` set in
Django settings file. This leads to the Django `SECRET_KEY` not being used by the signer object. The secret key of the signer ends to be the salt which in most cases is a static string which is publicly available.
In consequence this allows, with verification enabled, to guess
the signature contained in the verification link (which is sent in a verification e-mail) by a potential attacker very easily.
The bug went unnoticed for very long time so multiple versions are affected:
this bug affects versions `0.2.*`, `0.3.*`, `0.4.*`; version `0.1.*` is not affected.
Recently released version `0.5.0` contains the [fix](https://github.com/apragacz/django-rest-registration/commit/26d094fab65ea8c2694fdfb6a3ab95a7808b62d5) which correctly passes the salt to the Signer constructor as keyword argument instead as a positonal argument. It also contains additonal test so this problem should not reappear in the future.
### Thanks
I'd like to thank @peterthomassen from https://desec.io DNS security project for finding the bug. I'd like also to thank his employer, SSE (https://www.securesystems.de) for funding his work.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [GitHub issues project page](https://github.com/apragacz/django-rest-registration/issues)
* Email @apragacz, author of the library | {'CVE-2019-13177'} | 2022-03-21T21:29:00Z | 2019-07-02T15:43:41Z | CRITICAL | 9.8 | {'CWE-347'} | {'https://github.com/apragacz/django-rest-registration/security/advisories/GHSA-p3w6-jcg4-52xh', 'https://nvd.nist.gov/vuln/detail/CVE-2019-13177', 'https://github.com/advisories/GHSA-p3w6-jcg4-52xh', 'https://github.com/apragacz/django-rest-registration/commit/26d094fab65ea8c2694fdfb6a3ab95a7808b62d5', 'https://github.com/apragacz/django-rest-registration/releases/tag/0.5.0'} | null | {'https://github.com/apragacz/django-rest-registration/commit/26d094fab65ea8c2694fdfb6a3ab95a7808b62d5'} | {'https://github.com/apragacz/django-rest-registration/commit/26d094fab65ea8c2694fdfb6a3ab95a7808b62d5'} |
GHSA | GHSA-q44r-f2hm-v76v | Moderate severity vulnerability that affects puppet | lib/puppet/ssl/certificate_authority.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, does not properly restrict the characters in the Common Name field of a Certificate Signing Request (CSR), which makes it easier for user-assisted remote attackers to trick administrators into signing a crafted agent certificate via ANSI control sequences. | {'CVE-2012-3867'} | 2021-09-16T19:28:09Z | 2017-10-24T18:33:37Z | MODERATE | 0 | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=839158', 'http://www.debian.org/security/2012/dsa-2511', 'https://github.com/advisories/GHSA-q44r-f2hm-v76v', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3867', 'http://www.ubuntu.com/usn/USN-1506-1', 'http://puppetlabs.com/security/cve/cve-2012-3867/', 'http://lists.opensuse.org/opensuse-security-announce/2012-08/msg00006.html', 'https://github.com/puppetlabs/puppet/commit/dfedaa5fa841ccf335245a748b347b7c7c236640', 'http://secunia.com/advisories/50014', 'http://lists.opensuse.org/opensuse-updates/2012-07/msg00036.html', 'https://github.com/puppetlabs/puppet/commit/f3419620b42080dad3b0be14470b20a972f13c50'} | null | {'https://github.com/puppetlabs/puppet/commit/f3419620b42080dad3b0be14470b20a972f13c50', 'https://github.com/puppetlabs/puppet/commit/dfedaa5fa841ccf335245a748b347b7c7c236640'} | {'https://github.com/puppetlabs/puppet/commit/f3419620b42080dad3b0be14470b20a972f13c50', 'https://github.com/puppetlabs/puppet/commit/dfedaa5fa841ccf335245a748b347b7c7c236640'} |
GHSA | GHSA-pp57-mqmh-44h7 | Command Injection in macaddress | All versions of `macaddress` are vulnerable to command injection. For this vulnerability to be exploited an attacker needs to control the `iface` argument to the `one` method.
## Recommendation
Update to version 0.2.9 or later. | {'CVE-2018-13797'} | 2021-09-16T18:18:03Z | 2018-09-06T23:24:21Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-13797', 'https://www.npmjs.com/advisories/654', 'https://github.com/advisories/GHSA-pp57-mqmh-44h7', 'https://github.com/scravy/node-macaddress/pull/20', 'https://news.ycombinator.com/item?id=17283394', 'https://github.com/scravy/node-macaddress/commit/358fd594adb196a86b94ac9c691f69fe5dad2332', 'https://github.com/scravy/node-macaddress/releases/tag/0.2.9', 'https://hackerone.com/reports/319467', 'https://github.com/scravy/node-macaddress/pull/20/'} | null | {'https://github.com/scravy/node-macaddress/commit/358fd594adb196a86b94ac9c691f69fe5dad2332'} | {'https://github.com/scravy/node-macaddress/commit/358fd594adb196a86b94ac9c691f69fe5dad2332'} |
GHSA | GHSA-92vm-wfm5-mxvv | Timing Attack in cookie-signature | Affected versions of `cookie-signature` are vulnerable to timing attacks as a result of using a fail-early comparison instead of a constant-time comparison.
Timing attacks remove the exponential increase in entropy gained from increased secret length, by providing per-character feedback on the correctness of a guess via miniscule timing differences.
Under favorable network conditions, an attacker can exploit this to guess the secret in no more than `charset*length` guesses, instead of `charset^length` guesses required were the timing attack not present.
## Recommendation
Update to 1.0.6 or later. | {'CVE-2016-1000236'} | 2021-08-19T16:17:01Z | 2020-01-06T18:44:10Z | MODERATE | 4.4 | {'CWE-362'} | {'https://travis-ci.com/nodejs/security-wg/builds/76423102', 'https://www.npmjs.com/advisories/134', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000236', 'https://security-tracker.debian.org/tracker/CVE-2016-1000236', 'https://www.mail-archive.com/secure-testing-team@lists.alioth.debian.org/msg06583.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2016-1000236', 'https://github.com/tj/node-cookie-signature/commit/4cc5e21e7f59a4ea0b51cd5e9634772d48fab590', 'https://github.com/tj/node-cookie-signature/commit/2c4df6b6cee540f30876198cd0b5bebf28528c07', 'https://bugzilla.redhat.com/show_bug.cgi?id=1371409', 'https://github.com/tj/node-cookie-signature/commit/39791081692e9e14aa62855369e1c7f80fbfd50e', 'https://github.com/advisories/GHSA-92vm-wfm5-mxvv', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838618'} | null | {'https://github.com/tj/node-cookie-signature/commit/4cc5e21e7f59a4ea0b51cd5e9634772d48fab590', 'https://github.com/tj/node-cookie-signature/commit/39791081692e9e14aa62855369e1c7f80fbfd50e', 'https://github.com/tj/node-cookie-signature/commit/2c4df6b6cee540f30876198cd0b5bebf28528c07'} | {'https://github.com/tj/node-cookie-signature/commit/4cc5e21e7f59a4ea0b51cd5e9634772d48fab590', 'https://github.com/tj/node-cookie-signature/commit/39791081692e9e14aa62855369e1c7f80fbfd50e', 'https://github.com/tj/node-cookie-signature/commit/2c4df6b6cee540f30876198cd0b5bebf28528c07'} |
GHSA | GHSA-85g2-29m8-qf2p | Prototype Pollution Vulnerability in object-collider | Prototype pollution vulnerability in 'object-collider' versions 1.0.0 through 1.0.3 allows attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25914'} | 2021-03-19T21:18:33Z | 2021-03-19T21:18:33Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25914', 'https://github.com/advisories/GHSA-85g2-29m8-qf2p', 'https://github.com/FireBlinkLTD/object-collider/commit/321f75a7f8e7b3393e5b7dd6dd9ab26ede5906e5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25914'} | null | {'https://github.com/FireBlinkLTD/object-collider/commit/321f75a7f8e7b3393e5b7dd6dd9ab26ede5906e5'} | {'https://github.com/FireBlinkLTD/object-collider/commit/321f75a7f8e7b3393e5b7dd6dd9ab26ede5906e5'} |
GHSA | GHSA-vrmr-f2qh-3hhf | Improper use of cryptographic key in wal-g | WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to encrypt all file activity." | {'CVE-2021-38599'} | 2021-09-02T17:17:16Z | 2021-09-02T17:17:16Z | HIGH | 7.5 | {'CWE-922'} | {'https://github.com/wal-g/wal-g/pull/1062', 'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3', 'https://github.com/advisories/GHSA-vrmr-f2qh-3hhf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38599', 'https://github.com/wal-g/wal-g/releases/tag/v1.1'} | null | {'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3'} | {'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3'} |
GHSA | GHSA-g6j2-ch25-5mmv | Missing Token Replay Detection in Saml2 Authentication services for ASP.NET | ### Impact
Token Replay Detection is an important defence in depth measure for Single Sign On solutions. In all previous 2.X versions, the Token Replay Detection is not properly implemented.
Note that version 1.0.1 is not affected. It has a correct Token Replay Implementation and is safe to use.
### Patches
The 2.5.0 version is patched.
### Workarounds
There are no workarounds with existing versions. Fixing the issue requires code updates.
### References
https://en.wikipedia.org/wiki/Replay_attack
### For more information
If you have any questions or comments about this advisory:
* Comment on #711.
* Email us at [security@sustainsys.com](mailto:security@susatinsys.com) if you think that there are further security issues. | {'CVE-2020-5261'} | 2021-01-08T20:24:59Z | 2020-03-25T16:52:49Z | HIGH | 8.2 | {'CWE-294'} | {'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5261', 'https://github.com/Sustainsys/Saml2/security/advisories/GHSA-g6j2-ch25-5mmv', 'https://github.com/advisories/GHSA-g6j2-ch25-5mmv', 'https://github.com/Sustainsys/Saml2/issues/711'} | null | {'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241'} | {'https://github.com/Sustainsys/Saml2/commit/e58e0a1aff2b1ead6aca080b7cdced55ee6d5241'} |
GHSA | GHSA-8q59-q68h-6hv4 | Improper Input Validation in PyYAML | A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747. | {'CVE-2020-14343'} | 2022-04-22T18:26:17Z | 2021-03-25T21:26:26Z | CRITICAL | 9.8 | {'CWE-20'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14343', 'https://github.com/advisories/GHSA-8q59-q68h-6hv4', 'https://pypi.org/project/PyYAML/', 'https://github.com/yaml/pyyaml/commit/a001f2782501ad2d24986959f0239a354675f9dc', 'https://github.com/yaml/pyyaml/issues/420#issuecomment-663673966', 'https://bugzilla.redhat.com/show_bug.cgi?id=1860466'} | null | {'https://github.com/yaml/pyyaml/commit/a001f2782501ad2d24986959f0239a354675f9dc'} | {'https://github.com/yaml/pyyaml/commit/a001f2782501ad2d24986959f0239a354675f9dc'} |
GHSA | GHSA-8ch4-58qp-g3mp | Observable Timing Discrepancy in aaugustin websockets library | The aaugustin websockets library before 9.1 for Python has an Observable Timing Discrepancy on servers when HTTP Basic Authentication is enabled with basic_auth_protocol_factory(credentials=...). An attacker may be able to guess a password via a timing attack. | {'CVE-2021-33880'} | 2022-04-22T15:47:44Z | 2021-06-11T17:43:14Z | MODERATE | 5.9 | {'CWE-208', 'CWE-203'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/aaugustin/websockets/commit/547a26b685d08cac0aa64e5e65f7867ac0ea9bc0', 'https://github.com/advisories/GHSA-8ch4-58qp-g3mp', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33880'} | null | {'https://github.com/aaugustin/websockets/commit/547a26b685d08cac0aa64e5e65f7867ac0ea9bc0'} | {'https://github.com/aaugustin/websockets/commit/547a26b685d08cac0aa64e5e65f7867ac0ea9bc0'} |
GHSA | GHSA-668q-qrv7-99fm | Deserialization of Untrusted Data in logback | In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers. | {'CVE-2021-42550'} | 2022-03-28T19:32:57Z | 2021-12-17T20:00:50Z | MODERATE | 6.6 | {'CWE-502'} | {'https://github.com/qos-ch/logback/commit/ef4fc4186b74b45ce80d86833820106ff27edd42', 'https://github.com/qos-ch/logback/blob/1502cba4c1dfd135b2e715bc0cf80c0045d4d128/logback-site/src/site/pages/news.html', 'https://jira.qos.ch/browse/LOGBACK-1591', 'https://github.com/cn-panda/logbackRceDemo', 'https://github.com/qos-ch/logback/commit/87291079a1de9369ac67e20dc70a8fdc7cc4359c', 'https://github.com/advisories/GHSA-668q-qrv7-99fm', 'http://logback.qos.ch/news.html', 'https://security.netapp.com/advisory/ntap-20211229-0001/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42550'} | null | {'https://github.com/qos-ch/logback/commit/87291079a1de9369ac67e20dc70a8fdc7cc4359c', 'https://github.com/qos-ch/logback/commit/ef4fc4186b74b45ce80d86833820106ff27edd42'} | {'https://github.com/qos-ch/logback/commit/ef4fc4186b74b45ce80d86833820106ff27edd42', 'https://github.com/qos-ch/logback/commit/87291079a1de9369ac67e20dc70a8fdc7cc4359c'} |
GHSA | GHSA-2v82-5746-vwqc | XSS in doc_link | ### Impact
Users of MySQL, MariaDB, PgSQL and SQLite are affected. XSS is in most cases prevented by strict CSP in all modern browsers. The only exception is when Adminer is using a `pdo_` extension to communicate with the database (it is used if the native extensions are not enabled). In browsers without CSP, Adminer versions 4.6.1 to 4.8.0 are affected.
### Patches
Patched by 4043092, included in version [4.8.1](https://github.com/vrana/adminer/releases/tag/v4.8.1).
### Workarounds
Do both:
* Use browser supporting strict CSP.
* Enable the native PHP extensions (e.g. `mysqli`) or disable displaying PHP errors (`display_errors`).
### References
https://sourceforge.net/p/adminer/bugs-and-features/797/
### For more information
If you have any questions or comments about this advisory:
* Comment at 4043092.
| {'CVE-2021-29625'} | 2022-03-21T20:33:37Z | 2022-03-18T17:49:28Z | HIGH | 7.5 | {'CWE-79'} | {'https://github.com/vrana/adminer/security/advisories/GHSA-2v82-5746-vwqc', 'https://packagist.org/packages/vrana/adminer', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29625', 'https://github.com/vrana/adminer/commit/4043092ec2c0de2258d60a99d0c5958637d051a7', 'https://github.com/advisories/GHSA-2v82-5746-vwqc', 'https://sourceforge.net/p/adminer/bugs-and-features/797/'} | null | {'https://github.com/vrana/adminer/commit/4043092ec2c0de2258d60a99d0c5958637d051a7'} | {'https://github.com/vrana/adminer/commit/4043092ec2c0de2258d60a99d0c5958637d051a7'} |
GHSA | GHSA-r8j5-h5cx-65gg | ReDOS in IS-SVG | A vulnerability was discovered in IS-SVG version 4.3.1 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string. | {'CVE-2021-29059'} | 2021-12-10T19:02:37Z | 2021-12-10T19:02:37Z | HIGH | 7.5 | {'CWE-770'} | {'https://github.com/advisories/GHSA-r8j5-h5cx-65gg', 'https://github.com/sindresorhus/is-svg/commit/732fc72779840c45a30817d3fe28e12058592b02', 'https://github.com/yetingli/PoCs/blob/main/CVE-2021-29059/IS-SVG.md', 'https://github.com/yetingli/SaveResults/blob/main/js/is-svg.js', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29059', 'https://github.com/sindresorhus/is-svg/releases/tag/v4.3.0', 'https://www.npmjs.com/package/is-svg'} | null | {'https://github.com/sindresorhus/is-svg/commit/732fc72779840c45a30817d3fe28e12058592b02'} | {'https://github.com/sindresorhus/is-svg/commit/732fc72779840c45a30817d3fe28e12058592b02'} |
GHSA | GHSA-3pc2-fm7p-q2vg | Cross-site Scripting in October | ### Impact
Pasting content copied from malicious websites into the Froala richeditor could result in a successful self-XSS attack.
### Patches
Issue has been patched in Build 467 (v1.0.467).
### Workarounds
Apply https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5 to your installation manually if unable to upgrade to Build 467.
### References
- https://research.securitum.com/the-curious-case-of-copy-paste/
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat Assessment
Assessed as Low given that by the nature of the attack it can only impact users that do it to themselves by copying and pasting from malicious websites.
### Acknowledgements
Thanks to [Michał Bentkowski of Securitum](https://research.securitum.com/authors/michal-bentkowski/) for finding the original issue in Froala and @tomaszstrojny for reporting the issue to the October CMS team. | {'CVE-2020-4061'} | 2022-04-19T19:02:29Z | 2020-07-02T16:55:11Z | LOW | 3.7 | {'CWE-79'} | {'https://research.securitum.com/the-curious-case-of-copy-paste/', 'https://github.com/octobercms/october/security/advisories/GHSA-3pc2-fm7p-q2vg', 'https://github.com/advisories/GHSA-3pc2-fm7p-q2vg', 'https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4061'} | null | {'https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5'} | {'https://github.com/octobercms/october/commit/b384954a29b89117e1c0d6035b3ede4f46df67c5'} |
GHSA | GHSA-74r6-grj9-8rq6 | Remote Code Execution in AjaxNetProfessional | All versions of package ajaxpro.2 are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary .NET classes, which can be abused to gain remote code execution. | {'CVE-2021-23758'} | 2021-12-16T15:27:55Z | 2021-12-16T15:27:55Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23758', 'https://snyk.io/vuln/SNYK-DOTNET-AJAXPRO2-1925971', 'https://github.com/advisories/GHSA-74r6-grj9-8rq6', 'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/b0e63be5f0bb20dfce507cb8a1a9568f6e73de57', 'https://github.com/michaelschwarz/Ajax.NET-Professional/security/advisories/GHSA-6r7c-6w96-8pvw'} | null | {'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/b0e63be5f0bb20dfce507cb8a1a9568f6e73de57'} | {'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/b0e63be5f0bb20dfce507cb8a1a9568f6e73de57'} |
GHSA | GHSA-h77x-m5q8-c29h | Moderate severity vulnerability that affects rack | lib/rack/multipart.rb in Rack before 1.1.4, 1.2.x before 1.2.6, 1.3.x before 1.3.7, and 1.4.x before 1.4.2 uses an incorrect regular expression, which allows remote attackers to cause a denial of service (infinite loop) via a crafted Content-Disposion header. | {'CVE-2012-6109'} | 2021-09-14T15:39:43Z | 2017-10-24T18:33:37Z | MODERATE | 0 | {'CWE-835'} | {'https://github.com/rack/rack/commit/c9f65df37a151821eb88ddd1dc404b83e52c52d5', 'http://rhn.redhat.com/errata/RHSA-2013-0544.html', 'http://rhn.redhat.com/errata/RHSA-2013-0548.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=895277', 'http://rack.github.com/', 'https://github.com/rack/rack/blob/master/README.rdoc', 'https://github.com/advisories/GHSA-h77x-m5q8-c29h', 'https://groups.google.com/forum/#!msg/rack-devel/1w4_fWEgTdI/XAkSNHjtdTsJ', 'https://nvd.nist.gov/vuln/detail/CVE-2012-6109'} | null | {'https://github.com/rack/rack/commit/c9f65df37a151821eb88ddd1dc404b83e52c52d5'} | {'https://github.com/rack/rack/commit/c9f65df37a151821eb88ddd1dc404b83e52c52d5'} |
GHSA | GHSA-59cj-99cw-rq64 | 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-0914, 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-0913'} | 2021-03-29T21:00:05Z | 2021-03-29T21:00:05Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0913', 'https://github.com/advisories/GHSA-59cj-99cw-rq64', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0913', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f'} | null | {'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f'} |
GHSA | GHSA-vcg8-98q8-g7mj | Exposure of Sensitive Information to an Unauthorized Actor and Insecure Temporary File in Ansible | A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable. | {'CVE-2020-1740'} | 2021-08-31T21:11:03Z | 2021-04-07T21:47:31Z | LOW | 4.7 | {'CWE-200', 'CWE-377'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1740', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MRRYUU5ZBLPBXCYG6CFP35D64NP2UB2S/', 'https://security.gentoo.org/glsa/202006-11', 'https://github.com/ansible/ansible/issues/67798', 'https://github.com/advisories/GHSA-vcg8-98q8-g7mj', 'https://lists.debian.org/debian-lts-announce/2020/05/msg00005.html', 'https://github.com/ansible/ansible/commit/28f9fbdb5e281976e33f443193047068afb97a9b', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WQVOQD4VAIXXTVQAJKTN7NUGTJFE2PCB/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1740', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DKPA4KC3OJSUFASUYMG66HKJE7ADNGFW/'} | null | {'https://github.com/ansible/ansible/commit/28f9fbdb5e281976e33f443193047068afb97a9b'} | {'https://github.com/ansible/ansible/commit/28f9fbdb5e281976e33f443193047068afb97a9b'} |
GHSA | GHSA-6pcc-3rfx-4gpm | Dom4j contains a XML Injection vulnerability | dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
Note: This advisory applies to `dom4j:dom4j` version 1.x legacy artifacts. To resolve this a change to the latest version of `org.dom4j:dom4j` is recommended. | {'CVE-2018-1000632'} | 2022-04-26T18:43:59Z | 2018-10-16T17:01:25Z | HIGH | 7.5 | {'CWE-91'} | {'https://lists.apache.org/thread.html/7e9e78f0e4288fac6591992836d2a80d4df19161e54bd71ab4b8e458@%3Cdev.maven.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://access.redhat.com/errata/RHSA-2019:1162', 'https://github.com/dom4j/dom4j/commit/e598eb43d418744c4dbf62f647dd2381c9ce9387', 'https://github.com/advisories/GHSA-6pcc-3rfx-4gpm', 'https://access.redhat.com/errata/RHSA-2019:1160', 'https://access.redhat.com/errata/RHSA-2019:0380', 'https://access.redhat.com/errata/RHSA-2019:1159', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/7f6e120e6ed473f4e00dde4c398fc6698eb383bd7857d20513e989ce@%3Cdev.maven.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IOOVVCRQE6ATFD2JM2EMDXOQXTRIVZGP/', 'https://lists.apache.org/thread.html/708d94141126eac03011144a971a6411fcac16d9c248d1d535a39451@%3Csolr-user.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/9d4c1af6f702c3d6d6f229de57112ddccac8ce44446a01b7937ab9e0@%3Ccommits.maven.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KJULAHVR3I5SX7OSMXAG75IMNSAYOXGA/', 'https://security.netapp.com/advisory/ntap-20190530-0001/', 'https://access.redhat.com/errata/RHSA-2019:1161', 'https://lists.apache.org/thread.html/d7d960b2778e35ec9b4d40c8efd468c7ce7163bcf6489b633491c89f@%3Cdev.maven.apache.org%3E', 'https://github.com/dom4j/dom4j/issues/48', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/5a020ecaa3c701f408f612f7ba2ee37a021644c4a39da2079ed3ddbc@%3Ccommits.maven.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://access.redhat.com/errata/RHSA-2019:0364', 'https://github.com/dom4j/dom4j/commit/c2a99d7dee8ce7a4e5bef134bb781a6672bd8a0f', 'https://lists.apache.org/thread.html/4a77652531d62299a30815cf5f233af183425db8e3c9a824a814e768@%3Cdev.maven.apache.org%3E', 'https://ihacktoprotect.com/post/dom4j-xml-injection/', 'https://lists.apache.org/thread.html/rb1b990d7920ae0d50da5109b73b92bab736d46c9788dd4b135cb1a51@%3Cnotifications.freemarker.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:0365', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000632', 'https://lists.debian.org/debian-lts-announce/2018/09/msg00028.html', 'https://access.redhat.com/errata/RHSA-2019:0362', 'https://access.redhat.com/errata/RHSA-2019:3172', 'https://lists.apache.org/thread.html/00571f362a7a2470fba50a31282c65637c40d2e21ebe6ee535a4ed74@%3Ccommits.maven.apache.org%3E'} | null | {'https://github.com/dom4j/dom4j/commit/c2a99d7dee8ce7a4e5bef134bb781a6672bd8a0f', 'https://github.com/dom4j/dom4j/commit/e598eb43d418744c4dbf62f647dd2381c9ce9387'} | {'https://github.com/dom4j/dom4j/commit/e598eb43d418744c4dbf62f647dd2381c9ce9387', 'https://github.com/dom4j/dom4j/commit/c2a99d7dee8ce7a4e5bef134bb781a6672bd8a0f'} |
GHSA | GHSA-h385-52j6-9984 | Withdrawn: HTTP Request Smuggling in Agoo | # Withdrawn reason
Withdrawn on 1/13/2021 due to [this comment from the maintainer](https://github.com/ohler55/agoo/issues/88#issuecomment-723580783). This is no longer considered a vulnerability.
# Original description
agoo through 2.12.3 allows request smuggling attacks where agoo is used as a backend and a frontend proxy also being vulnerable. It is possible to conduct HTTP request smuggling attacks by sending the Content-Length header twice. Furthermore, invalid Transfer Encoding headers were found to be parsed as valid which could be leveraged for TE:CL smuggling attacks. | {'CVE-2020-7670'} | 2021-01-13T19:26:13Z | 2020-10-20T19:15:38Z | MODERATE | 0 | {'CWE-444'} | {'https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130', 'https://github.com/ohler55/agoo/issues/88', 'https://github.com/advisories/GHSA-h385-52j6-9984', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7670', 'https://snyk.io/vuln/SNYK-RUBY-AGOO-569137'} | null | {'https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130'} | {'https://github.com/ohler55/agoo/commit/23d03535cf7b50d679a60a953a0cae9519a4a130'} |
GHSA | GHSA-p94w-42g3-f7h4 | Holder can (re)create authentic credentials after receiving a credential in vp-toolkit | ### Impact
The [`verifyVerifiableCredential()`](https://github.com/rabobank-blockchain/vp-toolkit/blob/master/src/service/signers/verifiable-credential-signer.ts#L57) method check the cryptographic integrity of the Verifiable Credential, but it does not check if the [`credential.issuer`](https://github.com/rabobank-blockchain/vp-toolkit-models/blob/develop/src/model/verifiable-credential.ts#L129) DID matches the signer of the credential.
The **verifier** is impacted by this vulnerability.
### Patches
Patch will be available in version 0.2.2.
### Workarounds
In case you trust certain issuers for certain credentials as a verifier, trust the issuer's public key from the `credential.proof.verificationMethod` field.
### References
[Github issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)
### For more information
If you have any questions or comments about this advisory:
* Discuss in the existing [issue](https://github.com/rabobank-blockchain/vp-toolkit/issues/13)
* [Contact me](https://github.com/rabomarnix) | null | 2020-03-06T01:16:00Z | 2020-03-06T01:16:00Z | HIGH | 0 | null | {'https://github.com/advisories/GHSA-p94w-42g3-f7h4', 'https://github.com/rabobank-blockchain/vp-toolkit/commit/6315936d1d7913fd116fa51a0dbbd29d82c0ce17', 'https://github.com/rabobank-blockchain/vp-toolkit/security/advisories/GHSA-p94w-42g3-f7h4', 'https://github.com/rabobank-blockchain/vp-toolkit/issues/13'} | null | {'https://github.com/rabobank-blockchain/vp-toolkit/commit/6315936d1d7913fd116fa51a0dbbd29d82c0ce17'} | {'https://github.com/rabobank-blockchain/vp-toolkit/commit/6315936d1d7913fd116fa51a0dbbd29d82c0ce17'} |
GHSA | GHSA-m8qc-mf6p-pfq9 | Link Following in rply | python-rply before 0.7.4 insecurely creates temporary files. | {'CVE-2014-1938'} | 2021-08-19T21:52:46Z | 2020-03-11T20:56:34Z | MODERATE | 5.5 | {'CWE-59'} | {'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737627', 'https://nvd.nist.gov/vuln/detail/CVE-2014-1938', 'https://github.com/advisories/GHSA-m8qc-mf6p-pfq9', 'http://www.openwall.com/lists/oss-security/2014/02/11/1', 'https://github.com/alex/rply/commit/76d268a38c627bf4aebebcd064f5b6d380eb8b20', 'https://security-tracker.debian.org/tracker/CVE-2014-1938', 'https://github.com/alex/rply/issues/42'} | null | {'https://github.com/alex/rply/commit/76d268a38c627bf4aebebcd064f5b6d380eb8b20'} | {'https://github.com/alex/rply/commit/76d268a38c627bf4aebebcd064f5b6d380eb8b20'} |
GHSA | GHSA-f7xw-46vh-5jw2 | livehelperchat is vulnerable to Cross-site Scripting | livehelperchat is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-4132'} | 2022-01-05T20:33:47Z | 2022-01-05T20:33:47Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/7eb80e7c-bb7a-478d-9760-0ea2fa9dc0c2', 'https://github.com/advisories/GHSA-f7xw-46vh-5jw2', 'https://github.com/livehelperchat/livehelperchat/commit/55b1e3bf62c564db7c919f5293ec1e755c2958d6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4132'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/55b1e3bf62c564db7c919f5293ec1e755c2958d6'} | {'https://github.com/livehelperchat/livehelperchat/commit/55b1e3bf62c564db7c919f5293ec1e755c2958d6'} |
GHSA | GHSA-gx6h-936c-vrrr | Cross site scripting in registration template in xwiki-platform | ### Impact
We found a possible XSS vector in the `registerinline.vm` template related to the `xredirect` hidden field.
This template is only used in the following conditions:
- the wiki must be open to registration for anyone
- the wiki must be closed to view for Guest users (more specifically the XWiki.Registration page must be forbidden in View for guest user)
A way to obtain the second condition is when administrators checked the "Prevent unregistered users from viewing pages, regardless of the page rights" box in the administration rights.
### Patches
The issue is patched in versions 12.10.11, 14.0-rc-1, 13.4.7, 13.10.3.
### Workarounds
There are two main ways for protecting against this vulnerability, the easiest and the best one is by applying a patch in the `registerinline.vm` template, the patch consists in checking the value of the xredirect field to ensure it matches the following:
```
<input type="hidden" name="xredirect" value="$escapetool.xml($!request.xredirect)" />
```
If for some reason it's not possible to patch this file, another workaround is to ensure "Prevent unregistered users from viewing pages, regardless of the page rights" is not checked in the rights and apply a better right scheme using groups and rights on spaces.
### References
https://jira.xwiki.org/browse/XWIKI-19291
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Jira XWiki](https://jira.xwiki.org)
* Email us at [security mailing list](mailto:security@xwiki.org)
| {'CVE-2022-23622'} | 2022-02-11T15:00:09Z | 2022-02-09T23:25:44Z | HIGH | 7.4 | {'CWE-79'} | {'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-gx6h-936c-vrrr', 'https://github.com/xwiki/xwiki-platform/commit/053d957d53f2a543d158f3ab651e390d2728e0b9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23622', 'https://github.com/advisories/GHSA-gx6h-936c-vrrr', 'https://jira.xwiki.org/browse/XWIKI-19291'} | null | {'https://github.com/xwiki/xwiki-platform/commit/053d957d53f2a543d158f3ab651e390d2728e0b9'} | {'https://github.com/xwiki/xwiki-platform/commit/053d957d53f2a543d158f3ab651e390d2728e0b9'} |
GHSA | GHSA-8c5p-4362-9333 | Path traversal in grav | grav is vulnerable to Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | {'CVE-2021-3924'} | 2021-11-10T16:48:15Z | 2021-11-10T16:48:15Z | HIGH | 8.8 | {'CWE-22'} | {'https://huntr.dev/bounties/7ca13522-d0c9-4eff-a7dd-6fd1a7f205a2', 'https://github.com/advisories/GHSA-8c5p-4362-9333', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3924', 'https://github.com/getgrav/grav/commit/8f9c417c04b89dc8d2de60b95e7696821b2826ce'} | null | {'https://github.com/getgrav/grav/commit/8f9c417c04b89dc8d2de60b95e7696821b2826ce'} | {'https://github.com/getgrav/grav/commit/8f9c417c04b89dc8d2de60b95e7696821b2826ce'} |
GHSA | GHSA-4wv4-mgfq-598v | Code injection in nobelprizeparser | Code injection through use of eval. | null | 2021-03-12T23:00:19Z | 2021-03-12T23:00:19Z | CRITICAL | 0 | {'CWE-94'} | {'https://www.npmjs.com/package/nobelprizeparser', 'https://github.com/AnneTheDev/nobelprize/security/advisories/GHSA-4wv4-mgfq-598v', 'https://github.com/advisories/GHSA-4wv4-mgfq-598v', 'https://github.com/AnneTheDev/nobelprize/commit/00639d375b0efd097bc1eca18d9dc021691b9286'} | null | {'https://github.com/AnneTheDev/nobelprize/commit/00639d375b0efd097bc1eca18d9dc021691b9286'} | {'https://github.com/AnneTheDev/nobelprize/commit/00639d375b0efd097bc1eca18d9dc021691b9286'} |
GHSA | GHSA-r82c-j4mq-5xfw | Update bitlyshortener to >=0.5.0 to prevent generating some invalid short URLs | ### Impact
Due to a sudden upstream breaking change by Bitly, versions of `bitlyshortener` <0.5.0 can generate an invalid short URL when a vanity domain exists.
### Patches
Upgrading `bitlyshortener` to 0.5.0 or newer will prevent the generation of any such invalid short URLs.
### References
* [Release notes](https://github.com/impredicative/bitlyshortener/releases) | null | 2021-09-21T16:40:42Z | 2020-10-27T19:19:56Z | HIGH | 0 | {'CWE-601'} | {'https://pypi.org/project/bitlyshortener/', 'https://github.com/advisories/GHSA-r82c-j4mq-5xfw', 'https://github.com/impredicative/bitlyshortener/releases/tag/0.5.0', 'https://github.com/impredicative/bitlyshortener/commit/3d412feb77f3daf6f71536463734c2119a55968d', 'https://github.com/impredicative/bitlyshortener/security/advisories/GHSA-r82c-j4mq-5xfw'} | null | {'https://github.com/impredicative/bitlyshortener/commit/3d412feb77f3daf6f71536463734c2119a55968d'} | {'https://github.com/impredicative/bitlyshortener/commit/3d412feb77f3daf6f71536463734c2119a55968d'} |
GHSA | GHSA-2w7w-2j92-44hx | HTTP Request Smuggling in akka-http-core | A vulnerable Akka HTTP server will accept a malformed message and hand it over to the user. If the user application proxies this message to another server unchanged and that server also accepts that message but interprets it as two HTTP messages, the second message has reached the second server without having been inspected by the proxy. | {'CVE-2021-23339'} | 2021-05-10T15:17:09Z | 2021-05-10T15:17:09Z | MODERATE | 6.5 | {'CWE-444'} | {'https://github.com/akka/akka-http/commit/e3a4935151c91cee28e65e6b894dd50839ef9d34', 'https://github.com/advisories/GHSA-2w7w-2j92-44hx', 'https://github.com/akka/akka-http/pull/3754%23issuecomment-779265201', 'https://doc.akka.io/docs/akka-http/10.1/security/2021-02-24-incorrect-handling-of-Transfer-Encoding-header.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23339', 'https://snyk.io/vuln/SNYK-JAVA-COMTYPESAFEAKKA-1075043'} | null | {'https://github.com/akka/akka-http/commit/e3a4935151c91cee28e65e6b894dd50839ef9d34'} | {'https://github.com/akka/akka-http/commit/e3a4935151c91cee28e65e6b894dd50839ef9d34'} |
GHSA | GHSA-m4vv-p6fq-jhqp | Directory Traversal in @vivaxy/here | The @vivaxy/here module is a small web server that serves files with the process' working directory acting as the web root.
It is vulnerable to a directory traversal attack.
This means that files on the local file system which exist outside of the web root may be disclosed to an attacker. This might include confidential files.
Mitigating Factors:
If the node process is run as a user with very limited filesystem permissions, there is significantly less risk of exposing confidential/private information.
Proof of Concept:
```
curl "http://${SERVER_IP}:${SERVER_PORT}/..%2f..%2fetc/passwd"
```
## Recommendation
Run `npm i @vivaxy/here` to install the latest version that addresses this vulnerability. | null | 2021-09-23T21:48:56Z | 2020-09-01T19:04:07Z | HIGH | 0 | {'CWE-22'} | {'https://www.npmjs.com/advisories/557', 'https://github.com/advisories/GHSA-m4vv-p6fq-jhqp', 'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2', 'https://hackerone.com/reports/296254'} | null | {'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2'} | {'https://github.com/vivaxy/here/commit/298dbab41344dfb7f95f66b1fa7b5cfb436bd4a2'} |
GHSA | GHSA-5rcv-m4m3-hfh7 | Infinite Loop in Go | Go version v0.3.3 of the x/text package fixes a vulnerability in encoding/unicode that could lead to the UTF-16 decoder entering an infinite loop, causing the program to crash or run out of memory. An attacker could provide a single byte to a UTF16 decoder instantiated with UseBOM or ExpectBOM to trigger an infinite loop if the String function on the Decoder is called, or the Decoder is passed to golang.org/x/text/transform.String. | {'CVE-2020-14040'} | 2021-05-18T18:34:35Z | 2021-05-18T18:34:35Z | HIGH | 6.7 | {'CWE-835', 'CWE-400'} | {'https://go-review.googlesource.com/c/text/+/238238', 'https://github.com/advisories/GHSA-5rcv-m4m3-hfh7', 'https://groups.google.com/g/golang-announce/c/bXVeAmGOqz0', 'https://groups.google.com/forum/#!topic/golang-announce/bXVeAmGOqz0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14040', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TACQFZDPA7AUR6TRZBCX2RGRFSDYLI7O/', 'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e', 'https://github.com/golang/go/issues/39491'} | null | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e'} | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e'} |
GHSA | GHSA-p5f8-gfw5-33w4 | Heap buffer overflow in Tensorflow | ### Impact
The `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, this code is prone to heap buffer overflow:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L251
If `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large.
### 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 has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2020-15201'} | 2021-11-19T15:19:01Z | 2020-09-25T18:28:34Z | MODERATE | 4.8 | {'CWE-20', 'CWE-787', 'CWE-122'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15201', 'https://github.com/advisories/GHSA-p5f8-gfw5-33w4', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} |
GHSA | GHSA-39q4-p535-c852 | Uncontrolled Resource Consumption in locutus | The package locutus before 2.0.15 are vulnerable to Regular Expression Denial of Service (ReDoS) via the gopher_parsedir function. | {'CVE-2021-23392'} | 2021-06-16T20:02:15Z | 2021-06-10T17:25:05Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/locutusjs/locutus/commit/eb863321990e7e5514aa14f68b8d9978ece9e65e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23392', 'https://github.com/advisories/GHSA-39q4-p535-c852', 'https://github.com/locutusjs/locutus/pull/446', 'https://snyk.io/vuln/SNYK-JS-LOCUTUS-1090597'} | null | {'https://github.com/locutusjs/locutus/commit/eb863321990e7e5514aa14f68b8d9978ece9e65e'} | {'https://github.com/locutusjs/locutus/commit/eb863321990e7e5514aa14f68b8d9978ece9e65e'} |
GHSA | GHSA-6gw4-x63h-5499 | Ability to switch customer email address on account detail page and stay verified | ### Impact
The user may register in a shop by email mail@example.com, verify it, change it to the mail another@domain.com and stay verified and enabled. This may lead to having accounts addressed to totally different emails, that were verified. Note, that this way one is not able to take over any existing account (guest or normal one).
### Patches
Patch has been provided for Sylius 1.6.x and newer - 1.6.9, 1.7.9, 1.8.3. Versions older than 1.6 are not covered by our security support anymore.
### Workarounds
If for whatever reason you are not able to upgrade your application version, you may resolve this issue on your own by creating a custom event listener, which will listen to the `sylius.customer.pre_update` event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain `/admin` prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here.
### Acknowledgements
This security issue has been reported by Mircea Silviu (@decemvre), thanks a lot!
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@sylius.com](mailto:security@sylius.com) | {'CVE-2020-15245'} | 2022-04-19T19:02:37Z | 2020-10-19T20:40:59Z | MODERATE | 4.3 | {'CWE-862', 'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15245', 'https://github.com/Sylius/Sylius/security/advisories/GHSA-6gw4-x63h-5499', 'https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf', 'https://github.com/advisories/GHSA-6gw4-x63h-5499'} | null | {'https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf'} | {'https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf'} |
GHSA | GHSA-856q-xv3c-7f2f | Unauthenticated control plane denial of service attack in Istio | ### Impact
The Istio control plane, `istiod`, is vulnerable to a request processing error, allowing a malicious attacker that sends a specially crafted message which results in the control plane crashing. This endpoint is served over TLS port 15012, but does not require any authentication from the attacker.
For simple installations, Istiod is typically only reachable from within the cluster, limiting the blast radius. However, for some deployments, especially [multicluster](https://istio.io/latest/docs/setup/install/multicluster/primary-remote/) topologies, this port is exposed over the public internet.
### Patches
- Istio 1.13.1 and above
- Istio 1.12.4 and above
- Istio 1.11.7 and above
### Workarounds
There are no effective workarounds, beyond upgrading. Limiting network access to Istiod to the minimal set of clients can help lessen the scope of the vulnerability to some extent.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2022-003)
### For more information
If you have any questions or comments about this advisory, please email us at [istio-security-vulnerability-reports@googlegroups.com](mailto:istio-security-vulnerability-reports@googlegroups.com)
| {'CVE-2022-23635'} | 2022-04-20T21:05:17Z | 2022-02-23T14:59:08Z | HIGH | 7.5 | {'CWE-287'} | {'https://istio.io/latest/news/security/istio-security-2022-003', 'https://github.com/istio/istio/security/advisories/GHSA-856q-xv3c-7f2f', 'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23635', 'https://github.com/advisories/GHSA-856q-xv3c-7f2f'} | null | {'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84'} | {'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84'} |
GHSA | GHSA-26j7-6w8w-7922 | Division by zero in optimized pooling implementations in TFLite | ### Impact
Optimized pooling implementations in TFLite fail to check that the stride arguments are not 0 before calling [`ComputePaddingHeightWidth`](https://github.com/tensorflow/tensorflow/blob/3f24ccd932546416ec906a02ddd183b48a1d2c83/tensorflow/lite/kernels/pooling.cc#L90).
Since users can craft special models which will have `params->stride_{height,width}` be zero, this will result in a division by zero.
### Patches
We have patched the issue in GitHub commit [5f7975d09eac0f10ed8a17dbb6f5964977725adc](https://github.com/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29586'} | 2021-05-21T14:26:43Z | 2021-05-21T14:26:43Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-26j7-6w8w-7922', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29586', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-26j7-6w8w-7922', 'https://github.com/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc'} | null | {'https://github.com/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc'} | {'https://github.com/tensorflow/tensorflow/commit/5f7975d09eac0f10ed8a17dbb6f5964977725adc'} |
GHSA | GHSA-crfx-5phg-hmw9 | Cross-Site Scripting in ids-enterprise | Versions of `ids-enterprise` prior to 4.18.2 are vulnerable to Cross-Site Scripting (XSS). Script tags in the `soho-autocomplete` component are not properly encoded and may allow attackers to execute arbitrary JavaScript.
## Recommendation
Upgrade to version 4.18.2 or later | null | 2021-08-04T21:15:58Z | 2019-06-13T18:59:12Z | HIGH | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/955', 'https://github.com/infor-design/enterprise/commit/ce7b335bb614a6720867abf5b8eb351deb13aed1', 'https://github.com/infor-design/enterprise-ng/issues/502', 'https://github.com/advisories/GHSA-crfx-5phg-hmw9'} | null | {'https://github.com/infor-design/enterprise/commit/ce7b335bb614a6720867abf5b8eb351deb13aed1'} | {'https://github.com/infor-design/enterprise/commit/ce7b335bb614a6720867abf5b8eb351deb13aed1'} |
GHSA | GHSA-278g-rq84-9hmg | `CHECK`-fail in `MapStage` | ### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.MapStage`:
```python
import tensorflow as tf
tf.raw_ops.MapStage(
key=tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64),
indices=tf.constant((0), dtype=tf.int32),
values=[tf.constant((0), dtype=tf.int32)],
dtypes=[tf.int32,
tf.int64],
capacity=0,
memory_limit=0,
container='',
shared_name='')
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L513) does not check that the `key` input is a valid non-empty tensor.
### Patches
We have patched the issue in GitHub commit [d7de67733925de196ec8863a33445b73f9562d1d](https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-37673'} | 2021-08-25T14:41:36Z | 2021-08-25T14:41:36Z | MODERATE | 5.5 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37673', 'https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d', 'https://github.com/advisories/GHSA-278g-rq84-9hmg', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-278g-rq84-9hmg'} | null | {'https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d'} | {'https://github.com/tensorflow/tensorflow/commit/d7de67733925de196ec8863a33445b73f9562d1d'} |
GHSA | GHSA-q674-xm3x-2926 | Uncontrolled Resource Consumption in parse-link-header | The package parse-link-header before 2.0.0 are vulnerable to Regular Expression Denial of Service (ReDoS) via the checkHeader function. | {'CVE-2021-23490'} | 2022-01-07T16:08:29Z | 2022-01-06T21:37:02Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-q674-xm3x-2926', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23490', 'https://snyk.io/vuln/SNYK-JS-PARSELINKHEADER-1582783', 'https://github.com/thlorenz/parse-link-header/commit/72f05c717b3f129c5331a07bf300ed8886eb8ae1', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2321973'} | null | {'https://github.com/thlorenz/parse-link-header/commit/72f05c717b3f129c5331a07bf300ed8886eb8ae1'} | {'https://github.com/thlorenz/parse-link-header/commit/72f05c717b3f129c5331a07bf300ed8886eb8ae1'} |
GHSA | GHSA-fmm9-3gv8-58f4 | Improper Handling of Missing Values in kaml | ### Impact
Attackers that could provide arbitrary YAML input to an application that uses kaml could cause the application to endlessly loop while parsing the input. This could result in resource starvation and denial of service.
This only affects applications that use polymorphic serialization with the default tagged polymorphism style. Applications using the property polymorphism style are not affected.
YAML input for a polymorphic type that provided a tag but no value for the object would trigger the issue, for example:
```yaml
!<x>
```
The following is a sample application that demonstrates this issue:
```kotlin
import com.charleskorn.kaml.Yaml
import kotlinx.serialization.SerialName
import kotlinx.serialization.Serializable
@Serializable
private sealed class K {
@Serializable
@SerialName("x")
data class X(
val property: String? = null,
) : K()
}
const val s = """
!<x>
"""
fun main() {
println("Started.")
val result = Yaml.default.decodeFromString(K.serializer(), s)
println("Finished, result is $result")
}
```
On vulnerable versions of kaml, the `decodeFromString()` operation hangs and never returns.
### Patches
Version 0.35.3 or later contain the fix for this issue. | {'CVE-2021-39194'} | 2021-09-08T14:47:33Z | 2021-09-07T23:08:40Z | MODERATE | 4.3 | {'CWE-835', 'CWE-230'} | {'https://github.com/advisories/GHSA-fmm9-3gv8-58f4', 'https://github.com/charleskorn/kaml/issues/179', 'https://github.com/charleskorn/kaml/commit/e18785d043fc6324c81e968aae9764b4b060bc6a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39194', 'https://github.com/charleskorn/kaml/security/advisories/GHSA-fmm9-3gv8-58f4'} | null | {'https://github.com/charleskorn/kaml/commit/e18785d043fc6324c81e968aae9764b4b060bc6a'} | {'https://github.com/charleskorn/kaml/commit/e18785d043fc6324c81e968aae9764b4b060bc6a'} |
GHSA | GHSA-5x3v-2gxr-59m2 | Directory traversal in Apache RocketMQ | In Apache RocketMQ 4.2.0 to 4.6.0, when the automatic topic creation in the broker is turned on by default, an evil topic like “../../../../topic2020” is sent from rocketmq-client to the broker, a topic folder will be created in the parent directory in brokers, which leads to a directory traversal vulnerability. Users of the affected versions should apply one of the following: Upgrade to Apache RocketMQ 4.6.1 or later. | {'CVE-2019-17572'} | 2021-04-07T19:55:55Z | 2020-07-01T17:26:15Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/apache/rocketmq/issues/1637', 'https://github.com/advisories/GHSA-5x3v-2gxr-59m2', 'https://lists.apache.org/thread.html/fdea1c5407da47a17d5522fa149a097cacded1916c1c1534d46edc6d%40%3Cprivate.rocketmq.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17572', 'https://github.com/apache/rocketmq/commit/f8f6fbe4aa7f5dee937e688322628c366b12a552', 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEROCKETMQ-569108', 'https://seclists.org/oss-sec/2020/q2/112'} | null | {'https://github.com/apache/rocketmq/commit/f8f6fbe4aa7f5dee937e688322628c366b12a552'} | {'https://github.com/apache/rocketmq/commit/f8f6fbe4aa7f5dee937e688322628c366b12a552'} |
GHSA | GHSA-9g8h-pjm4-q92p | Out-of-bounds Write in OpenCV. | In OpenCV 3.3.1 (corresponding with OpenCV-Python 3.3.1.11), a heap-based buffer overflow happens in cv::Jpeg2KDecoder::readComponent8u in modules/imgcodecs/src/grfmt_jpeg2000.cpp when parsing a crafted image file. | {'CVE-2018-5268'} | 2021-11-18T15:31:48Z | 2021-10-12T22:23:41Z | MODERATE | 5.5 | {'CWE-787'} | {'http://www.securityfocus.com/bid/106945', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://github.com/opencv/opencv/issues/10541', 'https://nvd.nist.gov/vuln/detail/CVE-2018-5268', 'https://github.com/opencv/opencv/pull/10566/commits/435a3e337bd9d4e11af61cf8b8afca067bf1a8aa', 'https://github.com/advisories/GHSA-9g8h-pjm4-q92p', 'https://lists.debian.org/debian-lts-announce/2018/04/msg00019.html', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html'} | null | {'https://github.com/opencv/opencv/pull/10566/commits/435a3e337bd9d4e11af61cf8b8afca067bf1a8aa'} | {'https://github.com/opencv/opencv/pull/10566/commits/435a3e337bd9d4e11af61cf8b8afca067bf1a8aa'} |
GHSA | GHSA-4fjv-pmhg-3rfg | Multiple cryptographic issues in Python oic | ### Impact
* Client implementations using this library
### Issues
1) The IdToken signature algorithm was not checked automatically, but only if the expected algorithm was passed in as a kwarg.
2) JWA `none` algorithm was allowed in all flows.
3) `oic.consumer.Consumer.parse_authz` returns an unverified IdToken. The verification of the token was left to the discretion of the implementator.
4) `iat` claim was not checked for sanity (i.e. it could be in the future)
### Patches
1) IdToken signature is now always checked.
2) JWA `none` algorithm is now allowed only if using the `response_type` `code`
3) IdToken verification is now done automatically.
4) `iat` claim is now checked for sanity. | {'CVE-2020-26244'} | 2022-04-19T19:02:41Z | 2020-12-04T16:47:12Z | MODERATE | 6.8 | {'CWE-325', 'CWE-347'} | {'https://github.com/OpenIDC/pyoidc/security/advisories/GHSA-4fjv-pmhg-3rfg', 'https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498', 'https://github.com/OpenIDC/pyoidc/releases/tag/1.2.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26244', 'https://github.com/advisories/GHSA-4fjv-pmhg-3rfg', 'https://pypi.org/project/oic/'} | null | {'https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498'} | {'https://github.com/OpenIDC/pyoidc/commit/62f8d753fa17c8b1f29f8be639cf0b33afb02498'} |
GHSA | GHSA-xhr8-mpwq-2rr2 | Automatic named constructor discovery in Valinor | ## Design issue - automatic constructor discovery
The issue arises when upgrading from `cuyz/valinor:0.3.0` to a newer system on an existing application, which broke due to the wrong constructor being picked.
Still, a bigger security concern is problematic, and it is akin to https://github.com/rails/rails/issues/5228.
## Example exploit
Take following DTO example:
```php
final class UserDTO
{
public function __construct(
public int $id,
public string $name
) {}
public static function fromDb(
PDO $connection,
int $id
): self { /* ... code to fetch the DTO here ... */ }
}
```
There is nothing inherently unsafe about the above `UserDTO`, but when mixed with `cuyz/valinor:^0.5.0` ( specifically https://github.com/CuyZ/Valinor/commit/718d3c1bc2ea7d28b4b1f6c062addcd1dde8660b ), it is an explosive mix:
```php
// this could be coming from user input:
$maliciousPayload = [
'connection' => [
'dsn' => 'mysql:host=some-host;database=some-database',
'username' => 'root',
'password' => 'root',
'options' => [
// PDO::MYSQL_ATTR_INIT_COMMAND === 1002
1002 => 'DROP DATABASE all-the-moneys'
]
],
'id' => 123,
];
$treeMapper->map(
UserDTO::class,
$maliciousPayload
); // your DB is gone :D
```
The above payload is represented in PHP form, but may as well be input JSON, HTML or x-form-urlencoded.
## Mitigation
Version 0.7.0 contains a patch for this issue.
Automatic named constructor resolution should be disabled - only explicitly mapped named constructors should be used/discovered. | null | 2022-04-05T21:39:22Z | 2022-04-01T13:39:45Z | HIGH | 0 | null | {'https://github.com/advisories/GHSA-xhr8-mpwq-2rr2', 'https://github.com/CuyZ/Valinor/commit/718d3c1bc2ea7d28b4b1f6c062addcd1dde8660b', 'https://github.com/CuyZ/Valinor/security/advisories/GHSA-xhr8-mpwq-2rr2', 'https://github.com/CuyZ/Valinor/releases/tag/0.7.0'} | null | {'https://github.com/CuyZ/Valinor/commit/718d3c1bc2ea7d28b4b1f6c062addcd1dde8660b'} | {'https://github.com/CuyZ/Valinor/commit/718d3c1bc2ea7d28b4b1f6c062addcd1dde8660b'} |
GHSA | GHSA-f6g6-54hm-fhxv | Data races in libsbc | Affected versions of this crate implements `Send` for `Decoder<R>` for any `R: Read`. This allows `Decoder<R>` to contain `R: !Send` and carry (move) it to another thread.
This can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.
The flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder<R>`. | {'CVE-2020-36440'} | 2021-08-25T20:59:02Z | 2021-08-25T20:59:02Z | HIGH | 8.1 | {'CWE-119', 'CWE-362'} | {'https://github.com/mvertescher/libsbc-rs/commit/a34d6e1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36440', 'https://rustsec.org/advisories/RUSTSEC-2020-0120.html', 'https://github.com/advisories/GHSA-f6g6-54hm-fhxv'} | null | {'https://github.com/mvertescher/libsbc-rs/commit/a34d6e1'} | {'https://github.com/mvertescher/libsbc-rs/commit/a34d6e1'} |
GHSA | GHSA-x8rq-rc7x-5fg5 | uppy's companion module is vulnerable to Server-Side Request Forgery (SSRF) | uppy's companion module is vulnerable to Server-Side Request Forgery (SSRF) via IPv4-mapped IPv6 addresses. | {'CVE-2022-0086'} | 2022-04-19T19:03:24Z | 2022-01-06T22:24:35Z | HIGH | 8.2 | {'CWE-918'} | {'https://huntr.dev/bounties/c1c03ef6-3f18-4976-a9ad-08c251279122', 'https://github.com/transloadit/uppy/commit/fc137e30a2a3102eb191141f280d5de20dacdf8f', 'https://github.com/transloadit/uppy/releases/tag/uppy%402.3.3', 'https://github.com/transloadit/uppy/pull/3403', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0086', 'https://github.com/advisories/GHSA-x8rq-rc7x-5fg5'} | null | {'https://github.com/transloadit/uppy/commit/fc137e30a2a3102eb191141f280d5de20dacdf8f'} | {'https://github.com/transloadit/uppy/commit/fc137e30a2a3102eb191141f280d5de20dacdf8f'} |
GHSA | GHSA-89px-ww3j-g2mm | 2FA bypass in Wagtail through new device path | ## 2FA bypass through new device path
### Impact
If someone gains access to someone's Wagtail login credentials, they can log into the CMS and bypass the 2FA check by changing the URL. They can then add a new device and gain full access to the CMS.
### Patches
This problem has been patched in version 1.3.0.
### Workarounds
There is no workaround at the moment.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa)
* Email us at [security@labdigital.nl](mailto:security@labdigital.nl) | {'CVE-2019-16766'} | 2021-01-08T21:28:09Z | 2019-11-29T17:05:59Z | HIGH | 8.7 | {'CWE-304', 'CWE-290'} | {'https://github.com/advisories/GHSA-89px-ww3j-g2mm', 'https://github.com/labd/wagtail-2fa/commit/a6711b29711729005770ff481b22675b35ff5c81', 'https://github.com/labd/wagtail-2fa/security/advisories/GHSA-89px-ww3j-g2mm', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16766', 'https://github.com/labd/wagtail-2fa/commit/13b12995d35b566df08a17257a23863ab6efb0ca'} | null | {'https://github.com/labd/wagtail-2fa/commit/a6711b29711729005770ff481b22675b35ff5c81', 'https://github.com/labd/wagtail-2fa/commit/13b12995d35b566df08a17257a23863ab6efb0ca'} | {'https://github.com/labd/wagtail-2fa/commit/a6711b29711729005770ff481b22675b35ff5c81', 'https://github.com/labd/wagtail-2fa/commit/13b12995d35b566df08a17257a23863ab6efb0ca'} |
GHSA | GHSA-hj69-c76v-86wr | Out-of-bounds Read in Pillow | libImaging/FliDecode.c in Pillow before 6.2.2 has an FLI buffer overflow. | {'CVE-2020-5313'} | 2021-08-23T15:05:21Z | 2020-04-01T16:36:00Z | HIGH | 7.1 | {'CWE-125'} | {'https://github.com/advisories/GHSA-hj69-c76v-86wr', 'https://www.debian.org/security/2020/dsa-4631', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MMU3WT2X64GS5WHDPKKC2WZA7UIIQ3A/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5313', 'https://github.com/python-pillow/Pillow/commit/a09acd0decd8a87ccce939d5ff65dab59e7d365b', 'https://github.com/python-pillow/Pillow/blob/master/CHANGES.rst#622-2020-01-02', 'https://usn.ubuntu.com/4272-1/', 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.2.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3DUMIBUYGJRAVJCTFUWBRLVQKOUTVX5P/'} | null | {'https://github.com/python-pillow/Pillow/commit/a09acd0decd8a87ccce939d5ff65dab59e7d365b'} | {'https://github.com/python-pillow/Pillow/commit/a09acd0decd8a87ccce939d5ff65dab59e7d365b'} |
GHSA | GHSA-5jfw-35xp-5m42 | Buffer length underflow in LoginPacket causing unchecked exceptions to be thrown | ### Impact
`LoginPacket` uses `BinaryStream->getLInt()` to read the lengths of JSON payloads it wants to decode. Unfortunately, `BinaryStream->getLInt()` returns a signed integer, meaning that a malicious client can craft a packet with a large uint32 value for payload buffer size (which would be interpreted as a negative signed int32), causing `BinaryStream->get()` to throw an exception.
In the context of PocketMine-MP, this leads to a server crash when the vulnerability is exploited.
### Patches
e3fce7632b94e83fd6a518a87dcaf6a11681c4ac
### Workarounds
This can be worked around by registering a custom `LoginPacket` implementation into `PacketPool` which overrides [this code](https://github.com/pmmp/BedrockProtocol/blob/47532c95ea37d5f0365b23f734d70d943ff95295/src/LoginPacket.php#L54) to patch it.
### For more information
* Email us at [team@pmmp.io](mailto:team@pmmp.io) | null | 2022-04-06T18:43:19Z | 2022-04-05T17:53:22Z | HIGH | 7.5 | {'CWE-124'} | {'https://github.com/pmmp/BedrockProtocol/security/advisories/GHSA-5jfw-35xp-5m42', 'https://github.com/advisories/GHSA-5jfw-35xp-5m42', 'https://github.com/pmmp/BedrockProtocol/commit/e3fce7632b94e83fd6a518a87dcaf6a11681c4ac'} | null | {'https://github.com/pmmp/BedrockProtocol/commit/e3fce7632b94e83fd6a518a87dcaf6a11681c4ac'} | {'https://github.com/pmmp/BedrockProtocol/commit/e3fce7632b94e83fd6a518a87dcaf6a11681c4ac'} |
GHSA | GHSA-vcjj-xf2r-mwvc | XSS in knockout | There is a vulnerability in knockout before version 3.5.0-beta, where after escaping the context of the web application, the web application delivers data to its users along with other trusted dynamic content, without validating it. | {'CVE-2019-14862'} | 2022-04-25T23:07:31Z | 2020-04-01T15:47:45Z | MODERATE | 6.1 | {'CWE-79'} | {'https://snyk.io/vuln/npm:knockout:20180213', 'https://www.whitesourcesoftware.com/vulnerability-database/WS-2019-0015', 'https://github.com/knockout/knockout/issues/1244', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://github.com/advisories/GHSA-vcjj-xf2r-mwvc', 'https://github.com/knockout/knockout/commit/7e280b2b8a04cc19176b5171263a5c68bda98efb', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14862', 'https://github.com/knockout/knockout/pull/2345', 'https://nvd.nist.gov/vuln/detail/CVE-2019-14862', 'https://www.oracle.com/security-alerts/cpujan2021.html'} | null | {'https://github.com/knockout/knockout/commit/7e280b2b8a04cc19176b5171263a5c68bda98efb'} | {'https://github.com/knockout/knockout/commit/7e280b2b8a04cc19176b5171263a5c68bda98efb'} |
GHSA | GHSA-653m-r33x-39ff | Moderate severity vulnerability that affects geminabox | Stored cross-site scripting (XSS) vulnerability in "geminabox" (Gem in a Box) before 0.13.10 allows attackers to inject arbitrary web script via the "homepage" value of a ".gemspec" file, related to views/gem.erb and views/index.erb. | {'CVE-2017-16792'} | 2021-09-01T22:38:12Z | 2017-11-29T23:20:14Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-653m-r33x-39ff', 'https://github.com/geminabox/geminabox/commit/f8429a9e364658459add170e4ebc7a5d3b4759e7', 'https://github.com/geminabox/geminabox/blob/master/CHANGELOG.md', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16792', 'https://rubygems.org/gems/geminabox/versions/0.13.10'} | null | {'https://github.com/geminabox/geminabox/commit/f8429a9e364658459add170e4ebc7a5d3b4759e7'} | {'https://github.com/geminabox/geminabox/commit/f8429a9e364658459add170e4ebc7a5d3b4759e7'} |
GHSA | GHSA-57qf-82hh-2hmc | Cross-site Scripting in LiveHelperChat | LiveHelperChat prior to version 3.93 is vulnerable to cross-site scripting. | {'CVE-2022-0502'} | 2022-02-14T22:30:21Z | 2022-02-07T00:00:30Z | MODERATE | 5.4 | {'CWE-79'} | {'https://huntr.dev/bounties/34f2aa30-de7f-432a-8749-b43d2774140f', 'https://github.com/livehelperchat/livehelperchat/commit/d3b107aaa8ec10816acc762d60e7321079c21706', 'https://github.com/advisories/GHSA-57qf-82hh-2hmc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0502'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/d3b107aaa8ec10816acc762d60e7321079c21706'} | {'https://github.com/livehelperchat/livehelperchat/commit/d3b107aaa8ec10816acc762d60e7321079c21706'} |
GHSA | GHSA-8c9x-wfgj-v78w | Open Redirect in showdoc | showdoc is vulnerable to URL Redirection to Untrusted Site | {'CVE-2021-4000'} | 2021-12-16T15:31:58Z | 2021-12-16T15:31:58Z | MODERATE | 6.5 | {'CWE-601'} | {'https://huntr.dev/bounties/e4d803e0-3104-432c-80b3-34bc453c8962', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4000', 'https://github.com/star7th/showdoc/commit/c7f10033eba5f2b5a537f9af9ba2379138e67138', 'https://github.com/advisories/GHSA-8c9x-wfgj-v78w'} | null | {'https://github.com/star7th/showdoc/commit/c7f10033eba5f2b5a537f9af9ba2379138e67138'} | {'https://github.com/star7th/showdoc/commit/c7f10033eba5f2b5a537f9af9ba2379138e67138'} |
GHSA | GHSA-4ppp-gpcr-7qf6 | HTTP Request Smuggling: Content-Length Sent Twice in Waitress | ### Impact
Waitress would header fold a double `Content-Length` header and due to being unable to cast the now comma separated value to an integer would set the `Content-Length` to 0 internally.
So a request with:
```
Content-Length: 10
Content-Length: 10
```
would get transformed to:
```
Content-Length: 10, 10
```
Which would Waitress would then internally set to `Content-Lenght: 0`.
Waitress would then treat the request as having no body, thereby treating the body of the request as a new request in HTTP pipelining.
### Patches
This issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.
The Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don't cause any changes in behavior.
### Workarounds
Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn't use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).
### Issues/more security issues:
* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related) | null | 2022-03-24T17:52:21Z | 2019-12-20T23:04:35Z | CRITICAL | 0 | {'CWE-444'} | {'https://github.com/advisories/GHSA-4ppp-gpcr-7qf6', 'https://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65', 'https://github.com/Pylons/waitress/security/advisories/GHSA-4ppp-gpcr-7qf6'} | null | {'https://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65'} | {'https://github.com/Pylons/waitress/commit/575994cd42e83fd772a5f7ec98b2c56751bd3f65'} |
GHSA | GHSA-px4h-xg32-q955 | ReDoS in normalize-url | The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs. | {'CVE-2021-33502'} | 2021-10-27T17:04:16Z | 2021-06-08T23:11:43Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/sindresorhus/normalize-url/releases/tag/v6.0.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33502', 'https://github.com/advisories/GHSA-px4h-xg32-q955', 'https://security.netapp.com/advisory/ntap-20210706-0001/', 'https://github.com/sindresorhus/normalize-url/commit/b1fdb5120b6d27a88400d8800e67ff5a22bd2103'} | null | {'https://github.com/sindresorhus/normalize-url/commit/b1fdb5120b6d27a88400d8800e67ff5a22bd2103'} | {'https://github.com/sindresorhus/normalize-url/commit/b1fdb5120b6d27a88400d8800e67ff5a22bd2103'} |
GHSA | GHSA-h4pc-gx2w-f2xv | Heap OOB read in TFLite | ### Impact
A specially crafted TFLite model could trigger an OOB read on heap in the TFLite implementation of [`Split_V`](https://github.com/tensorflow/tensorflow/blob/c59c37e7b2d563967da813fa50fe20b21f4da683/tensorflow/lite/kernels/split_v.cc#L99):
```cc
const int input_size = SizeOfDimension(input, axis_value);
```
If `axis_value` is not a value between 0 and `NumDimensions(input)`, then the [`SizeOfDimension` function](https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/kernel_util.h#L148-L150) will access data outside the bounds of the tensor shape array:
```cc
inline int SizeOfDimension(const TfLiteTensor* t, int dim) {
return t->dims->data[dim];
}
```
### Patches
We have patched the issue in GitHub commit [ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412](https://github.com/tensorflow/tensorflow/commit/ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29606'} | 2021-05-21T14:28:24Z | 2021-05-21T14:28:24Z | HIGH | 7.1 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h4pc-gx2w-f2xv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29606', 'https://github.com/tensorflow/tensorflow/commit/ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412', 'https://github.com/advisories/GHSA-h4pc-gx2w-f2xv'} | null | {'https://github.com/tensorflow/tensorflow/commit/ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412'} | {'https://github.com/tensorflow/tensorflow/commit/ae2daeb45abfe2c6dda539cf8d0d6f653d3ef412'} |
GHSA | GHSA-vpx7-vm66-qx8r | Path Traversal in github.com/unknwon/cae/zip | The ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading "..". This allows an attacker to add or replace files system-wide. | {'CVE-2020-7664'} | 2022-01-04T19:33:01Z | 2021-05-18T20:31:06Z | HIGH | 7.5 | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383', 'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://github.com/advisories/GHSA-vpx7-vm66-qx8r', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7664'} | null | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} |
GHSA | GHSA-h9vc-2p9g-63gp | Exposure of Sensitive Information to an Unauthorized Actor in pimcore | Exposure of Sensitive Information to an Unauthorized Actor in Packagist pimcore/pimcore prior to 10.3.1. | {'CVE-2022-0565'} | 2022-02-24T13:10:52Z | 2022-02-15T00:02:47Z | HIGH | 7.5 | {'CWE-200'} | {'https://github.com/advisories/GHSA-h9vc-2p9g-63gp', 'https://huntr.dev/bounties/b0b29656-4bbe-41cf-92f6-8579df0b6de5', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0565', 'https://github.com/pimcore/pimcore/commit/7697f709a501860144352696e583a2533a6e1245'} | null | {'https://github.com/pimcore/pimcore/commit/7697f709a501860144352696e583a2533a6e1245'} | {'https://github.com/pimcore/pimcore/commit/7697f709a501860144352696e583a2533a6e1245'} |
GHSA | GHSA-4cfr-gjfx-fj3x | Cobbler before 3.3.0 allows arbitrary file write operations via upload_log_data. | Cobbler before 3.3.0 allows arbitrary file write operations via upload_log_data. | {'CVE-2021-40324'} | 2021-10-13T17:27:07Z | 2021-10-05T17:53:11Z | HIGH | 0 | {'CWE-434'} | {'https://github.com/cobbler/cobbler/releases/tag/v3.3.0', 'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40324', 'https://github.com/advisories/GHSA-4cfr-gjfx-fj3x'} | null | {'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a'} | {'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a'} |
GHSA | GHSA-qxmr-qxh6-2cc9 | ReDos vulnerability on guest checkout email validation | ### Impact
Denial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order's email was subject to exponential backtracking through a fragment like `a.a.`.
Before the patch, it can be reproduced in the console like this:
```ruby
irb(main)> Spree::EmailValidator::EMAIL_REGEXP.match "a@a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.@"
processing time: 54.293660s
=> nil
```
To reproduce in the browser, fill in the "Customer Email" field with that fake email address during a guest checkout. Before that, you should open the browser dev tools and change the `type` attribute for that field from `email` to `text`. After entering a fake address and pressing the "Save & Continue" button, the browser will take a long term to perform the request before showing an error message for the invalid address. Eventually, making the email string even longer could lead to the exhaustion of server resources.
### Patches
Versions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression.
There's an improbable chance that some orders in your system end up having associated an email address that is no longer valid. We've added a task to check precisely that:
```bash
bin/rails solidus:check_orders_with_invalid_email
```
The above will print information for every affected order if any.
### Workarounds
If a prompt upgrade is not an option, please, add the following to `config/application.rb`:
```ruby
config.after_initialize do
Spree::EmailValidator.send(:remove_const, :EMAIL_REGEXP)
Spree::EmailValidator::EMAIL_REGEXP = URI::MailTo::EMAIL_REGEXP
end
```
### References
- https://en.wikipedia.org/wiki/ReDoS
- https://snyk.io/blog/redos-and-catastrophic-backtracking/
### For more information
If you have any questions or comments about this advisory:
* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
| {'CVE-2021-43805'} | 2022-04-19T19:03:16Z | 2021-12-07T22:01:47Z | HIGH | 7.5 | {'CWE-1333'} | {'https://github.com/solidusio/solidus/commit/6be174c955fad84017ca67589c676526bc5ade71', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43805', 'https://github.com/solidusio/solidus/commit/9867153e01e3c3b898cdbcedd7b43375ea922401', 'https://github.com/advisories/GHSA-qxmr-qxh6-2cc9', 'https://github.com/solidusio/solidus/security/advisories/GHSA-qxmr-qxh6-2cc9'} | null | {'https://github.com/solidusio/solidus/commit/9867153e01e3c3b898cdbcedd7b43375ea922401', 'https://github.com/solidusio/solidus/commit/6be174c955fad84017ca67589c676526bc5ade71'} | {'https://github.com/solidusio/solidus/commit/9867153e01e3c3b898cdbcedd7b43375ea922401', 'https://github.com/solidusio/solidus/commit/6be174c955fad84017ca67589c676526bc5ade71'} |
GHSA | GHSA-hcw3-j74m-qc58 | Incorrect Calculation in github.com/open-policy-agent/opa | ### Impact
Under certain conditions, pretty-printing an AST that contains synthetic nodes could change the logic of some statements by reordering array literals. Example of policies impacted are those that parse and compare web paths, see the example below.
**All of these** three conditions have to be met to create an adverse effect:
1. An AST of Rego had to be **created programmatically** such that it ends up containing terms without a location (such as wildcard variables).
2. The AST had to be **pretty-printed** using the `github.com/open-policy-agent/opa/format` package.
3. The result of the pretty-printing had to be **parsed and evaluated again** via an OPA instance using the bundles, or the Golang packages.
If any of these three conditions are not met, you are not affected.
Notably, all three would be true if using **optimized bundles**, i.e. bundles created with `opa build -O=1` or higher.
In that case, the optimizer would fulfil condition (1.), the result of that would be pretty-printed when writing the bundle to disk, fulfilling (2.). When the bundle was then used, we'd satisfy (3.).
#### Example
For example, the process outlined above could turn
this rule
```rego
hello {
["foo", _] = split(input.resource, "/")
}
```
into
```rego
hello {
[_, "foo"] = split(input.resource, "/")
}
```
with an input of
```rego
{
"resource": "foo/bar"
}
```
the result would change from
```rego
{
"hello": true
}
```
to (no default value of hello)
```rego
{}
```
The severity was determined to be *moderate* because the conditions are quite particular. Please note that its only the OPA bundle build process thats affected. An OPA sidecar of version 0.36.0 with an optimized bundle built by OPA 0.32.1 would not face this bug.
### Patches
Fixed in version 0.37.2.
### Workarounds
- Disabling optimization when creating bundles.
### References
- Introduced in https://github.com/open-policy-agent/opa/pull/3851
- Backported for the 0.33.1 patch release: https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717
- Fixed by https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239 and https://github.com/open-policy-agent/opa/commit/2bd8edab9e10e2dc9cf76ae8335ced0c224f3055
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Community Discussions](https://github.com/open-policy-agent/community/discussions/categories/opa-and-rego)
* Ask in Slack: https://slack.openpolicyagent.org/ | {'CVE-2022-23628'} | 2022-04-19T19:03:21Z | 2022-02-09T22:17:37Z | MODERATE | 6.3 | {'CWE-682'} | {'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/pull/3851', 'https://github.com/advisories/GHSA-hcw3-j74m-qc58', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23628', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239', 'https://github.com/open-policy-agent/opa/security/advisories/GHSA-hcw3-j74m-qc58'} | null | {'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239'} | {'https://github.com/open-policy-agent/opa/commit/bfd984ddf93ef2c4963a08d4fdadae0bcf1a3717', 'https://github.com/open-policy-agent/opa/commit/932e4ffc37a590ace79e9b75ca4340288c220239'} |
GHSA | GHSA-7vxc-chqj-h83g | showdoc is vulnerable to Cross-Site Request Forgery (CSRF) | showdoc is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-4168'} | 2022-01-07T16:11:22Z | 2022-01-06T22:02:18Z | MODERATE | 6.3 | {'CWE-352'} | {'https://github.com/star7th/showdoc/commit/3ff0c85d439ccbdfadeb96b5a52acf6318041109', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4168', 'https://github.com/advisories/GHSA-7vxc-chqj-h83g', 'https://huntr.dev/bounties/f14431e2-f1f6-4331-ba91-a4ea8b26be0c'} | null | {'https://github.com/star7th/showdoc/commit/3ff0c85d439ccbdfadeb96b5a52acf6318041109'} | {'https://github.com/star7th/showdoc/commit/3ff0c85d439ccbdfadeb96b5a52acf6318041109'} |
GHSA | GHSA-qjmq-8hjr-qcv6 | SQL Injection when creating an application with Reactive SQL backend | ### Impact
SQL Injection vulnerability in entities for applications generated with the option "reactive with Spring WebFlux" enabled and an SQL database using r2dbc. Applications created without "reactive with Spring WebFlux" and applications with NoSQL databases are not affected.
If you have generated a microservice Gateway using the affected version, you might be impacted as Gateways are reactive by default.
Currently, SQL injection is possible in the `findAllBy(Pageable pageable, Criteria criteria)` method of an entity repository class generated in these applications as the where clause using Criteria for queries are not sanitized and user input is passed on as it is by the criteria.
## Impacted applications
- Monolith and microservice applications with SQL database and reactive with Spring WebFlux combination (other combinations are not affected and the issue is only present when you generate entities)
- Gateway applications with SQL database (issue will appear only when generating entities)
### Patches
Patched in v7.8.1
The `findAllBy(Pageable pageable, Criteria criteria)` method has been removed from the entity repositories and `org.springframework.data.relational.core.query.Criteria` support in the underlying methods has been replaced with `org.springframework.data.relational.core.sql.Condition`. This means you won't be able to do custom filtering in the generated applications.
If you have existing reactive applications generated by the impacted version, we advise you to audit for use of `Criteria` and take appropriate actions.
### Workarounds
The problem lies in the `EntityManager.java` class when creating the where clause via `Conditions.just(criteria.toString())`.
`just` accepts the literal string provided. Criteria's `toString` method returns a plain string and this combination is vulnerable to sql injection as the string is not sanitized and will contain whatever used passed as input using any plain SQL
So be careful when combining criterias and conditions. As a workaround we have removed the possibility to pass any user-provided criteria to the `createSelect` method of `EntityManager`.
### Example
```java
Criteria criteria = Criteria.where("name").is("foobar';DROP TABLE example;--"); // parameter is user provided input
criteria.toString(); // --> "'foobar';DROP TABLE example;--'"
```
### References
[More details in this Issue report](https://github.com/jhipster/generator-jhipster/issues/18269)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [JHipster issue tracker](https://github.com/jhipster/generator-jhipster/issues)
| {'CVE-2022-24815'} | 2022-04-18T22:20:12Z | 2022-04-07T15:18:05Z | HIGH | 8.1 | {'CWE-89'} | {'https://github.com/jhipster/generator-jhipster/issues/18269', 'https://github.com/jhipster/generator-jhipster/commit/c220a210fd7742c53eea72bd5fadbb96220faa98', 'https://github.com/jhipster/generator-jhipster/security/advisories/GHSA-qjmq-8hjr-qcv6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24815', 'https://github.com/advisories/GHSA-qjmq-8hjr-qcv6'} | null | {'https://github.com/jhipster/generator-jhipster/commit/c220a210fd7742c53eea72bd5fadbb96220faa98'} | {'https://github.com/jhipster/generator-jhipster/commit/c220a210fd7742c53eea72bd5fadbb96220faa98'} |
GHSA | GHSA-7xwj-5r4v-429p | NPE in TFLite | ### Impact
The implementation of SVDF in TFLite is [vulnerable to a null pointer error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/svdf.cc#L300-L313):
```cc
TfLiteTensor* state = GetVariableInput(context, node, kStateTensor);
// ...
GetTensorData<float>(state)
```
The [`GetVariableInput` function](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L115-L119) can return a null pointer but `GetTensorData` assumes that the argument is always a valid tensor.
```cc
TfLiteTensor* GetVariableInput(TfLiteContext* context, const TfLiteNode* node,
int index) {
TfLiteTensor* tensor = GetMutableInput(context, node, index);
return tensor->is_variable ? tensor : nullptr;
}
```
Furthermore, because `GetVariableInput` calls [`GetMutableInput`](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/kernel_util.cc#L82-L90) which might return `nullptr`, the `tensor->is_variable` expression can also trigger a null pointer exception.
### Patches
We have patched the issue in GitHub commit [5b048e87e4e55990dae6b547add4dae59f4e1c76](https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37681'} | 2021-08-25T14:40:35Z | 2021-08-25T14:40:35Z | HIGH | 7.8 | {'CWE-476'} | {'https://github.com/advisories/GHSA-7xwj-5r4v-429p', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37681', 'https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7xwj-5r4v-429p'} | null | {'https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76'} | {'https://github.com/tensorflow/tensorflow/commit/5b048e87e4e55990dae6b547add4dae59f4e1c76'} |
GHSA | GHSA-xhfx-hgmf-v6vp | Potential Host Header Poisoning on misconfigured servers | ### Impact
When running on servers that are configured to accept a wildcard as a hostname (i.e. the server routes any request, regardless of the HOST header to an October CMS instance) the potential exists for Host Header Poisoning attacks to succeed. See the following resources for more information on Host Header Poisoning:
- https://portswigger.net/web-security/host-header
- https://dzone.com/articles/what-is-a-host-header-attack
### Patches
A feature has been added in v1.1.2 to allow a set of trusted hosts to be specified in the application.
### Workarounds
- Apply https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6 & https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0 to your installation manually if unable to upgrade to v1.1.2.
- Check that the configuration setting `cms.linkPolicy` is set to `force`.
### Alternative Workaround
Check to make sure that your web server does not accept any hostname when serving your web application.
1. Add an entry called `testing.tld` to your computer's host file and direct it to your server's IP address
2. Open the address `testing.tld` in your web browser
3. Make sure an October CMS website is not available at this address
If an October CMS website is returned, configure your webserver to only allow known hostnames. If you require assistance with this, please contact your server administrator.
### References
Reported by [Abdullah Hussam](https://github.com/ahussam)
### For More Information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat Assessment
<img width="1108" alt="Screen Shot 2021-01-15 at 4 12 57 PM" src="https://user-images.githubusercontent.com/7253840/104783859-92fb3600-574c-11eb-9e21-c0dc05d230a9.png"> | {'CVE-2021-21265'} | 2021-03-11T02:18:01Z | 2021-03-10T21:07:25Z | LOW | 0 | {'CWE-644'} | {'https://packagist.org/packages/october/backend', 'https://github.com/advisories/GHSA-xhfx-hgmf-v6vp', 'https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21265', 'https://github.com/octobercms/october/security/advisories/GHSA-xhfx-hgmf-v6vp', 'https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6'} | null | {'https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6', 'https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0'} | {'https://github.com/octobercms/library/commit/f86fcbcd066d6f8b939e8fe897409d152b11c3c6', 'https://github.com/octobercms/october/commit/f638d3f78cfe91d7f6658820f9d5e424306a3db0'} |
GHSA | GHSA-8gwj-8hxc-285w | Prototype Pollution in json-ptr | This affects the package `json-ptr` before `3.0.0`. A type confusion vulnerability can lead to a bypass of CVE-2020-7766 when the user-provided keys used in the pointer parameter are arrays. | {'CVE-2021-23509'} | 2021-11-08T17:43:27Z | 2021-11-08T17:43:27Z | MODERATE | 5.6 | {'CWE-843', 'CWE-1321'} | {'https://github.com/flitbit/json-ptr%23security-vulnerabilities-resolved', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23509', 'https://github.com/flitbit/json-ptr/pull/42', 'https://github.com/flitbit/json-ptr/commit/5dc458fbad1c382a2e3ca6d62e66ede3d92849ca', 'https://snyk.io/vuln/SNYK-JS-JSONPTR-1577291', 'https://github.com/advisories/GHSA-8gwj-8hxc-285w'} | null | {'https://github.com/flitbit/json-ptr/commit/5dc458fbad1c382a2e3ca6d62e66ede3d92849ca'} | {'https://github.com/flitbit/json-ptr/commit/5dc458fbad1c382a2e3ca6d62e66ede3d92849ca'} |
GHSA | GHSA-hpqh-2wqx-7qp5 | Memory access due to code generation flaw in Cranelift module | There is a bug in 0.73.0 of the Cranelift x64 backend that can create a scenario that could result in a potential sandbox escape in a WebAssembly module. Users of versions 0.73.0 of Cranelift should upgrade to either 0.73.1 or 0.74 to remediate this vulnerability. Users of Cranelift prior to 0.73.0 should update to 0.73.1 or 0.74 if they were not using the old default backend.
### Description
This bug was introduced in the new backend on 2020-09-08 and first included in a release on 2020-09-30, but the new backend was not the default prior to 0.73.0. The recently-released version 0.73.0 with default settings, and prior versions with an explicit build flag to select the new backend, are vulnerable. The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, under a specific set of circumstances. If those circumstances occur, the bug could allow access to memory addresses up to 2GiB before the start of the heap allocated for the WebAssembly module.
If the heap bound is larger than 2GiB, then it would be possible to read memory from a computable range dependent on the size of the heap's bound.
The impact of this bug is highly dependent on heap implementation; specifically:
* if the heap has bounds checks, and
* does not rely exclusively on guard pages, and
* the heap bound is 2GiB or smaller
then this bug cannot be used to reach memory from another WebAssembly module heap.
The impact of the vulnerability is mitigated if there is no memory mapped in the range accessible using this bug, for example, if there is a 2 GiB guard region before the WebAssembly module heap.
The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, we rely on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.
The issue would thus occur when:
* An i32 value is greater than or equal to 0x8000_0000;
* The value is spilled and reloaded by the register allocator due to high register pressure in the program between the value’s definition and its use;
* The value is produced by an instruction that we know to be "special" in that it zeroes the upper 32 bits of its destination: add, sub, mul, and, or;
* The value is then zero-extended to 64 bits;
* The resulting 64-bit value is used.
Under these circumstances there is a potential sandbox escape when the i32 value is a pointer. The usual code emitted for heap accesses zero-extends the WebAssembly heap address, adds it to a 64-bit heap base, and accesses the resulting address. If the zero-extend becomes a sign-extend, the module could reach backward and access memory up to 2GiB before the start of its heap.
This bug was identified by developers at Fastly following a report from Javier Cabrera Arteaga, KTH Royal Institute of Technology, with support from project Trustful of Stiftelsen för Strategisk Forskning. In addition to supporting the analysis and remediation of this vulnerability, Fastly will publish a related Fastly Security Advisory at [https://www.fastly.com/security-advisories](https://www.fastly.com/security-advisories).
In addition to assessing the nature of the code generation bug in Cranelift, we have also determined that under specific circumstances, both Lucet and Wasmtime using this version of Cranelift may be exploitable.
### General Impact to Lucet
Lucet inherits the heap address computation and bounds-checks of Cranelift, which it uses as its backend code generator. Of particular importance specifically is the address-space layout used by Lucet. In the default configuration for Lucet, only a single module is running, and therefore it is not possible to access memory from another module.
By default, the open source implementation of Lucet uses a maximum heap size of 4 GiB, and an instance slot size of 8 GiB, when invoking an instance from the lucet-wasi command-line tool. These settings are within the range of vulnerability described above, but only a single instance is running, so there is no other instance to read. When embedding the runtime (for example, in a long-running daemon), the default for the heap size as described in the source is 1MB; with this setting, the runtime is not vulnerable.
Lucet allocates its WebAssembly module instances into "instance slots", which are contiguous zones of virtual address space that contain the VM context at the bottom, the WebAssembly heap in the next page after that, a guard region in the middle, and other data at the top: the stack and the globals.
If the instance slot size is less than (max heap) + 2GiB, then the lowest accessible address using the bug will overlap with the prior instance’s heap. If the size of VM context + stack + globals is greater than (4GiB - heap limit), then the highest accessible address using the bug will overlap with this critical data. If neither of these conditions are true, the bug should only result in an access to the prior instance’s guard region.
Generally, if the limit is between 2GiB and 4GiB - ~1MB (depending on stack/global size) and the instance slot size is less than 6GiB, the configuration is vulnerable. If the limit is greater than 4GiB - ~1MB, the configuration is vulnerable regardless of instance slot size. Otherwise, the configuration is not vulnerable.
### General Impact on Wasmtime
In Wasmtime, the same Cranelift heap address computations and heap types are used as above. The memory layout, however, is slightly different, with different outcomes:
* With the mmap implementation impact is mitigated probabilistically if ASLR is enabled.
* With the pooling allocator, the vulnerability only exists if a memory reservation size lower than the default of 6GB is used.
With the default mmap-based instance memory implementation, Wasmtime uses mmap() to allocate a block of memory large enough for the heap and guard region, as specified in its configuration. If the underlying OS implements ASLR (modern Linux, macOS and Windows do) then this address will be randomized, and the region below it will (probabilistically) be free. Hence, the bug is mitigated probabilistically in the default configuration if ASLR is enabled.
If using the pooling allocator, the vulnerability exists if instance memory size (`memory_reservation_size` in InstanceLimit) is strictly less than 6GiB (4 GiB + 2 GiB of guard pages). The default is 6GiB, so the vulnerability is masked in the default pooling allocator configuration.
| {'CVE-2021-32629'} | 2022-04-26T18:11:38Z | 2021-08-25T21:01:55Z | HIGH | 7.2 | {'CWE-125'} | {'https://github.com/RustSec/advisory-db/blob/main/crates/cranelift-codegen/RUSTSEC-2021-0067.md', 'https://www.fastly.com/security-advisories/memory-access-due-to-code-generation-flaw-in-cranelift-module', 'https://github.com/advisories/GHSA-hpqh-2wqx-7qp5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32629', 'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0', 'https://crates.io/crates/cranelift-codegen', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0'} | {'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0'} |
GHSA | GHSA-7f53-fmmv-mfjv | Regular expression denial of service in react-native | A regular expression denial of service (ReDoS) vulnerability in the validateBaseUrl function can cause the application to use excessive resources, become unresponsive, or crash. This was introduced in react-native version 0.59.0 and fixed in version 0.64.1. | {'CVE-2020-1920'} | 2021-07-20T17:35:28Z | 2021-07-20T17:33:28Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-7f53-fmmv-mfjv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1920', 'https://www.npmjs.com/package/react-native', 'https://github.com/facebook/react-native/releases/tag/v0.64.1', 'https://github.com/facebook/react-native/releases/tag/v0.62.3', 'https://github.com/facebook/react-native/commit/ca09ae82715e33c9ac77b3fa55495cf84ba891c7', 'https://securitylab.github.com/advisories/GHSL-2020-293-redos-react-native/'} | null | {'https://github.com/facebook/react-native/commit/ca09ae82715e33c9ac77b3fa55495cf84ba891c7'} | {'https://github.com/facebook/react-native/commit/ca09ae82715e33c9ac77b3fa55495cf84ba891c7'} |
GHSA | GHSA-2r2c-g63r-vccr | Improper Verification of Cryptographic Signature in `node-forge` | ### Impact
RSA PKCS#1 v1.5 signature verification code is not properly checking `DigestInfo` for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest.
### Patches
The issue has been addressed in `node-forge` `1.3.0`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [forge](https://github.com/digitalbazaar/forge)
* Email us at [example email address](mailto:security@digitalbazaar.com) | {'CVE-2022-24773'} | 2022-03-22T19:33:03Z | 2022-03-18T23:10:48Z | MODERATE | 5.3 | {'CWE-347'} | {'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1', 'https://github.com/digitalbazaar/forge/security/advisories/GHSA-2r2c-g63r-vccr', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24773', 'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2', 'https://github.com/advisories/GHSA-2r2c-g63r-vccr'} | null | {'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1', 'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2'} | {'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2', 'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1'} |
GHSA | GHSA-9chx-2vqw-8vq5 | Path Traversal in the Logs plugin for Craft CMS | The Logs plugin before 3.0.4 for Craft CMS allows remote attackers to read arbitrary files via input to actionStream in Controller.php. | {'CVE-2022-23409'} | 2022-02-10T22:32:15Z | 2022-02-01T00:01:00Z | MODERATE | 4.9 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23409', 'https://sec-consult.com/vulnerability-lab/', 'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4', 'http://packetstormsecurity.com/files/165706/Ethercreative-Logs-3.0.3-Path-Traversal.html', 'https://github.com/advisories/GHSA-9chx-2vqw-8vq5', 'https://plugins.craftcms.com/logs'} | null | {'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4'} | {'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4'} |
GHSA | GHSA-4446-656p-f54g | Deserialization of Untrusted Data in Bouncy castle | Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs version prior to version 1.60 contains a CWE-470: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in XMSS/XMSS^MT private key deserialization that can result in Deserializing an XMSS/XMSS^MT private key can result in the execution of unexpected code. This attack appear to be exploitable via A handcrafted private key can include references to unexpected classes which will be picked up from the class path for the executing application. This vulnerability appears to have been fixed in 1.60 and later. | {'CVE-2018-1000613'} | 2022-04-27T17:25:45Z | 2018-10-17T16:23:12Z | CRITICAL | 9.8 | {'CWE-470', 'CWE-502'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00011.html', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000613', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://github.com/advisories/GHSA-4446-656p-f54g', 'https://github.com/bcgit/bc-java/commit/4092ede58da51af9a21e4825fbad0d9a3ef5a223#diff-2c06e2edef41db889ee14899e12bd574', 'https://github.com/bcgit/bc-java/commit/cd98322b171b15b3f88c5ec871175147893c31e6#diff-148a6c098af0199192d6aede960f45dc', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://security.netapp.com/advisory/ntap-20190204-0003/'} | null | {'https://github.com/bcgit/bc-java/commit/cd98322b171b15b3f88c5ec871175147893c31e6#diff-148a6c098af0199192d6aede960f45dc', 'https://github.com/bcgit/bc-java/commit/4092ede58da51af9a21e4825fbad0d9a3ef5a223#diff-2c06e2edef41db889ee14899e12bd574'} | {'https://github.com/bcgit/bc-java/commit/cd98322b171b15b3f88c5ec871175147893c31e6#diff-148a6c098af0199192d6aede960f45dc', 'https://github.com/bcgit/bc-java/commit/4092ede58da51af9a21e4825fbad0d9a3ef5a223#diff-2c06e2edef41db889ee14899e12bd574'} |
GHSA | GHSA-wg6g-ppvx-927h | Prototype Pollution in cached-path-relative | The package cached-path-relative before 1.1.0 is vulnerable to Prototype Pollution via the cache variable that is set as {} instead of Object.create(null) in the cachedPathRelative function, which allows access to the parent prototype properties when the object is used to create the cached relative path. When using the origin path as __proto__, the attribute of the object is accessed instead of a path. **Note:** This vulnerability derives from an incomplete fix in https://security.snyk.io/vuln/SNYK-JS-CACHEDPATHRELATIVE-72573 | {'CVE-2021-23518'} | 2022-01-27T14:27:53Z | 2022-01-27T14:27:53Z | HIGH | 7.3 | {'CWE-1321'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23518', 'https://snyk.io/vuln/SNYK-JS-CACHEDPATHRELATIVE-2342653', 'https://github.com/ashaffer/cached-path-relative/commit/40c73bf70c58add5aec7d11e4f36b93d144bb760', 'https://github.com/advisories/GHSA-wg6g-ppvx-927h'} | null | {'https://github.com/ashaffer/cached-path-relative/commit/40c73bf70c58add5aec7d11e4f36b93d144bb760'} | {'https://github.com/ashaffer/cached-path-relative/commit/40c73bf70c58add5aec7d11e4f36b93d144bb760'} |
GHSA | GHSA-4gr7-qw2q-jxh6 | Cross-site Scripting in Nacos | A Cross Site Scripting (XSS) vulnerability exists in Nacos 2.0.3 in auth/users via the (1) pageSize and (2) pageNo parameters. | {'CVE-2021-44667'} | 2022-03-22T21:37:09Z | 2022-03-12T00:00:27Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-4gr7-qw2q-jxh6', 'https://github.com/alibaba/nacos/issues/7359', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44667', 'https://github.com/alibaba/nacos/commit/cd6d7e33b94f24814701f3faf8b632e5e85444c5'} | null | {'https://github.com/alibaba/nacos/commit/cd6d7e33b94f24814701f3faf8b632e5e85444c5'} | {'https://github.com/alibaba/nacos/commit/cd6d7e33b94f24814701f3faf8b632e5e85444c5'} |
GHSA | GHSA-wrp6-9w7f-3wxg | calibre-web is vulnerable to Cross-site Scripting | calibre-web is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-4170'} | 2022-01-21T23:55:34Z | 2022-01-21T23:55:34Z | HIGH | 7.3 | {'CWE-79'} | {'https://github.com/advisories/GHSA-wrp6-9w7f-3wxg', 'https://github.com/janeczku/calibre-web/commit/7ad419dc8c12180e842a82118f4866ac3d074bc5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4170', 'https://huntr.dev/bounties/ff395101-e392-401d-ab4f-579c63fbf6a0'} | null | {'https://github.com/janeczku/calibre-web/commit/7ad419dc8c12180e842a82118f4866ac3d074bc5'} | {'https://github.com/janeczku/calibre-web/commit/7ad419dc8c12180e842a82118f4866ac3d074bc5'} |
GHSA | GHSA-cw7p-q79f-m2v7 | incomplete JupyterHub logout with simultaneous JupyterLab sessions | ### Impact
Users of JupyterLab with JupyterHub who have multiple JupyterLab tabs open in the same browser session, may see incomplete logout from the single-user server, as fresh credentials (for the single-user server only, not the Hub) reinstated after logout, if another active JupyterLab session is open while the logout takes place.
### Patches
Upgrade to JupyterHub 1.5. For distributed deployments, it is jupyterhub in the _user_ environment that needs patching. There are no patches necessary in the Hub environment.
### Workarounds
The only workaround is to make sure that only one JupyterLab tab is open when you log out. | {'CVE-2021-41247'} | 2022-04-19T19:03:13Z | 2021-11-08T18:02:37Z | LOW | 3.5 | {'CWE-613'} | {'https://github.com/jupyterhub/jupyterhub/commit/5ac9e7f73a6e1020ffddc40321fc53336829fe27', 'https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-cw7p-q79f-m2v7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41247', 'https://github.com/advisories/GHSA-cw7p-q79f-m2v7'} | null | {'https://github.com/jupyterhub/jupyterhub/commit/5ac9e7f73a6e1020ffddc40321fc53336829fe27'} | {'https://github.com/jupyterhub/jupyterhub/commit/5ac9e7f73a6e1020ffddc40321fc53336829fe27'} |
GHSA | GHSA-hvf8-h2qh-37m9 | IPC messages delivered to the wrong frame in Electron | ### Impact
IPC messages sent from the main process to a subframe in the renderer process, through `webContents.sendToFrame`, `event.reply` or when using the `remote` module, can in some cases be delivered to the wrong frame.
If your app does ANY of the following, then it is impacted by this issue:
- Uses `remote`
- Calls `webContents.sendToFrame`
- Calls `event.reply` in an IPC message handler
### Patches
This has been fixed in the following versions:
- 9.4.0
- 10.2.0
- 11.1.0
- 12.0.0-beta.9
### Workarounds
There are no workarounds for this issue.
### For more information
If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org). | {'CVE-2020-26272'} | 2022-04-19T19:02:42Z | 2021-01-28T19:11:34Z | MODERATE | 5.4 | {'CWE-668'} | {'https://github.com/advisories/GHSA-hvf8-h2qh-37m9', 'https://github.com/electron/electron/pull/26875', 'https://www.electronjs.org/releases/stable?version=9#9.4.0', 'https://github.com/electron/electron/security/advisories/GHSA-hvf8-h2qh-37m9', 'https://github.com/electron/electron/commit/07a1c2a3e5845901f7e2eda9506695be58edc73c', 'https://github.com/electron/electron/releases/tag/v9.4.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26272'} | null | {'https://github.com/electron/electron/commit/07a1c2a3e5845901f7e2eda9506695be58edc73c'} | {'https://github.com/electron/electron/commit/07a1c2a3e5845901f7e2eda9506695be58edc73c'} |
GHSA | GHSA-42fp-4hm3-j8r7 | Moderate severity vulnerability that affects moin | Cross-site scripting (XSS) vulnerability in the link dialogue in GUI editor in MoinMoin before 1.9.10 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. | {'CVE-2017-5934'} | 2021-08-31T21:37:19Z | 2019-01-04T17:46:08Z | MODERATE | 6.1 | {'CWE-79'} | {'http://lists.opensuse.org/opensuse-security-announce/2018-10/msg00024.html', 'https://nvd.nist.gov/vuln/detail/CVE-2017-5934', 'https://www.debian.org/security/2018/dsa-4318', 'https://github.com/advisories/GHSA-42fp-4hm3-j8r7', 'https://github.com/moinwiki/moin-1.9/commit/70955a8eae091cc88fd9a6e510177e70289ec024', 'http://moinmo.in/SecurityFixes', 'https://lists.debian.org/debian-lts-announce/2018/10/msg00007.html', 'https://usn.ubuntu.com/3794-1/'} | null | {'https://github.com/moinwiki/moin-1.9/commit/70955a8eae091cc88fd9a6e510177e70289ec024'} | {'https://github.com/moinwiki/moin-1.9/commit/70955a8eae091cc88fd9a6e510177e70289ec024'} |
GHSA | GHSA-x27v-x225-gq8g | Server-Side Request Forgery in Recurly | The Recurly Client Ruby Library before 2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.2, 2.10.4, 2.11.3 is vulnerable to a Server-Side Request Forgery vulnerability in the "Resource#find" method that could result in compromise of API keys or other critical resources. | {'CVE-2017-0905'} | 2021-12-01T21:50:52Z | 2017-12-06T16:43:00Z | CRITICAL | 9.8 | {'CWE-918'} | {'https://dev.recurly.com/page/ruby-updates', 'https://github.com/recurly/recurly-client-ruby/commit/1bb0284d6e668b8b3d31167790ed6db1f6ccc4be', 'https://hackerone.com/reports/288635', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0905', 'https://github.com/advisories/GHSA-x27v-x225-gq8g'} | null | {'https://github.com/recurly/recurly-client-ruby/commit/1bb0284d6e668b8b3d31167790ed6db1f6ccc4be'} | {'https://github.com/recurly/recurly-client-ruby/commit/1bb0284d6e668b8b3d31167790ed6db1f6ccc4be'} |
GHSA | GHSA-hh27-ffr2-f2jc | Open redirect in url-parse | # Overview
Affected versions of npm `url-parse` are vulnerable to URL Redirection to Untrusted Site.
# Impact
Depending on library usage and attacker intent, impacts may include allow/block list bypasses, SSRF attacks, open redirects, or other undesired behavior. | {'CVE-2021-3664'} | 2021-08-10T16:07:08Z | 2021-08-10T16:07:08Z | MODERATE | 6.1 | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3664', 'https://github.com/unshiftio/url-parse/commit/81ab967889b08112d3356e451bf03e6aa0cbb7e0', 'https://github.com/unshiftio/url-parse/issues/205', 'https://huntr.dev/bounties/1625557993985-unshiftio/url-parse', 'https://github.com/advisories/GHSA-hh27-ffr2-f2jc', 'https://github.com/unshiftio/url-parse/issues/206'} | null | {'https://github.com/unshiftio/url-parse/commit/81ab967889b08112d3356e451bf03e6aa0cbb7e0'} | {'https://github.com/unshiftio/url-parse/commit/81ab967889b08112d3356e451bf03e6aa0cbb7e0'} |
GHSA | GHSA-7chv-rrw6-w6fc | XStream is vulnerable to a Remote Command Execution attack | ### Impact
The vulnerability may allow a remote attacker has sufficient rights to execute commands of the host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types.
### Patches
If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.17.
### Workarounds
See [workarounds](https://x-stream.github.io/security.html#workaround) for the different versions covering all CVEs.
### References
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-29505](https://x-stream.github.io/CVE-2021-29505.html).
### Credits
V3geB1rd, white hat hacker from Tencent Security Response Center found and reported the issue to XStream and provided the required information to reproduce it.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [XStream](https://github.com/x-stream/xstream/issues)
* Email us at [XStream Google Group](https://groups.google.com/group/xstream-user)
| {'CVE-2021-29505'} | 2022-04-22T15:48:50Z | 2021-05-18T18:36:27Z | HIGH | 7.5 | {'CWE-94', 'CWE-74', 'CWE-502'} | {'https://www.debian.org/security/2021/dsa-5004', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29505', 'https://lists.debian.org/debian-lts-announce/2021/07/msg00004.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://x-stream.github.io/CVE-2021-29505.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PVPHZA7VW2RRSDCOIPP2W6O5ND254TU7/', 'https://github.com/advisories/GHSA-7chv-rrw6-w6fc', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QGXIU3YDPG6OGTDHMBLAFN7BPBERXREB/', 'https://security.netapp.com/advisory/ntap-20210708-0007/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/22KVR6B5IZP3BGQ3HPWIO2FWWCKT3DHP/', 'https://github.com/x-stream/xstream/security/advisories/GHSA-7chv-rrw6-w6fc', 'https://lists.apache.org/thread.html/r8ee51debf7fd184b6a6b020dc31df25118b0aa612885f12fbe77f04f@%3Cdev.jmeter.apache.org%3E', 'https://github.com/x-stream/xstream/commit/24fac82191292c6ae25f94508d28b9823f83624f'} | null | {'https://github.com/x-stream/xstream/commit/24fac82191292c6ae25f94508d28b9823f83624f'} | {'https://github.com/x-stream/xstream/commit/24fac82191292c6ae25f94508d28b9823f83624f'} |
GHSA | GHSA-r24h-634p-m72x | Validation Bypass in schema-inspector | In schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the `sanitize()` and the `validate()` function used within schema-inspector. | {'CVE-2019-10781'} | 2021-08-30T13:35:23Z | 2020-06-10T20:02:47Z | CRITICAL | 9.8 | {'CWE-668'} | {'https://snyk.io/vuln/SNYK-JS-SCHEMAINSPECTOR-536970', 'https://github.com/Atinux/schema-inspector/commit/345a7b2eed11bb6128421150d65f4f83fdbb737d', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10781', 'https://github.com/advisories/GHSA-r24h-634p-m72x'} | null | {'https://github.com/Atinux/schema-inspector/commit/345a7b2eed11bb6128421150d65f4f83fdbb737d'} | {'https://github.com/Atinux/schema-inspector/commit/345a7b2eed11bb6128421150d65f4f83fdbb737d'} |
GHSA | GHSA-cmx4-p4v5-hmr5 | Server-side request forgery (SSRF) in Apache Batik | Apache Batik is vulnerable to server-side request forgery, caused by improper input validation by the "xlink:href" attributes. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests. | {'CVE-2019-17566'} | 2022-02-09T00:46:46Z | 2022-02-09T00:46:46Z | HIGH | 7.5 | {'CWE-20', 'CWE-918'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/apache/xmlgraphics-batik/commit/bc6078ca949039e2076cd08b4cb169c84c1179b1', 'https://xmlgraphics.apache.org/security.html', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://issues.apache.org/jira/browse/BATIK-1276', 'https://github.com/advisories/GHSA-cmx4-p4v5-hmr5', 'https://lists.apache.org/thread.html/rab94fe68b180d2e2fba97abf6fe1ec83cff826be25f86cd90f047171@%3Ccommits.myfaces.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17566', 'https://lists.apache.org/thread.html/rcab14a9ec91aa4c151e0729966282920423eff50a22759fd21db6509@%3Ccommits.myfaces.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/xmlgraphics-batik/commit/bc6078ca949039e2076cd08b4cb169c84c1179b1'} | {'https://github.com/apache/xmlgraphics-batik/commit/bc6078ca949039e2076cd08b4cb169c84c1179b1'} |
GHSA | GHSA-2wmv-37vq-52g5 | FPE in `tf.raw_ops.UnravelIndex` | ### Impact
An attacker can cause denial of service in applications serving models using `tf.raw_ops.UnravelIndex` by triggering a division by 0:
```python
import tensorflow as tf
tf.raw_ops.UnravelIndex(indices=-1, dims=[1,0,2])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/unravel_index_op.cc#L36) does not check that the tensor subsumed by `dims` is not empty. Hence, if one element of `dims` is 0, the implementation does a division by 0.
### Patches
We have patched the issue in GitHub commit [a776040a5e7ebf76eeb7eb923bf1ae417dd4d233](https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233).
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-37668'} | 2021-08-25T14:42:06Z | 2021-08-25T14:42:06Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2wmv-37vq-52g5', 'https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37668', 'https://github.com/advisories/GHSA-2wmv-37vq-52g5'} | null | {'https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233'} | {'https://github.com/tensorflow/tensorflow/commit/a776040a5e7ebf76eeb7eb923bf1ae417dd4d233'} |
GHSA | GHSA-8hfj-j24r-96c4 | Path Traversal: 'dir/../../filename' in moment.locale | ### Impact
This vulnerability impacts npm (server) users of moment.js, especially if user provided locale string, eg `fr` is directly used to switch moment locale.
### Patches
This problem is patched in 2.29.2, and the patch can be applied to all affected versions (from 1.0.1 up until 2.29.1, inclusive).
### Workarounds
Sanitize user-provided locale name before passing it to moment.js.
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [moment repo](https://github.com/moment/moment)
| {'CVE-2022-24785'} | 2022-04-26T20:56:20Z | 2022-04-04T21:25:48Z | HIGH | 7.5 | {'CWE-27', 'CWE-22'} | {'https://github.com/advisories/GHSA-8hfj-j24r-96c4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24785', 'https://github.com/moment/moment/commit/4211bfc8f15746be4019bba557e29a7ba83d54c5', 'https://www.tenable.com/security/tns-2022-09', 'https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4'} | null | {'https://github.com/moment/moment/commit/4211bfc8f15746be4019bba557e29a7ba83d54c5'} | {'https://github.com/moment/moment/commit/4211bfc8f15746be4019bba557e29a7ba83d54c5'} |
GHSA | GHSA-49pj-69vf-c689 | Incorrect Default Permissions in netaddr | The netaddr gem before 2.0.4 for Ruby has misconfigured file permissions, such that a gem install may result in 0777 permissions in the target filesystem. | {'CVE-2019-17383'} | 2021-08-18T21:45:01Z | 2019-10-14T21:43:19Z | CRITICAL | 9.8 | {'CWE-276'} | {'https://rubygems.org/gems/netaddr/versions', 'https://github.com/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51', 'https://github.com/advisories/GHSA-49pj-69vf-c689', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17383'} | null | {'https://github.com/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51'} | {'https://github.com/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51'} |
GHSA | GHSA-2jx8-v4hv-gx3h | XXE vulnerability in Launch import | | Release Date | Affected Projects | Affected Versions | Access Vector| Security Risk |
|--------------|-------------------|-------------------|---------------|---------------|
| Monday, May 4, 2020| [service-api](https://github.com/reportportal/service-api) | Every version, starting from 3.1.0 | Remote | Medium |
### Impact
Starting from version 3.1.0 we introduced a new feature of JUnit XML launch import. Unfortunately XML parser was not configured properly to prevent XML external entity (XXE) attacks. This allows a user to import a specifically-crafted XML file that uses external entities for extraction of secrets from Report Portal service-api module or server-side request forgery.
Report Portal versions 4.3.12+ and 5.1.1+ disables external entity resolution for theirs XML parser.
We advise our users install the latest releases we built specifically to address this issue.
### Patches
Fixed with https://github.com/reportportal/service-api/pull/1201
### Binary Download
https://bintray.com/epam/reportportal/service-api/5.1.1
https://bintray.com/epam/reportportal/service-api/4.3.12
### Docker Container Download
* RP v4: `docker pull reportportal/service-api:4.3.12`
* RP v5: `docker pull reportportal/service-api:5.1.1`
### Acknowledgement
The issue was reported to Report Portal Team by an external security researcher.
Our Team thanks Julien M. for reporting the issue.
### For more information
If you have any questions or comments about this advisory email us: [support@reportportal.io](mailto:support@reportportal.io) | {'CVE-2020-12642'} | 2021-10-05T17:29:41Z | 2021-06-28T16:45:47Z | HIGH | 7.5 | {'CWE-611'} | {'https://github.com/reportportal/service-api/pull/1201', 'https://github.com/reportportal/reportportal/security/advisories/GHSA-2jx8-v4hv-gx3h', 'https://github.com/advisories/GHSA-2jx8-v4hv-gx3h', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12642', 'https://github.com/reportportal/service-api/commit/da4a012abdcc69f02f4255d81466f1f473b7f418'} | null | {'https://github.com/reportportal/service-api/commit/da4a012abdcc69f02f4255d81466f1f473b7f418'} | {'https://github.com/reportportal/service-api/commit/da4a012abdcc69f02f4255d81466f1f473b7f418'} |
GHSA | GHSA-gh4g-3gm9-5wrq | Cross-Site Scripting in shave | Versions of `shave` prior to 2.5.3 are vulnerable to Cross-Site Scripting. The `shave` package overwrites HTML elements and in doing so fails to properly encode the output. If encoded HTML input is passed into `shave` the output will be decoded which may lead to Cross-Site Scripting.
## Recommendation
Upgrade to version 2.5.3 or later. | {'CVE-2019-12313'} | 2021-08-04T16:06:35Z | 2019-05-29T18:38:08Z | MODERATE | 6.1 | {'CWE-79'} | {'https://www.npmjs.com/advisories/822', 'https://github.com/advisories/GHSA-gh4g-3gm9-5wrq', 'https://github.com/dollarshaveclub/shave/commit/da7371b0531ba14eae48ef1bb1456a3de4cfa954#diff-074799b511e4b61923dfd3f2a3bf9b54R67', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12313', 'https://github.com/dollarshaveclub/shave/compare/852b537...da7371b'} | null | {'https://github.com/dollarshaveclub/shave/commit/da7371b0531ba14eae48ef1bb1456a3de4cfa954#diff-074799b511e4b61923dfd3f2a3bf9b54R67'} | {'https://github.com/dollarshaveclub/shave/commit/da7371b0531ba14eae48ef1bb1456a3de4cfa954#diff-074799b511e4b61923dfd3f2a3bf9b54R67'} |
GHSA | GHSA-rr8m-29g8-8cgc | SQL Injection in Fork CMS | Fork CMS is vulnerable to SQL injection through marking blog comments on bulk as spam in versions prior to 5.11.1. | {'CVE-2022-1064'} | 2022-04-05T20:55:35Z | 2022-03-26T00:00:32Z | HIGH | 8.8 | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1064', 'https://github.com/forkcms/forkcms/commit/6aca30e10b4181534f73f96d6e2ebeb45ec15069', 'https://github.com/advisories/GHSA-rr8m-29g8-8cgc', 'https://huntr.dev/bounties/2f664985-c5fc-485b-b4fc-4c401be2cf40'} | null | {'https://github.com/forkcms/forkcms/commit/6aca30e10b4181534f73f96d6e2ebeb45ec15069'} | {'https://github.com/forkcms/forkcms/commit/6aca30e10b4181534f73f96d6e2ebeb45ec15069'} |
GHSA | GHSA-2xhg-w2g5-w95x | CSV Injection in symfony/serializer | Description
-----------
CSV Injection, also known as Formula Injection, occurs when websites embed untrusted input inside CSV files. When a spreadsheet program opens a CSV, any cell starting with `=` is interpreted by the software as a formula and could be abused by an attacker.
In Symfony 4.1, we've added the opt-in `csv_escape_formulas` option in `CsvEncoder`, to prefix all cells starting by `=`, `+`, `-` or `@` by a tab `\t`.
Since then, OWASP added 2 chars in that list:
- Tab (0x09)
- Carriage return (0x0D)
This makes our previous prefix char (Tab `\t`) part of the vulnerable characters, and [OWASP suggests](https://owasp.org/www-community/attacks/CSV_Injection) using the single quote `'` for prefixing the value.
Resolution
----------
Symfony now follows the OWASP recommendations and use the single quote `'` to prefix formulas and adds the prefix to cells starting by `\t`, `\r` as well as `=`, `+`, `-` and `@`.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8) for branch 4.4.
Credits
-------
We would like to thank Jake Barwell for reporting the issue and Jérémy Derussé for fixing the issue.
| {'CVE-2021-41270'} | 2022-04-19T19:03:15Z | 2021-11-24T21:01:23Z | MODERATE | 6.5 | {'CWE-1236'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QSREFD2TJT5LWKM6S4MD3W26NQQ5WJUP/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41270', 'https://github.com/symfony/symfony/releases/tag/v5.3.12', 'https://github.com/symfony/symfony/security/advisories/GHSA-2xhg-w2g5-w95x', 'https://github.com/symfony/symfony/pull/44243', 'https://github.com/advisories/GHSA-2xhg-w2g5-w95x', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3BPT4SF6SIXFMZARDWED5T32J7JEH3EP/', 'https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8'} | null | {'https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8'} | {'https://github.com/symfony/symfony/commit/3da6f2d45e7536ccb2a26f52fbaf340917e208a8'} |
GHSA | GHSA-273r-rm8g-7f3x | Uncaught Exception in mercurius | ### Impact
Any users from Mercurius@8.10.0 to 8.11.1 are subjected to a denial of service attack by sending a malformed JSON to `/graphql` unless they are using a custom error handler.
### Patches
The vulnerability has been fixed in https://github.com/mercurius-js/mercurius/pull/678 and shipped as v8.11.2.
### Workarounds
Use a custom error handler.
### References
See https://github.com/mercurius-js/mercurius/issues/677
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/mercurius-js/mercurius
* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)
| {'CVE-2021-43801'} | 2021-12-14T15:26:38Z | 2021-12-13T21:33:04Z | HIGH | 7.5 | {'CWE-754'} | {'https://github.com/mercurius-js/mercurius/security/advisories/GHSA-273r-rm8g-7f3x', 'https://github.com/advisories/GHSA-273r-rm8g-7f3x', 'https://github.com/mercurius-js/mercurius/pull/678/commits/732b2f895312da8deadd7b173dcd2d141d54b223', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43801', 'https://github.com/mercurius-js/mercurius/issues/677'} | null | {'https://github.com/mercurius-js/mercurius/pull/678/commits/732b2f895312da8deadd7b173dcd2d141d54b223'} | {'https://github.com/mercurius-js/mercurius/pull/678/commits/732b2f895312da8deadd7b173dcd2d141d54b223'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.