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-977j-xj7q-2jr9 | Segmentation faultin TensorFlow when converting a Python string to `tf.float16` | ### Impact
Converting a string (from Python) to a `tf.float16` value results in a segmentation fault in eager mode as the format checks for this use case are only in the graph mode.
This issue can lead to denial of service in inference/training where a malicious attacker can send a data point which contains a string instead of a `tf.float16` value.
Similar effects can be obtained by manipulating saved models and checkpoints whereby replacing a scalar `tf.float16` value with a scalar string will trigger this issue due to automatic conversions.
This can be easily reproduced by `tf.constant("hello", tf.float16)`, if eager execution is enabled.
### Patches
We have patched the vulnerability in GitHub commit [5ac1b9](https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf).
We are additionally releasing TensorFlow 1.15.1 and 2.0.1 with this vulnerability patched.
TensorFlow 2.1.0 was released after we fixed the issue, thus it is not affected.
We encourage users to switch to TensorFlow 1.15.1, 2.0.1 or 2.1.0.
### For more information
Please consult [`SECURITY.md`](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2020-5215'} | 2021-01-08T20:32:01Z | 2020-01-28T21:32:29Z | HIGH | 5 | {'CWE-754'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-977j-xj7q-2jr9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5215', 'https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf', 'https://github.com/advisories/GHSA-977j-xj7q-2jr9', 'https://github.com/tensorflow/tensorflow/releases/tag/v1.15.2', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.0.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf'} | {'https://github.com/tensorflow/tensorflow/commit/5ac1b9e24ff6afc465756edf845d2e9660bd34bf'} |
GHSA | GHSA-r478-c2pc-m7gx | DNS reply verification issue in dnslinb | The dnslib package through 0.9.16 for Python does not verify that the ID value in a DNS reply matches an ID value in a query. | {'CVE-2022-22846'} | 2022-01-19T19:58:20Z | 2022-01-12T20:07:10Z | HIGH | 7.5 | null | {'https://github.com/paulc/dnslib/issues/30', 'https://github.com/paulc/dnslib/commit/76e8677699ed098387d502c57980f58da642aeba', 'https://github.com/advisories/GHSA-r478-c2pc-m7gx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22846'} | null | {'https://github.com/paulc/dnslib/commit/76e8677699ed098387d502c57980f58da642aeba'} | {'https://github.com/paulc/dnslib/commit/76e8677699ed098387d502c57980f58da642aeba'} |
GHSA | GHSA-v6fx-752r-ccp2 | CSRF on PgHero gem | The PgHero gem through 2.6.0 for Ruby allows CSRF. | {'CVE-2020-16253'} | 2021-09-23T18:37:56Z | 2020-08-05T14:53:43Z | HIGH | 8.1 | {'CWE-352'} | {'https://github.com/ankane/pghero/issues/330', 'https://rubygems.org/gems/pghero', 'https://github.com/ankane/pghero/commit/14b67b32fed19a30aaf9826ee72f2a29cda604e9', 'https://github.com/advisories/GHSA-v6fx-752r-ccp2', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/pghero/CVE-2020-16253.yml', 'https://github.com/ankane/pghero/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16253'} | null | {'https://github.com/ankane/pghero/commit/14b67b32fed19a30aaf9826ee72f2a29cda604e9'} | {'https://github.com/ankane/pghero/commit/14b67b32fed19a30aaf9826ee72f2a29cda604e9'} |
GHSA | GHSA-4449-hg37-77v8 | Command injection in total.js | There is a command injection vulnerability that affects the package total.js before version 3.4.7. The issue occurs in the image.pipe and image.stream functions. The type parameter is used to build the command that is then executed using child_process.spawn. The issue occurs because child_process.spawn is called with the option shell set to true and because the type parameter is not properly sanitized. | {'CVE-2020-28494'} | 2021-07-28T18:57:24Z | 2021-02-05T20:43:27Z | HIGH | 8.6 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28494', 'https://github.com/advisories/GHSA-4449-hg37-77v8', 'https://www.npmjs.com/package/total.js', 'https://snyk.io/vuln/SNYK-JS-TOTALJS-1046672', 'https://github.com/totaljs/framework/commit/6192491ab2631e7c1d317c221f18ea613e2c18a5'} | null | {'https://github.com/totaljs/framework/commit/6192491ab2631e7c1d317c221f18ea613e2c18a5'} | {'https://github.com/totaljs/framework/commit/6192491ab2631e7c1d317c221f18ea613e2c18a5'} |
GHSA | GHSA-qffw-8wg7-h665 | Command injection in git-interface | A command injection vulnerability exists in git-interface in the GitHub repository yarkeev/git-interface prior to 2.1.2. If both the git remote and destination directory are provided by user input, then the use of an `--upload-pack` command-line argument feature of git is also supported for `git clone`, which would then allow for any operating system command to be spawned by the attacker. | {'CVE-2022-1440'} | 2022-04-29T17:22:44Z | 2022-04-23T00:03:01Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://huntr.dev/bounties/cdc25408-d3c1-4a9d-bb45-33b12a715ca1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1440', 'https://github.com/yarkeev/git-interface/commit/f828aa790016fee3aa667f7b44cf94bf0aa8c60d', 'https://github.com/advisories/GHSA-qffw-8wg7-h665'} | null | {'https://github.com/yarkeev/git-interface/commit/f828aa790016fee3aa667f7b44cf94bf0aa8c60d'} | {'https://github.com/yarkeev/git-interface/commit/f828aa790016fee3aa667f7b44cf94bf0aa8c60d'} |
GHSA | GHSA-h3rx-g5c9-8q4x | Prototype Pollution in bmoor | The package bmoor before 0.8.12 are vulnerable to Prototype Pollution via the set function. | {'CVE-2020-7736'} | 2021-07-28T19:52:39Z | 2021-05-10T18:37:26Z | HIGH | 7.3 | {'CWE-1321'} | {'https://github.com/b-heilman/bmoor/commit/7d4a086a1dc3ef11ed0b323824d02348734b7da5', 'https://github.com/advisories/GHSA-h3rx-g5c9-8q4x', 'https://www.npmjs.com/package/bmoor', 'https://snyk.io/vuln/SNYK-JS-BMOOR-598664', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7736'} | null | {'https://github.com/b-heilman/bmoor/commit/7d4a086a1dc3ef11ed0b323824d02348734b7da5'} | {'https://github.com/b-heilman/bmoor/commit/7d4a086a1dc3ef11ed0b323824d02348734b7da5'} |
GHSA | GHSA-24m3-w8g9-jwpq | Information disclosure of source code in SimpleSAMLphp | ### Background
The module controller in `SimpleSAML\Module` that processes requests for pages
hosted by modules, has code to identify paths ending with `.php` and process
those as PHP code. If no other suitable way of handling the given path exists it
presents the file to the browser.
### Description
The check to identify paths ending with `.php` does not account for uppercase
letters. If someone requests a path ending with e.g. `.PHP` and the server is
serving the code from a case-insensitive file system, such as on Windows, the
processing of the PHP code does not occur, and the source code is instead
presented to the browser.
### Affected versions
SimpleSAMLphp versions **1.18.5 and older**.
### Impact
An attacker may use this issue to gain access to the source code in third-party
modules that is meant to be private, or even sensitive. However, the attack
surface is considered small, as the attack will only work when SimpleSAMLphp
serves such content from a file system that is not case-sensitive, such as on
Windows.
### Resolution
Upgrade the SimpleSAMLphp installation to version **1.18.6**.
### Credit
This vulnerability was discovered and reported by Sławek Naczyński. | {'CVE-2020-5301'} | 2022-04-19T19:02:25Z | 2020-04-22T20:59:44Z | LOW | 3 | {'CWE-200', 'CWE-178'} | {'https://github.com/simplesamlphp/simplesamlphp/security/advisories/GHSA-24m3-w8g9-jwpq', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5301', 'https://github.com/advisories/GHSA-24m3-w8g9-jwpq', 'https://github.com/simplesamlphp/simplesamlphp/commit/47968d26a2fd3ed52da70dc09210921d612ce44e'} | null | {'https://github.com/simplesamlphp/simplesamlphp/commit/47968d26a2fd3ed52da70dc09210921d612ce44e'} | {'https://github.com/simplesamlphp/simplesamlphp/commit/47968d26a2fd3ed52da70dc09210921d612ce44e'} |
GHSA | GHSA-grc3-8q8m-4j7c | Improper privilege handling in Apache Accumulo | Apache Accumulo versions 1.5.0 through 1.10.0 and version 2.0.0 do not properly check the return value of some policy enforcement functions before permitting an authenticated user to perform certain administrative operations. Specifically, the return values of the 'canFlush' and 'canPerformSystemActions' security functions are not checked in some instances, therefore allowing an authenticated user with insufficient permissions to perform the following actions: flushing a table, shutting down Accumulo or an individual tablet server, and setting or removing system-wide Accumulo configuration properties. | {'CVE-2020-17533'} | 2022-02-09T22:37:59Z | 2022-02-09T22:37:59Z | HIGH | 8.1 | {'CWE-280', 'CWE-732'} | {'http://www.openwall.com/lists/oss-security/2020/12/29/1', 'https://lists.apache.org/thread.html/rf8c1a787b6951d3dacb9ec58f0bf1633790c91f54ff10c6f8ff9d8ed%40%3Cuser.accumulo.apache.org%3E', 'https://github.com/advisories/GHSA-grc3-8q8m-4j7c', 'https://lists.apache.org/thread.html/rf8c1a787b6951d3dacb9ec58f0bf1633790c91f54ff10c6f8ff9d8ed@%3Cannounce.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17533', 'https://github.com/apache/accumulo/commit/877ad502f6857e48342664e4b0ce83db74e4cda4'} | null | {'https://github.com/apache/accumulo/commit/877ad502f6857e48342664e4b0ce83db74e4cda4'} | {'https://github.com/apache/accumulo/commit/877ad502f6857e48342664e4b0ce83db74e4cda4'} |
GHSA | GHSA-xc47-3rch-cv57 | Improper Access Control in snipe-it | Users with no system permissions are able to see and create personal access tokens | {'CVE-2022-0178'} | 2022-01-26T20:24:23Z | 2022-01-26T20:24:23Z | MODERATE | 5.4 | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0178', 'https://huntr.dev/bounties/81c6b974-d0b3-410b-a902-8324a55b1368', 'https://github.com/advisories/GHSA-xc47-3rch-cv57', 'https://github.com/snipe/snipe-it/commit/0e5ef53c352754de2778ffa20c85da15fd6f7ae0'} | null | {'https://github.com/snipe/snipe-it/commit/0e5ef53c352754de2778ffa20c85da15fd6f7ae0'} | {'https://github.com/snipe/snipe-it/commit/0e5ef53c352754de2778ffa20c85da15fd6f7ae0'} |
GHSA | GHSA-hgc3-hp6x-wpgx | Antilles Dependency Confusion Vulnerability | ### Potential Impact:
Remote code execution.
### Scope of Impact:
Open-source project specific.
### Summary Description:
A dependency confusion vulnerability was reported in the Antilles open-source software prior to version 1.0.1 that could allow for remote code execution during installation due to a package listed in requirements.txt not existing in the public package index (PyPi).
MITRE classifies this weakness as an Uncontrolled Search Path Element (CWE-427) in which a private package dependency may be replaced by an unauthorized package of the same name published to a well-known public repository such as PyPi.
The configuration has been updated to only install components built by Antilles, removing all other public package indexes. Additionally, the antilles-tools dependency has been published to PyPi.
### Mitigation Strategy for Customers (what you should do to protect yourself):
Remove previous versions of Antilles as a precautionary measure and Update to version 1.0.1 or later.
### Acknowledgement:
The Antilles team thanks Kotko Vladyslav for reporting this issue.
### References:
https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9
| {'CVE-2021-3840'} | 2021-11-17T21:17:30Z | 2021-11-03T17:36:22Z | HIGH | 8.8 | {'CWE-427'} | {'https://github.com/advisories/GHSA-hgc3-hp6x-wpgx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3840', 'https://github.com/lenovo/Antilles/security/advisories/GHSA-hgc3-hp6x-wpgx', 'https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9'} | null | {'https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9'} | {'https://github.com/lenovo/Antilles/commit/c7b9c5740908b343aceefe69733d9972e64df0b9'} |
GHSA | GHSA-976r-qfjj-c24w | Command injection via Celery broker in Apache Airflow | An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attacker can connect to the broker (Redis, RabbitMQ) directly, it is possible to inject commands, resulting in the celery worker running arbitrary commands. | {'CVE-2020-11981'} | 2022-03-21T22:48:38Z | 2020-07-27T16:57:33Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://github.com/advisories/GHSA-976r-qfjj-c24w', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11981', 'https://issues.apache.org/jira/browse/AIRFLOW-6351', 'https://lists.apache.org/thread.html/r7255cf0be3566f23a768e2a04b40fb09e52fcd1872695428ba9afe91%40%3Cusers.airflow.apache.org%3E', 'https://github.com/apache/airflow/commit/afa4b11fddfdbadb048f742cf66d5c21c675a5c8'} | null | {'https://github.com/apache/airflow/commit/afa4b11fddfdbadb048f742cf66d5c21c675a5c8'} | {'https://github.com/apache/airflow/commit/afa4b11fddfdbadb048f742cf66d5c21c675a5c8'} |
GHSA | GHSA-qcj7-g2j5-g7r3 | In Bouncy Castle JCE Provider ECDSA does not fully validate ASN.1 encoding of signature on verification | In the Bouncy Castle JCE Provider version 1.55 and earlier ECDSA does not fully validate ASN.1 encoding of signature on verification. It is possible to inject extra elements in the sequence making up the signature and still have it validate, which in some cases may allow the introduction of 'invisible' data into a signed structure. | {'CVE-2016-1000342'} | 2022-04-27T13:28:11Z | 2018-10-17T16:24:12Z | HIGH | 7.5 | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2016-1000342', 'https://github.com/bcgit/bc-java/commit/843c2e60f67d71faf81d236f448ebbe56c62c647#diff-25c3c78db788365f36839b3f2d3016b9', 'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/advisories/GHSA-qcj7-g2j5-g7r3', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://usn.ubuntu.com/3727-1/', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00009.html'} | null | {'https://github.com/bcgit/bc-java/commit/843c2e60f67d71faf81d236f448ebbe56c62c647#diff-25c3c78db788365f36839b3f2d3016b9'} | {'https://github.com/bcgit/bc-java/commit/843c2e60f67d71faf81d236f448ebbe56c62c647#diff-25c3c78db788365f36839b3f2d3016b9'} |
GHSA | GHSA-7733-hjv6-4h47 | Cross-Site Scripting in ternary conditional operator | > ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C`(5.0)
> * CWE-79
---
:information_source: This vulnerability has been fixed in May 2019 already, CVE and GHSA were assigned later in October 2020
---
### Problem
It has been discovered that the Fluid Engine (package `typo3fluid/fluid`) is vulnerable to cross-site scripting when making use of the ternary conditional operator in templates like the following.
```
{showFullName ? fullName : defaultValue}
```
### Solution
Update to versions 2.0.5, 2.1.4, 2.2.1, 2.3.5, 2.4.1, 2.5.5 or 2.6.1 of this `typo3fluid/fluid` package that fix the problem described.
Updated versions of this package are bundled in following TYPO3 (`typo3/cms-core`) releases:
* TYPO3 v8.7.25 (using `typo3fluid/fluid` v2.5.5)
* TYPO3 v9.5.6 (using `typo3fluid/fluid` v2.6.1)
### Credits
Thanks to Bill Dagou who reported this issue and to TYPO3 core merger Claus Due who fixed the issue.
### References
* [TYPO3-CORE-SA-2019-013](https://typo3.org/security/advisory/typo3-core-sa-2019-013) | {'CVE-2020-15241'} | 2022-04-19T19:02:36Z | 2020-10-08T19:55:53Z | MODERATE | 4.7 | {'CWE-601', 'CWE-79'} | {'https://github.com/advisories/GHSA-7733-hjv6-4h47', 'https://github.com/TYPO3/Fluid/security/advisories/GHSA-7733-hjv6-4h47', 'https://github.com/TYPO3/Fluid/commit/9ef6a8ffff2e812025fc0701b4ce72eea6911a3d', 'https://typo3.org/security/advisory/typo3-core-sa-2019-013', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15241'} | null | {'https://github.com/TYPO3/Fluid/commit/9ef6a8ffff2e812025fc0701b4ce72eea6911a3d'} | {'https://github.com/TYPO3/Fluid/commit/9ef6a8ffff2e812025fc0701b4ce72eea6911a3d'} |
GHSA | GHSA-6vqp-h455-42mr | Uncontrolled Memory Allocation in Apache PDFBox | A carefully crafted PDF file can trigger an OutOfMemory-Exception while loading the file. This issue affects Apache PDFBox version 2.0.22 and prior 2.0.x versions. | {'CVE-2021-27906'} | 2022-04-22T18:27:47Z | 2021-05-13T22:30:13Z | MODERATE | 5.5 | {'CWE-789'} | {'https://github.com/apache/pdfbox/commit/8c47be1011c11dc47300faecffd8ab32fba3646f', 'https://lists.apache.org/thread.html/r4cbc3f6981cd0a1a482531df9d44e4c42a7f63342a7ba78b7bff8a1b@%3Cnotifications.james.apache.org%3E', 'https://issues.apache.org/jira/browse/PDFBOX-5112', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6PT72QOFDXLJ7PLTN66EMG5EHPTE7TFZ/', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/rc69140d894c6a9c67a8097a25656cce59b46a5620c354ceba10543c3@%3Cnotifications.ofbiz.apache.org%3E', 'https://lists.apache.org/thread.html/rf35026148ccc0e1af133501c0d003d052883fcc65107b3ff5d3b61cd@%3Cusers.pdfbox.apache.org%3E', 'https://lists.apache.org/thread.html/r9ffe179385637b0b5cbdabd0246118005b4b8232909d2d14cd68ccd3@%3Ccommits.ofbiz.apache.org%3E', 'https://lists.apache.org/thread.html/r1218e60c32829f76943ecaca79237120c2ec1ab266459d711a578b50@%3Cdev.pdfbox.apache.org%3E', 'https://lists.apache.org/thread.html/r5c8e2125d18af184c80f7a986fbe47eaf0d30457cd450133adc235ac@%3Ccommits.ofbiz.apache.org%3E', 'https://lists.apache.org/thread.html/rf35026148ccc0e1af133501c0d003d052883fcc65107b3ff5d3b61cd%40%3Cusers.pdfbox.apache.org%3E', 'https://lists.apache.org/thread.html/raa35746227f3f8d50fff1db9899524423a718f6f35cd39bd4769fa6c@%3Cnotifications.ofbiz.apache.org%3E', 'https://github.com/advisories/GHSA-6vqp-h455-42mr', 'https://lists.apache.org/thread.html/r54594251369e14c185da9662a5340a52afbbdf75d61c9c3a69c8f2e8@%3Cdev.pdfbox.apache.org%3E', 'https://lists.apache.org/thread.html/re1e35881482e07dc2be6058d9b44483457f36133cac67956686ad9b9@%3Cnotifications.ofbiz.apache.org%3E', 'https://lists.apache.org/thread.html/r1d268642f8b52456ee8f876b888b8ed7a9e9568c7770789f3ded7f9e@%3Ccommits.ofbiz.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6KDA2U4KL2N3XT3PM4ZJEBBA6JJIH2G4/', 'https://lists.apache.org/thread.html/rdf78aef4793362e778e21e34328b0456e302bde4b7e74f229df0ee04@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r7ee634c21816c69ce829d0c41f35afa2a53a99bdd3c7cce8644fdc0e@%3Cnotifications.ofbiz.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r6e067a6d83ccb6892d0ff867bd216704f21fb0b6a854dea34be04f12@%3Cnotifications.ofbiz.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2AVLKAHFMPH72TTP25INPZPGX5FODK3H/', 'http://www.openwall.com/lists/oss-security/2021/03/19/10', 'https://lists.apache.org/thread.html/r64982b768c8a2220b07aaf813bd099a9863de0d13eb212fd4efe208f@%3Cusers.pdfbox.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27906', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/pdfbox/commit/8c47be1011c11dc47300faecffd8ab32fba3646f'} | {'https://github.com/apache/pdfbox/commit/8c47be1011c11dc47300faecffd8ab32fba3646f'} |
GHSA | GHSA-72m5-fvvv-55m6 | Observable Differences in Behavior to Error Inputs in Bouncy Castle | In Legion of the Bouncy Castle BC before 1.55 and BC-FJA before 1.0.2, attackers can obtain sensitive information about a private exponent because of Observable Differences in Behavior to Error Inputs. This occurs in org.bouncycastle.crypto.encodings.OAEPEncoding. Sending invalid ciphertext that decrypts to a short payload in the OAEP Decoder could result in the throwing of an early exception, potentially leaking some information about the private exponent of the RSA private key performing the encryption. | {'CVE-2020-26939'} | 2021-05-26T13:31:25Z | 2021-04-22T16:16:49Z | MODERATE | 5.3 | {'CWE-203'} | {'https://lists.apache.org/thread.html/r8c36ba34e80e05eecb1f80071cc834d705616f315b634ec0c7d8f42e@%3Cissues.solr.apache.org%3E', 'https://github.com/bcgit/bc-java/commit/930f8b274c4f1f3a46e68b5441f1e7fadb57e8c1', 'https://security.netapp.com/advisory/ntap-20201202-0005/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00007.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26939', 'https://github.com/bcgit/bc-java/wiki/CVE-2020-26939', 'https://github.com/advisories/GHSA-72m5-fvvv-55m6'} | null | {'https://github.com/bcgit/bc-java/commit/930f8b274c4f1f3a46e68b5441f1e7fadb57e8c1'} | {'https://github.com/bcgit/bc-java/commit/930f8b274c4f1f3a46e68b5441f1e7fadb57e8c1'} |
GHSA | GHSA-7q36-4xx7-xcxf | Untrusted data can lead to DoS attack due to hash collisions and stack overflow in MessagePack | ### Impact
When this library is used to deserialize messagepack data from an untrusted source, there is a risk of a denial of service attack by either of two vectors:
1. hash collisions - leading to large CPU consumption disproportionate to the size of the data being deserialized.
1. stack overflow - leading to the deserializing process crashing.
### Patches
The following steps are required to mitigate this risk.
1. Upgrade to a version of the library where a fix is available
1. Add code to your application to put MessagePack into the defensive `UntrustedData` mode.
1. Identify all MessagePack extensions that implement `IMessagePackFormatter<T>` implementations that do not ship with the MessagePack library to include the security mitigations. This includes those acquired from 3rd party packages and classes included directly into your project. Any AOT formatters generated with the MPC tool must be regenerated with the patched version of mpc.
1. Review your messagepack-serializable data structures for hash-based collections that use custom or unusual types for the hashed key. See below for details on handling such situations.
Review the `MessagePackSecurity` class to tweak any settings as necessary to strike the right balance between performance, functionality, and security.
Specialized `IEqualityComparer<T>` implementations provide the hash collision resistance.
Each type of hashed key may require a specialized implementation of its own.
The patched MessagePack library includes many such implementations for primitive types commonly used as keys in hash-based collections.
If your data structures use custom types as keys in these hash-based collections,
putting MessagePack in `UntrustedData` mode may lead the deserializer to throw an exception
because no safe `IEqualityComparer<T>` is available for your custom `T` type.
You can provide your own safe implementation by deriving from the `MessagePackSecurity` class
and overriding the `GetHashCollisionResistantEqualityComparer<T>()` method to return your own
custom implementation when `T` matches your type, and fallback to `return base.GetHashCollisionResistantEqualityComparer<T>();` for types you do not have custom implementations for.
Unrelated to this advisory, but as general security guidance, you should also avoid the Typeless serializer/formatters/resolvers for untrusted data as that opens the door for the untrusted data to potentially deserialize unanticipated types that can compromise security.
#### MessagePack 1.x users
1. Upgrade to any 1.9.x version.
1. When deserializing untrusted data, put MessagePack into a more secure mode with:
```cs
MessagePackSecurity.Active = MessagePackSecurity.UntrustedData;
```
In MessagePack v1.x this is a static property and thus the security level is shared by the entire process or AppDomain.
Use MessagePack v2.1 or later for better control over the security level for your particular use.
1. Any code produced by mpc should be regenerated with the mpc tool with the matching (patched) version. Such generated code usually is written to a file called `Generated.cs`. A patched `Generated.cs` file will typically reference the `MessagePackSecurity` class.
Review any custom-written `IMessagePackFormatter<T>` implementations in your project or that you might use from 3rd party packages to ensure they also utilize the `MessagePackSecurity` class as required.
In particular, a formatter that deserializes an object (as opposed to a primitive value) should wrap the deserialization in a `using (MessagePackSecurity.DepthStep())` block. For example:
```cs
public MyObject Deserialize(ref MessagePackReader reader, MessagePackSerializerOptions options)
{
if (reader.TryReadNil())
{
return default;
}
else
{
using (MessagePackSecurity.DepthStep()) // STACK OVERFLOW MITIGATION
{
MyObject o = new MyObject();
// deserialize members of the object here.
return o;
}
}
}
```
If your custom formatter creates hash-based collections (e.g. `Dictionary<K, V>` or `HashSet<T>`) where the hashed key comes from the messagepack data, always instantiate your collection using `MessagePackSecurity.Active.GetEqualityComparer<T>()` as the equality comparer:
```cs
var collection = new HashSet<T>(MessagePackSecurity.Active.GetEqualityComparer<T>());
```
This ensures that when reading untrusted data, you will be using a collision-resistent hash algorithm.
Learn more about [best security practices when reading untrusted data with MessagePack 1.x](https://github.com/neuecc/MessagePack-CSharp/tree/v1.x#security).
#### MessagePack 2.x users
1. Upgrade to any 2.1.x or later version.
1. When deserializing untrusted data, put MessagePack into a more secure mode by configuring your `MessagePackSerializerOptions.Security` property:
```cs
var options = MessagePackSerializerOptions.Standard
.WithSecurity(MessagePackSecurity.UntrustedData);
// Pass the options explicitly for the greatest control.
T object = MessagePackSerializer.Deserialize<T>(data, options);
// Or set the security level as the default.
MessagePackSerializer.DefaultOptions = options;
```
1. Any code produced by mpc should be regenerated with the mpc tool with the matching (patched) version. Such generated code usually is written to a file called `Generated.cs`. A patched `Generated.cs` file will typically reference the `Security` member on the `MessagePackSerializerOptions` parameter.
Review any custom-written `IMessagePackFormatter<T>` implementations in your project or that you might use from 3rd party packages to ensure they also utilize the `MessagePackSecurity` class as required.
In particular, a formatter that deserializes an object (as opposed to a primitive value) should call `options.Security.DepthStep(ref reader);` before deserializing the object's members, and be sure to revert the depth step with `reader.Depth--;` before exiting the method. For example:
```cs
public MyObject Deserialize(ref MessagePackReader reader, MessagePackSerializerOptions options)
{
if (reader.TryReadNil())
{
return default;
}
else
{
options.Security.DepthStep(ref reader); // STACK OVERFLOW MITIGATION, line 1
try
{
MyObject o = new MyObject();
// deserialize members of the object here.
return o;
}
finally
{
reader.Depth--; // STACK OVERFLOW MITIGATION, line 2
}
}
}
```
If your custom formatter creates hash-based collections (e.g. `Dictionary<K, V>` or `HashSet<T>`) where the hashed key comes from the messagepack data, always instantiate your collection using `options.Security.GetEqualityComparer<TKey>()` as the equality comparer:
```cs
var collection = new HashSet<T>(options.Security.GetEqualityComparer<T>());
```
This ensures that when reading untrusted data, you will be using a collision-resistent hash algorithm.
Learn more about [best security practices when reading untrusted data with MessagePack 2.x](https://github.com/neuecc/MessagePack-CSharp#security).
### Workarounds
The security vulnerabilities are in the formatters.
Avoiding the built-in formatters entirely in favor of reading messagepack primitive data directly
or relying on carefully written custom formatters can provide a workaround.
MessagePack v1.x users may utilize the `MessagePackBinary` static class directly to read the data they expect.
MessagePack v2.x users may utilize the `MessagePackReader` struct directly to read the data they expect.
### References
Learn more about best security practices when reading untrusted data with [MessagePack 1.x](https://github.com/neuecc/MessagePack-CSharp/tree/v1.x#security) or [MessagePack 2.x](https://github.com/neuecc/MessagePack-CSharp#security).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [MessagePack-CSharp](https://github.com/neuecc/MessagePack-CSharp/issues/new/choose)
* [Email us](mailto:andrewarnott@gmail.com) | {'CVE-2020-5234'} | 2021-04-06T17:54:57Z | 2020-01-31T17:59:20Z | MODERATE | 4.8 | {'CWE-121'} | {'https://github.com/neuecc/MessagePack-CSharp/security/advisories/GHSA-7q36-4xx7-xcxf', 'https://github.com/advisories/GHSA-7q36-4xx7-xcxf', 'https://github.com/aspnet/Announcements/issues/405', 'https://github.com/neuecc/MessagePack-CSharp/commit/f88684078698386df02204f13faeff098a61f007', 'https://github.com/neuecc/MessagePack-CSharp/commit/56fa86219d01d0a183babbbbcb34abbdea588a02', 'https://github.com/neuecc/MessagePack-CSharp/issues/810', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5234'} | null | {'https://github.com/neuecc/MessagePack-CSharp/commit/f88684078698386df02204f13faeff098a61f007', 'https://github.com/neuecc/MessagePack-CSharp/commit/56fa86219d01d0a183babbbbcb34abbdea588a02'} | {'https://github.com/neuecc/MessagePack-CSharp/commit/56fa86219d01d0a183babbbbcb34abbdea588a02', 'https://github.com/neuecc/MessagePack-CSharp/commit/f88684078698386df02204f13faeff098a61f007'} |
GHSA | GHSA-h6xw-mghq-7523 | Unsafe parsing in SWHKD | SWHKD 1.1.5 allows unsafe parsing via the -c option. An information leak might occur but there is a simple denial of service (memory exhaustion) upon an attempt to parse a large or infinite file (such as a block or character device). | {'CVE-2022-27819'} | 2022-04-15T16:14:51Z | 2022-04-08T00:00:24Z | MODERATE | 5.3 | {'CWE-400'} | {'http://www.openwall.com/lists/oss-security/2022/04/14/1', 'https://github.com/waycrate/swhkd/commit/b4e6dc76f4845ab03104187a42ac6d1bbc1e0021', 'https://github.com/advisories/GHSA-h6xw-mghq-7523', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27819', 'https://github.com/waycrate/swhkd/releases', 'https://github.com/waycrate/swhkd/releases/tag/1.1.7'} | null | {'https://github.com/waycrate/swhkd/commit/b4e6dc76f4845ab03104187a42ac6d1bbc1e0021'} | {'https://github.com/waycrate/swhkd/commit/b4e6dc76f4845ab03104187a42ac6d1bbc1e0021'} |
GHSA | GHSA-q2cv-94xm-qvg4 | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF) | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3921'} | 2021-11-17T21:12:32Z | 2021-11-15T23:18:00Z | MODERATE | 5.4 | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3921', 'https://huntr.dev/bounties/724d3fd5-9f04-45c4-98d6-35a7d15468f5', 'https://github.com/advisories/GHSA-q2cv-94xm-qvg4', 'https://github.com/firefly-iii/firefly-iii/commit/47fa9e39561a9ec9e210e4023d090a7b33381684'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/47fa9e39561a9ec9e210e4023d090a7b33381684'} | {'https://github.com/firefly-iii/firefly-iii/commit/47fa9e39561a9ec9e210e4023d090a7b33381684'} |
GHSA | GHSA-r6jx-9g48-2r5r | Arbitrary code execution due to YAML deserialization | ### Impact
TensorFlow and Keras can be tricked to perform arbitrary code execution when deserializing a Keras model from YAML format.
```python
from tensorflow.keras import models
payload = '''
!!python/object/new:type
args: ['z', !!python/tuple [], {'extend': !!python/name:exec }]
listitems: "__import__('os').system('cat /etc/passwd')"
'''
models.model_from_yaml(payload)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/python/keras/saving/model_config.py#L66-L104) uses `yaml.unsafe_load` which can perform arbitrary code execution on the input.
### Patches
Given that YAML format support requires a significant amount of work, we have removed it for now.
We have patched the issue in GitHub commit [23d6383eb6c14084a8fc3bdf164043b974818012](https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012).
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 Arjun Shibu. | {'CVE-2021-37678'} | 2022-03-23T22:52:07Z | 2021-08-25T14:41:12Z | CRITICAL | 9.3 | {'CWE-502'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37678', 'https://github.com/advisories/GHSA-r6jx-9g48-2r5r', 'https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r6jx-9g48-2r5r'} | null | {'https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012'} | {'https://github.com/tensorflow/tensorflow/commit/23d6383eb6c14084a8fc3bdf164043b974818012'} |
GHSA | GHSA-m9fq-c9hp-59g7 | Cross-site Scripting in yourls | yourls is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in edit dialog. | {'CVE-2021-3785'} | 2021-09-24T13:08:50Z | 2021-09-20T20:42:52Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/yourls/yourls/commit/1d8e224ebabb8a4c75b97f026950ed710faab0ff', 'https://github.com/advisories/GHSA-m9fq-c9hp-59g7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3785', 'https://huntr.dev/bounties/b4085d13-54fa-4419-a2ce-1d780cc31638'} | null | {'https://github.com/yourls/yourls/commit/1d8e224ebabb8a4c75b97f026950ed710faab0ff'} | {'https://github.com/yourls/yourls/commit/1d8e224ebabb8a4c75b97f026950ed710faab0ff'} |
GHSA | GHSA-wqwf-x5cj-rg56 | Arbitrary Command Injection | In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Windows nodes, which could lead to command line argument injection. | {'CVE-2018-1002101'} | 2022-04-20T20:56:14Z | 2022-02-15T01:57:18Z | MODERATE | 7.1 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1002101', 'https://github.com/advisories/GHSA-wqwf-x5cj-rg56', 'https://github.com/kubernetes/kubernetes/issues/65750', 'https://github.com/kubernetes/kubernetes/pull/65751', 'http://www.securityfocus.com/bid/106238', 'https://security.netapp.com/advisory/ntap-20190416-0008/', 'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} | null | {'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} | {'https://github.com/kubernetes/kubernetes/commit/d65039c56ce4de5f2efdc38aa1284eeb95f89169'} |
GHSA | GHSA-73m2-3pwg-5fgc | Catastrophic backtracking in regex allows Denial of Service in Waitress | ### Impact
When waitress receives a header that contains invalid characters it will cause the regular expression engine to catastrophically backtrack causing the process to use 100% CPU time and blocking any other interactions.
This would allow an attacker to send a single request with an invalid header and take the service offline.
Invalid header example:
```
Bad-header: xxxxxxxxxxxxxxx\x10
```
Increasing the number of `x`'s in the header will increase the amount of time Waitress spends in the regular expression engine.
This issue was introduced in version 1.4.2 when the regular expression was updated to attempt to match the behaviour required by errata associated with RFC7230.
### Patches
The regular expression that is used to validate incoming headers has been updated in version 1.4.3, it is recommended that people upgrade to the new version of Waitress as soon as possible.
### Workarounds
If you have deployed a reverse proxy in front of Waitress it may already be rejecting requests that include invalid headers.
### Thanks
The Pylons Project would like to thank [Fil Zembowicz](https://github.com/fzembow) for reaching out and disclosing this vulnerability!
### References
Catastrophic backtracking explained: https://www.regular-expressions.info/catastrophic.html
### For more information
If you have any questions or comments about this advisory:
- open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
- email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related) | {'CVE-2020-5236'} | 2022-03-24T19:27:20Z | 2020-02-04T03:07:31Z | CRITICAL | 5.7 | {'CWE-400'} | {'https://github.com/Pylons/waitress/security/advisories/GHSA-73m2-3pwg-5fgc', 'https://github.com/Pylons/waitress/commit/6e46f9e3f014d64dd7d1e258eaf626e39870ee1f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5236', 'https://github.com/advisories/GHSA-73m2-3pwg-5fgc'} | null | {'https://github.com/Pylons/waitress/commit/6e46f9e3f014d64dd7d1e258eaf626e39870ee1f'} | {'https://github.com/Pylons/waitress/commit/6e46f9e3f014d64dd7d1e258eaf626e39870ee1f'} |
GHSA | GHSA-wx5j-54mm-rqqq | HTTP request smuggling in io.netty:netty-codec-http | ### Impact
Netty currently just skips control chars when these are present at the beginning / end of the header name. We should better fail fast as these are not allowed by the spec and could lead to HTTP request smuggling.
Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore and so not do the validation itself.
| {'CVE-2021-43797'} | 2022-04-22T15:40:01Z | 2021-12-09T19:09:17Z | MODERATE | 6.5 | {'CWE-444'} | {'https://github.com/netty/netty/security/advisories/GHSA-wx5j-54mm-rqqq', 'https://github.com/netty/netty/commit/07aa6b5938a8b6ed7a6586e066400e2643897323', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://security.netapp.com/advisory/ntap-20220107-0003/', 'https://github.com/netty/netty/pull/11891', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43797', 'https://github.com/advisories/GHSA-wx5j-54mm-rqqq'} | null | {'https://github.com/netty/netty/commit/07aa6b5938a8b6ed7a6586e066400e2643897323'} | {'https://github.com/netty/netty/commit/07aa6b5938a8b6ed7a6586e066400e2643897323'} |
GHSA | GHSA-xw7v-qrhc-jjg2 | Access Control vulnerability in Dolibarr | An Access Control vulnerability exists in Dolibarr ERP/CRM 13.0.2, fixed version is 14.0.1, in the forgot-password function becuase the application allows email addresses as usernames, which can cause a Denial of Service. | {'CVE-2021-37517'} | 2022-04-18T22:21:51Z | 2022-04-01T00:00:41Z | HIGH | 7.5 | {'CWE-863'} | {'https://github.com/Dolibarr/dolibarr/releases/tag/14.0.1', 'https://github.com/Dolibarr/dolibarr/commit/b57eb8284e830e30eefb26e3c5ede076ea24037c', 'https://github.com/advisories/GHSA-xw7v-qrhc-jjg2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37517'} | null | {'https://github.com/Dolibarr/dolibarr/commit/b57eb8284e830e30eefb26e3c5ede076ea24037c'} | {'https://github.com/Dolibarr/dolibarr/commit/b57eb8284e830e30eefb26e3c5ede076ea24037c'} |
GHSA | GHSA-qwqc-28w3-fww6 | Message Signature Bypass in openpgp | Versions of `openpgp` prior to 4.2.0 are vulnerable to Message Signature Bypass. The package fails to verify that a message signature is of type `text`. This allows an attacker to to construct a message with a signature type that only verifies subpackets without additional input (such as `standalone` or `timestamp`). For example, an attacker that captures a `standalone` signature packet from a victim can construct arbitrary signed messages that would be verified correctly.
## Recommendation
Upgrade to version 4.2.0 or later.
If you are upgrading from a version <4.0.0 it is highly recommended to read the `High-Level API Changes` section of the `openpgp` 4.0.0 release: https://github.com/openpgpjs/openpgpjs/releases/tag/v4.0.0 | {'CVE-2019-9153'} | 2021-08-17T22:06:13Z | 2019-08-23T21:42:20Z | HIGH | 7.5 | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-9153', 'https://www.npmjs.com/advisories/1160', 'https://github.com/advisories/GHSA-qwqc-28w3-fww6', 'http://packetstormsecurity.com/files/154191/OpenPGP.js-4.2.0-Signature-Bypass-Invalid-Curve-Attack.html', 'https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc', 'https://sec-consult.com/en/blog/advisories/multiple-vulnerabilities-in-openpgp-js/', 'https://snyk.io/vuln/SNYK-JS-OPENPGP-460248', 'https://github.com/openpgpjs/openpgpjs/releases/tag/v4.2.0', 'https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/Studies/Mailvelope_Extensions/Mailvelope_Extensions_pdf.html#download=1', 'https://github.com/openpgpjs/openpgpjs/pull/816'} | null | {'https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc'} | {'https://github.com/openpgpjs/openpgpjs/pull/797/commits/327d3e5392a6f59a4270569d200c7f7a2bfc4cbc'} |
GHSA | GHSA-5pv7-hx9m-8jh3 | Missing permission checks in Jenkins Publish Over FTP Plugin | Missing permission checks in Jenkins Publish Over FTP Plugin prior to 1.17 allow attackers with Overall/Read permission to connect to an FTP server using attacker-specified credentials. | {'CVE-2022-29051'} | 2022-05-05T15:29:48Z | 2022-04-13T00:00:16Z | MODERATE | 4.3 | {'CWE-862'} | {'https://github.com/advisories/GHSA-5pv7-hx9m-8jh3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29051', 'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7', 'https://www.jenkins.io/security/advisory/2022-04-12/#SECURITY-2321'} | null | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7'} | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7'} |
GHSA | GHSA-76mp-659p-rw65 | Users registered with email verification can self re-activate their disabled accounts | ### Impact
A user disabled on a wiki using email verification for registration can re-activate himself by using the activation link provided for his registration.
### Patches
The problem has been patched in the following versions of XWiki: 11.10.13, 12.6.7, 12.10.2, 13.0.
### Workarounds
It's possible to workaround the issue by resetting the `validkey` property of the disabled XWiki users. This can be done by editing the user profile with object editor.
### References
https://jira.xwiki.org/browse/XWIKI-17942
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Jira](http://jira.xwiki.org)
* Email us at [Security mailing-list](mailto:security@xwiki.org)
| {'CVE-2021-32620'} | 2021-06-08T17:00:19Z | 2021-05-18T18:36:21Z | HIGH | 8.8 | {'CWE-285'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32620', 'https://github.com/xwiki/xwiki-platform/commit/f9a677408ffb06f309be46ef9d8df1915d9099a4', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-76mp-659p-rw65', 'https://github.com/advisories/GHSA-76mp-659p-rw65', 'https://jira.xwiki.org/browse/XWIKI-17942'} | null | {'https://github.com/xwiki/xwiki-platform/commit/f9a677408ffb06f309be46ef9d8df1915d9099a4'} | {'https://github.com/xwiki/xwiki-platform/commit/f9a677408ffb06f309be46ef9d8df1915d9099a4'} |
GHSA | GHSA-3h8m-483j-7xxm | Heap out of bounds read in `RequantizationRange` | ### Impact
The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs:
```python
import tensorflow as tf
input = tf.constant([1], shape=[1], dtype=tf.qint32)
input_max = tf.constant([], dtype=tf.float32)
input_min = tf.constant([], dtype=tf.float32)
tf.raw_ops.RequantizationRange(input=input, input_min=input_min, input_max=input_max)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/ac328eaa3870491ababc147822cd04e91a790643/tensorflow/core/kernels/requantization_range_op.cc#L49-L50) assumes that the `input_min` and `input_max` tensors have at least one element, as it accesses the first element in two arrays:
```cc
const float input_min_float = ctx->input(1).flat<float>()(0);
const float input_max_float = ctx->input(2).flat<float>()(0);
```
If the tensors are empty, `.flat<T>()` is an empty object, backed by an empty array. Hence, accesing even the 0th element is a read outside the bounds.
### Patches
We have patched the issue in GitHub commit [ef0c008ee84bad91ec6725ddc42091e19a30cf0e](https://github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29569'} | 2021-05-21T14:25:22Z | 2021-05-21T14:25:22Z | LOW | 2.5 | {'CWE-125'} | {'https://github.com/advisories/GHSA-3h8m-483j-7xxm', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3h8m-483j-7xxm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29569', 'https://github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e'} | null | {'https://github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e'} | {'https://github.com/tensorflow/tensorflow/commit/ef0c008ee84bad91ec6725ddc42091e19a30cf0e'} |
GHSA | GHSA-mcg6-h362-cmq5 | Improper Authorization in cobbler | ### Impact
If PAM is correctly configured and a user account is set to expired, the expired user-account is still able to successfully log into Cobbler in all places (Web UI, CLI & XMLRPC-API).
The same applies to user accounts with passwords set to be expired.
### Patches
There is a patch for the latest Cobbler `3.3.2` available, however a backport will be done for `3.2.x`.
### Workarounds
- Delete expired accounts which are able to access Cobbler via PAM.
- Use `chage -l <username>` to lock the account. If the account has SSH-Keys attached then remove them completely.
### References
- Originally discovered by @ysf at https://www.huntr.dev/bounties/c458b868-63df-414e-af10-47e3745caa1d/
### How to test if my Cobbler instance is affected?
The following `pytest` test assumes that your PAM setup is correct. In case the added user is not able to login, this test does not make sense to be executed.
```python
def test_pam_login_with_expired_user():
# Arrange
# create pam testuser
test_username = "expired_user"
test_password = "password"
test_api = CobblerAPI()
subprocess_1 = subprocess.run(
["perl", "-e", "'print crypt(\"%s\", \"%s\")'" % (test_username, test_password)],
stdout=subprocess.PIPE
)
subprocess.run(["useradd", "-p", subprocess_1.stdout, test_username])
# change user to be expired
subprocess.run(["chage", "-E0", test_username])
# Act
result = pam.authenticate(test_api, test_username, test_password)
# Assert - login should fail
assert not result
```
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the Cobbler repository](https://github.com/cobbler/cobbler/issues/new/choose)
* Ask in the [Gitter/Matrix Chat](https://gitter.im/cobbler/community)
* Email us at [cobbler.project@gmail.com](mailto:cobbler.project@gmail.com)
| {'CVE-2022-0860'} | 2022-04-01T20:11:34Z | 2022-03-11T20:52:04Z | HIGH | 8.2 | {'CWE-863', 'CWE-285'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0860', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DYWYHWVVRUSPCV5SWBOSAMQJQLTSBTKY/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D4KCNZYBQC2FM5SEEDRQZO4LRZ4ZECMG/', 'https://github.com/cobbler/cobbler/commit/9044aa990a94752fa5bd5a24051adde099280bfa', 'https://github.com/advisories/GHSA-mcg6-h362-cmq5', 'https://github.com/cobbler/cobbler/security/advisories/GHSA-mcg6-h362-cmq5', 'https://huntr.dev/bounties/c458b868-63df-414e-af10-47e3745caa1d', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IYSHMF6MEIITFAG7EJ3IQKVUN7MDV2XM/'} | null | {'https://github.com/cobbler/cobbler/commit/9044aa990a94752fa5bd5a24051adde099280bfa'} | {'https://github.com/cobbler/cobbler/commit/9044aa990a94752fa5bd5a24051adde099280bfa'} |
GHSA | GHSA-vjw7-6gfq-6wf5 | Path Traversal in Eclipse Vert | In Eclipse Vert.x 3.4.x up to 3.9.4, 4.0.0-milestone1, 4.0.0-milestone2, 4.0.0-milestone3, 4.0.0-milestone4, 4.0.0-milestone5, 4.0.0.Beta1, 4.0.0.Beta2, and 4.0.0.Beta3, StaticHandler doesn't correctly processes back slashes on Windows Operating systems, allowing, escape the webroot folder to the current working directory. | {'CVE-2019-17640'} | 2022-02-10T20:28:57Z | 2022-02-10T20:28:57Z | CRITICAL | 9.8 | {'CWE-23', 'CWE-22'} | {'https://lists.apache.org/thread.html/r591f6932560c8c46cee87415afed92924a982189fea7f7c9096f8e33@%3Ccommits.pulsar.apache.org%3E', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=567416', 'https://lists.apache.org/thread.html/r8383b5e7344a8b872e430ad72241b84b83e9701d275c602cfe34a941@%3Ccommits.servicecomb.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17640', 'https://mvnrepository.com/artifact/io.vertx/vertx-web', 'https://github.com/vert-x3/vertx-web/commit/b12f7c4c6576a8adc3f683b2899de4b0e7d099e4', 'https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rfd0ebf8387cfd0b959d1e218797e709793cce51a5ea2f84d0976f47d@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r8d863b148efe778ce5f8f961d0cafeda399e681d3f0656233b4c5511@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/advisories/GHSA-vjw7-6gfq-6wf5'} | null | {'https://github.com/vert-x3/vertx-web/commit/b12f7c4c6576a8adc3f683b2899de4b0e7d099e4'} | {'https://github.com/vert-x3/vertx-web/commit/b12f7c4c6576a8adc3f683b2899de4b0e7d099e4'} |
GHSA | GHSA-6vfw-74wr-3chh | Cross-site Scripting in Crater Invoice | Crater invoice prior to version 6.0.0 has a cross-site scripting vulnerability. | {'CVE-2022-0372'} | 2022-02-10T22:25:39Z | 2022-01-28T00:03:42Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0372', 'https://huntr.dev/bounties/563232b9-5a93-4f4d-8389-ed805b262ef1', 'https://github.com/advisories/GHSA-6vfw-74wr-3chh', 'https://github.com/crater-invoice/crater/pull/681'} | null | {'https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d'} | {'https://github.com/crater-invoice/crater/commit/cdc913d16cf624aee852bc9163a7c6ffc8d1da9d'} |
GHSA | GHSA-hwr7-8gxx-fj5p | Null pointer dereference in `RaggedTensorToTensor` | ### Impact
Sending invalid argument for `row_partition_types` of `tf.raw_ops.RaggedTensorToTensor` API results in a null pointer dereference and undefined behavior:
```python
import tensorflow as tf
tf.raw_ops.RaggedTensorToTensor(
shape=1,
values=10,
default_value=21,
row_partition_tensors=tf.constant([0,0,0,0]),
row_partition_types=[])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/47a06f40411a69c99f381495f490536972152ac0/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L328) accesses the first element of a user supplied list of values without validating that the provided list is not empty.
### Patches
We have patched the issue in GitHub commit [301ae88b331d37a2a16159b65b255f4f9eb39314](https://github.com/tensorflow/tensorflow/commit/301ae88b331d37a2a16159b65b255f4f9eb39314).
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-37638'} | 2021-08-25T14:44:09Z | 2021-08-25T14:44:09Z | HIGH | 7.7 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37638', 'https://github.com/tensorflow/tensorflow/commit/301ae88b331d37a2a16159b65b255f4f9eb39314', 'https://github.com/advisories/GHSA-hwr7-8gxx-fj5p', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hwr7-8gxx-fj5p'} | null | {'https://github.com/tensorflow/tensorflow/commit/301ae88b331d37a2a16159b65b255f4f9eb39314'} | {'https://github.com/tensorflow/tensorflow/commit/301ae88b331d37a2a16159b65b255f4f9eb39314'} |
GHSA | GHSA-84fq-6626-w5fg | CORS Token Disclosure in crumb | When CORS is enabled on a hapi route handler, it is possible to set a crumb token for a different domain. An attacker would need to have an application consumer visit a site they control, request a route supporting CORS, and then retrieve the token. With this token, they could possibly make requests to non CORS routes as this user.
A configuration and scenario where this would occur is unlikely, as most configurations will set CORS globally (where crumb is not used), or not at all.
## Recommendation
Update to version 3.0.0 or greater. | {'CVE-2014-7193'} | 2021-07-19T21:45:56Z | 2017-10-24T18:33:36Z | MODERATE | 0 | {'CWE-284'} | {'https://nvd.nist.gov/vuln/detail/CVE-2014-7193', 'https://nodesecurity.io/advisories/crumb_cors_token_disclosure', 'https://github.com/advisories/GHSA-84fq-6626-w5fg', 'https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://www.npmjs.com/advisories/4'} | null | {'https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c'} | {'https://github.com/hapijs/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c', 'https://github.com/spumko/crumb/commit/5e6d4f5c81677fe9e362837ffd4a02394303db3c'} |
GHSA | GHSA-q8gv-q7wr-9jf8 | Segfault in Tensorflow | ### Impact
In eager mode, TensorFlow does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/session_ops.cc#L45
In the above snippet, in eager mode, `ctx->session_state()` returns `nullptr`. Since code immediately dereferences this, we get a segmentation fault.
### Patches
We have patched the issue in 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 and will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2020-15204'} | 2021-08-26T15:17:13Z | 2020-09-25T18:28:41Z | MODERATE | 5.3 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15204', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q8gv-q7wr-9jf8', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/advisories/GHSA-q8gv-q7wr-9jf8', 'https://github.com/tensorflow/tensorflow/commit/9a133d73ae4b4664d22bd1aa6d654fec13c52ee1', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/9a133d73ae4b4664d22bd1aa6d654fec13c52ee1'} | {'https://github.com/tensorflow/tensorflow/commit/9a133d73ae4b4664d22bd1aa6d654fec13c52ee1'} |
GHSA | GHSA-jwqp-28gf-p498 | HTTP authentication credentials potentially leaked to target websites | ### Impact
If you use [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth) (i.e. the `http_user` and `http_pass` spider attributes) for HTTP authentication, all requests will expose your credentials to the request target.
This includes requests generated by Scrapy components, such as `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`, or as requests reached through redirects.
### Patches
Upgrade to Scrapy 2.5.1 and use the new `http_auth_domain` spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials.
If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.5.1 is not an option, you may upgrade to Scrapy 1.8.1 instead.
### Workarounds
If you cannot upgrade, set your HTTP authentication credentials on a per-request basis, using for example the [`w3lib.http.basic_auth_header`](https://w3lib.readthedocs.io/en/latest/w3lib.html#w3lib.http.basic_auth_header) function to convert your credentials into a value that you can assign to the `Authorization` header of your request, instead of defining your credentials globally using [`HttpAuthMiddleware`](http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth).
### For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/scrapy/scrapy/issues)
* [Email us](mailto:opensource@zyte.com)
| {'CVE-2021-41125'} | 2022-04-25T23:42:17Z | 2021-10-06T17:46:22Z | MODERATE | 5.7 | {'CWE-200', 'CWE-522'} | {'http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth', 'https://github.com/advisories/GHSA-jwqp-28gf-p498', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41125', 'https://github.com/scrapy/scrapy/security/advisories/GHSA-jwqp-28gf-p498', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00021.html', 'https://w3lib.readthedocs.io/en/latest/w3lib.html#w3lib.http.basic_auth_header', 'https://github.com/scrapy/scrapy/commit/b01d69a1bf48060daec8f751368622352d8b85a6'} | null | {'https://github.com/scrapy/scrapy/commit/b01d69a1bf48060daec8f751368622352d8b85a6'} | {'https://github.com/scrapy/scrapy/commit/b01d69a1bf48060daec8f751368622352d8b85a6'} |
GHSA | GHSA-7423-5qfm-g648 | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, 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-0916'} | 2021-03-29T21:00:09Z | 2021-03-29T21:00:09Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0916', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0916', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f', 'https://github.com/advisories/GHSA-7423-5qfm-g648'} | 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-v94v-pxqp-5qgj | Cross-site Scripting in ShowDoc | The upload feature of ShowDoc prior to version 2.10.4 allows files with the extension `.*html`, which leads to stored cross-site scripting. | {'CVE-2022-0950'} | 2022-03-29T21:28:09Z | 2022-03-16T00:00:48Z | MODERATE | 5.4 | {'CWE-434', 'CWE-79'} | {'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0950', 'https://huntr.dev/bounties/acc23996-bd57-448f-9eb4-05a8a046c2dc', 'https://github.com/advisories/GHSA-v94v-pxqp-5qgj'} | null | {'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3'} | {'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3'} |
GHSA | GHSA-xcvv-84j5-jw9h | Prototype Pollution in assign-deep | Versions of `assign-deep` before 0.4.7 are vulnerable to prototype pollution via merging functions.
## Recommendation
Update to version 0.4.7 or later. | {'CVE-2018-3720'} | 2021-01-08T00:07:35Z | 2018-07-26T15:12:31Z | LOW | 0 | {'CWE-471'} | {'https://github.com/jonschlinkert/assign-deep/commit/19953a8c089b0328c470acaaaf6accdfcb34da11', 'https://github.com/advisories/GHSA-xcvv-84j5-jw9h', 'https://hackerone.com/reports/310707', 'https://www.npmjs.com/advisories/579', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3720'} | null | {'https://github.com/jonschlinkert/assign-deep/commit/19953a8c089b0328c470acaaaf6accdfcb34da11'} | {'https://github.com/jonschlinkert/assign-deep/commit/19953a8c089b0328c470acaaaf6accdfcb34da11'} |
GHSA | GHSA-j8cx-j9j2-f29w | Insecure Storage of Sensitive Information in Microweber | Microweber prior to version 1.3 does not strip images of EXIF data, exposing information about users' locations, device hardware, and device software. | {'CVE-2022-0724'} | 2022-02-26T01:18:37Z | 2022-02-24T00:00:53Z | HIGH | 0 | {'CWE-922'} | {'https://huntr.dev/bounties/0cdc4a29-dada-4264-b326-8b65b4f11062', 'https://github.com/microweber/microweber/commit/b592c86d2b927c0cae5b73b87fb541f25e777aa3', 'https://github.com/advisories/GHSA-j8cx-j9j2-f29w', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0724'} | null | {'https://github.com/microweber/microweber/commit/b592c86d2b927c0cae5b73b87fb541f25e777aa3'} | {'https://github.com/microweber/microweber/commit/b592c86d2b927c0cae5b73b87fb541f25e777aa3'} |
GHSA | GHSA-c7pp-g2v2-2766 | DOM-based XSS in gmail-js | Affected versions of `gmail-js` are vulnerable to cross-site scripting in the `tools.parse_response`, `helper.get.visible_emails_post`, and `helper.get.email_data_post` functions, which pass user input directly into the Function constructor.
## Recommendation
Update to version 0.6.5 or later. | {'CVE-2016-1000228'} | 2021-09-23T21:31:56Z | 2020-09-01T15:32:04Z | HIGH | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/125', 'https://github.com/KartikTalwar/gmail.js/issues/281', 'https://github.com/advisories/GHSA-c7pp-g2v2-2766', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000228', 'https://github.com/KartikTalwar/gmail.js/commit/a83436f499f9c01b04280af945a5a81137b6baf1'} | null | {'https://github.com/KartikTalwar/gmail.js/commit/a83436f499f9c01b04280af945a5a81137b6baf1'} | {'https://github.com/KartikTalwar/gmail.js/commit/a83436f499f9c01b04280af945a5a81137b6baf1'} |
GHSA | GHSA-f92j-qf46-p6vm | Reflected Cross-site Scripting in ACS Commons | ### Impact
ACS Commons version 4.9.2 (and earlier) suffers from a Reflected Cross-site Scripting (XSS) vulnerability in version-compare and page-compare due to invalid JCR characters that are not handled correctly.
An attacker could potentially exploit this vulnerability to inject malicious JavaScript content into vulnerable form fields and execute it within the context of the victim's browser. Exploitation of this issue requires user interaction in order to be successful.
### Patches
This issue has been resolved in v4.10.0
### Workarounds
No workaround exist.
### References
N/A
### For more information
If you have any questions or comments about this advisory open an issue in acs-aem-commons.
### Credit
This issue was discovered and reported by Christopher Whipp (Christopher.Whipp@servicesaustralia.gov.au). | {'CVE-2021-21028'} | 2021-02-12T18:04:29Z | 2021-02-02T15:46:52Z | HIGH | 0 | {'CWE-416', 'CWE-79'} | {'https://github.com/Adobe-Consulting-Services/acs-aem-commons/security/advisories/GHSA-f92j-qf46-p6vm', 'https://helpx.adobe.com/security/products/acrobat/apsb21-09.html', 'https://github.com/advisories/GHSA-f92j-qf46-p6vm', 'https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/14d769c86606c4ce9a93c47a19f87e1ad72788d6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21028'} | null | {'https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/14d769c86606c4ce9a93c47a19f87e1ad72788d6'} | {'https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/14d769c86606c4ce9a93c47a19f87e1ad72788d6'} |
GHSA | GHSA-qhxx-j73r-qpm2 | Uninitialized memory access in TensorFlow | ### Impact
Under certain cases, a saved model can trigger use of uninitialized values during code execution. This is caused by having tensor buffers be filled with the default value of the type but forgetting to [default initialize the quantized floating point types in Eigen](https://github.com/tensorflow/tensorflow/blob/f70160322a579144950dff1537dcbe3c7c09d6f5/third_party/eigen3/unsupported/Eigen/CXX11/src/FixedPoint/FixedPointTypes.h#L61-L104):
```cc
struct QUInt8 {
QUInt8() {}
// ...
uint8_t value;
};
struct QInt16 {
QInt16() {}
// ...
int16_t value;
};
struct QUInt16 {
QUInt16() {}
// ...
uint16_t value;
};
struct QInt32 {
QInt32() {}
// ...
int32_t value;
};
```
### Patches
We have patched the issue in GitHub commit [ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2](https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2) and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2020-26266'} | 2021-01-07T22:36:21Z | 2020-12-10T19:07:24Z | LOW | 4.4 | {'CWE-908'} | {'https://github.com/advisories/GHSA-qhxx-j73r-qpm2', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qhxx-j73r-qpm2', 'https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26266'} | null | {'https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2'} | {'https://github.com/tensorflow/tensorflow/commit/ace0c15a22f7f054abcc1f53eabbcb0a1239a9e2'} |
GHSA | GHSA-4cpg-3vgw-4877 | Prototype pollution in Plist | Prototype pollution vulnerability via `.parse()` in Plist allows attackers to cause a Denial of Service (DoS) and may lead to remote code execution. | {'CVE-2022-22912'} | 2022-03-26T00:39:16Z | 2022-02-18T00:00:33Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-22912', 'https://github.com/TooTallNate/plist.js/pull/118', 'https://github.com/advisories/GHSA-4cpg-3vgw-4877', 'https://github.com/TooTallNate/plist.js/commit/96e2303d059e6be0c9e0c4773226d14b4758de52', 'https://github.com/TooTallNate/plist.js/issues/114'} | null | {'https://github.com/TooTallNate/plist.js/commit/96e2303d059e6be0c9e0c4773226d14b4758de52'} | {'https://github.com/TooTallNate/plist.js/commit/96e2303d059e6be0c9e0c4773226d14b4758de52'} |
GHSA | GHSA-9hx4-qm7h-x84j | Cross-site Scripting in Gogs | Cross-site scripting (XSS) vulnerability in models/issue.go in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.8 allows remote attackers to inject arbitrary web script or HTML via the text parameter to api/v1/markdown. | {'CVE-2014-8683'} | 2021-06-29T18:32:53Z | 2021-06-29T18:32:53Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-9hx4-qm7h-x84j', 'https://gogs.io/docs/intro/change_log.html', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98693', 'https://seclists.org/fulldisclosure/2014/Nov/31', 'https://packetstormsecurity.com/files/129118/Gogs-Markdown-Renderer-Cross-Site-Scripting.html', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8683', 'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade', 'https://www.securityfocus.com/archive/1/533996/100/0/threaded', 'https://seclists.org/fulldisclosure/2014/Nov/34', 'https://github.com/gogits/gogs/releases/tag/v0.5.8'} | null | {'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade'} | {'https://github.com/gogits/gogs/commit/3abc41cccab2486012b46305827433ad6f5deade'} |
GHSA | GHSA-2hwx-mjrm-v3g8 | Denial of service attack via .well-known lookups | ### Impact
A malicious homeserver could redirect requests to their .well-known file to a large file. This can lead to a denial of service attack where homeservers will consume significantly more resources when requesting the .well-known file of a malicious homeserver.
This affects any server which accepts federation requests from untrusted servers.
### Patches
Issue is resolved by #8950. A bug not affecting the security aspects of this was fixed in #9108.
### Workarounds
The `federation_domain_whitelist` setting can be used to restrict the homeservers communicated with over federation. | {'CVE-2021-21274'} | 2022-04-19T19:02:47Z | 2021-03-01T19:34:54Z | MODERATE | 4.3 | {'CWE-400'} | {'https://github.com/matrix-org/synapse/pull/8950', 'https://github.com/matrix-org/synapse/releases/tag/v1.25.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21274', 'https://github.com/advisories/GHSA-2hwx-mjrm-v3g8', 'https://github.com/matrix-org/synapse/commit/ff5c4da1289cb5e097902b3e55b771be342c29d6', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-2hwx-mjrm-v3g8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNNAJOZNMVMXM6AS7RFFKB4QLUJ4IFEY/'} | null | {'https://github.com/matrix-org/synapse/commit/ff5c4da1289cb5e097902b3e55b771be342c29d6'} | {'https://github.com/matrix-org/synapse/commit/ff5c4da1289cb5e097902b3e55b771be342c29d6'} |
GHSA | GHSA-q7rv-6hp3-vh96 | Improper Input Validation in guzzlehttp/psr7 | ### Impact
In proper header parsing. An attacker could sneak in a new line character and pass untrusted values.
### Patches
The issue is patched in 1.8.4 and 2.1.1
### Workarounds
There are no known workarounds.
| {'CVE-2022-24775'} | 2022-03-29T21:58:29Z | 2022-03-25T19:26:33Z | HIGH | 7.5 | {'CWE-20'} | {'https://www.drupal.org/sa-core-2022-006', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24775', 'https://github.com/guzzle/psr7/pull/485/commits/e55afaa3fc138c89adf3b55a8ba20dc60d17f1f1', 'https://github.com/guzzle/psr7/security/advisories/GHSA-q7rv-6hp3-vh96', 'https://github.com/advisories/GHSA-q7rv-6hp3-vh96', 'https://github.com/guzzle/psr7/pull/486/commits/9a96d9db668b485361ed9de7b5bf1e54895df1dc'} | null | {'https://github.com/guzzle/psr7/pull/485/commits/e55afaa3fc138c89adf3b55a8ba20dc60d17f1f1', 'https://github.com/guzzle/psr7/pull/486/commits/9a96d9db668b485361ed9de7b5bf1e54895df1dc'} | {'https://github.com/guzzle/psr7/pull/485/commits/e55afaa3fc138c89adf3b55a8ba20dc60d17f1f1', 'https://github.com/guzzle/psr7/pull/486/commits/9a96d9db668b485361ed9de7b5bf1e54895df1dc'} |
GHSA | GHSA-h6w6-xmqv-7q78 | High severity vulnerability that affects activerecord | Multiple SQL injection vulnerabilities in the quote_table_name method in the ActiveRecord adapters in activerecord/lib/active_record/connection_adapters/ in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allow remote attackers to execute arbitrary SQL commands via a crafted column name. | {'CVE-2011-2930'} | 2021-09-14T15:35:28Z | 2017-10-24T18:33:38Z | HIGH | 0 | {'CWE-89'} | {'http://groups.google.com/group/rubyonrails-security/msg/b1a85d36b0f9dd30?dmode=source&output=gplain', 'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'https://github.com/advisories/GHSA-h6w6-xmqv-7q78', 'https://bugzilla.redhat.com/show_bug.cgi?id=731438', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'http://www.debian.org/security/2011/dsa-2301', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'https://github.com/rails/rails/commit/8a39f411dc3c806422785b1f4d5c7c9d58e4bf85', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2930', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/8a39f411dc3c806422785b1f4d5c7c9d58e4bf85'} | {'https://github.com/rails/rails/commit/8a39f411dc3c806422785b1f4d5c7c9d58e4bf85'} |
GHSA | GHSA-2x7h-96h5-rq84 | Path Traversal in SharpZipLib | SharpZipLib (or #ziplib) is a Zip, GZip, Tar and BZip2 library. Starting version 1.3.0 and prior to version 1.3.3, a check was added if the destination file is under destination directory. However, it is not enforced that `destDir` ends with slash. If the `destDir` is not slash terminated like `/home/user/dir` it is possible to create a file with a name thats begins with the destination directory, i.e. `/home/user/dir.sh`. Because of the file name and destination directory constraints, the arbitrary file creation impact is limited and depends on the use case. Version 1.3.3 contains a patch for this vulnerability. | {'CVE-2021-32841'} | 2022-02-08T19:44:46Z | 2022-02-01T16:22:57Z | MODERATE | 4 | {'CWE-22'} | {'https://securitylab.github.com/advisories/GHSL-2021-125-sharpziplib/', 'https://github.com/icsharpcode/SharpZipLib/releases/tag/v1.3.3', 'https://github.com/advisories/GHSA-2x7h-96h5-rq84', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32841', 'https://github.com/icsharpcode/SharpZipLib/commit/5c3b293de5d65b108e7f2cd0ea8f81c1b8273f78'} | null | {'https://github.com/icsharpcode/SharpZipLib/commit/5c3b293de5d65b108e7f2cd0ea8f81c1b8273f78'} | {'https://github.com/icsharpcode/SharpZipLib/commit/5c3b293de5d65b108e7f2cd0ea8f81c1b8273f78'} |
GHSA | GHSA-7r94-xv9v-63jw | A use of uninitialized value vulnerability in Tensorflow | ### Impact
TensorFlow's Grappler optimizer has a [use of unitialized variable](https://github.com/tensorflow/tensorflow/blob/3457a2b122e50b4d44ceaaed5a663d635e5c22df/tensorflow/core/grappler/optimizers/auto_parallel.cc#L155-L164):
```cc
const NodeDef* dequeue_node;
for (const auto& train_node : train_nodes) {
if (IsDequeueOp(*train_node)) {
dequeue_node = train_node;
break;
}
}
if (dequeue_node) {
...
}
```
If the `train_nodes` vector (obtained from the saved model that gets optimized) does not contain a `Dequeue` node, then `dequeue_node` is left unitialized.
### Patches
We have patched the issue in GitHub commit [68867bf01239d9e1048f98cbad185bf4761bedd3](https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Qian Feng from Baidu Security Team.
| {'CVE-2021-41225'} | 2021-11-10T18:44:11Z | 2021-11-10T18:44:11Z | MODERATE | 5.5 | {'CWE-908'} | {'https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41225', 'https://github.com/advisories/GHSA-7r94-xv9v-63jw', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7r94-xv9v-63jw'} | null | {'https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3'} | {'https://github.com/tensorflow/tensorflow/commit/68867bf01239d9e1048f98cbad185bf4761bedd3'} |
GHSA | GHSA-fxwv-953p-7qpf | Phusion Passenger allows remote attackers to spoof headers passed to applications by using an _ (underscore) character instead of a - (dash) character in an HTTP header | agent/Core/Controller/SendRequest.cpp in Phusion Passenger before 4.0.60 and 5.0.x before 5.0.22, when used in Apache integration mode or in standalone mode without a filtering proxy, allows remote attackers to spoof headers passed to applications by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X_User header. | {'CVE-2015-7519'} | 2022-04-26T18:27:08Z | 2018-10-10T17:29:13Z | LOW | 3.7 | {'CWE-20'} | {'https://blog.phusion.nl/2015/12/07/cve-2015-7519/', 'http://www.openwall.com/lists/oss-security/2015/12/07/1', 'http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00024.html', 'https://github.com/phusion/passenger/commit/ddb8ecc4ebf260e4967f57f271d4f5761abeac3e', 'https://puppet.com/security/cve/passenger-dec-2015-security-fixes', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7519', 'https://github.com/advisories/GHSA-fxwv-953p-7qpf', 'https://bugzilla.suse.com/show_bug.cgi?id=956281', 'http://www.openwall.com/lists/oss-security/2015/12/07/2', 'https://lists.debian.org/debian-lts-announce/2018/06/msg00007.html'} | null | {'https://github.com/phusion/passenger/commit/ddb8ecc4ebf260e4967f57f271d4f5761abeac3e'} | {'https://github.com/phusion/passenger/commit/ddb8ecc4ebf260e4967f57f271d4f5761abeac3e'} |
GHSA | GHSA-vq2r-5xvm-3hc3 | Segfault in `CTCBeamSearchDecoder` | ### Impact
Due to lack of validation in `tf.raw_ops.CTCBeamSearchDecoder`, an attacker can trigger denial of service via segmentation faults:
```python
import tensorflow as tf
inputs = tf.constant([], shape=[18, 8, 0], dtype=tf.float32)
sequence_length = tf.constant([11, -43, -92, 11, -89, -83, -35, -100],
shape=[8], dtype=tf.int32)
beam_width = 10
top_paths = 3
merge_repeated = True
tf.raw_ops.CTCBeamSearchDecoder(
inputs=inputs, sequence_length=sequence_length, beam_width=beam_width,
top_paths=top_paths, merge_repeated=merge_repeated)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/a74768f8e4efbda4def9f16ee7e13cf3922ac5f7/tensorflow/core/kernels/ctc_decoder_ops.cc#L68-L79) fails to detect cases when the input tensor is empty and proceeds to read data from a null buffer.
### Patches
We have patched the issue in GitHub commit [b1b323042264740c398140da32e93fb9c2c9f33e](https://github.com/tensorflow/tensorflow/commit/b1b323042264740c398140da32e93fb9c2c9f33e).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29581'} | 2021-05-21T14:26:30Z | 2021-05-21T14:26:30Z | LOW | 2.5 | {'CWE-908'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29581', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-vq2r-5xvm-3hc3', 'https://github.com/advisories/GHSA-vq2r-5xvm-3hc3', 'https://github.com/tensorflow/tensorflow/commit/b1b323042264740c398140da32e93fb9c2c9f33e'} | null | {'https://github.com/tensorflow/tensorflow/commit/b1b323042264740c398140da32e93fb9c2c9f33e'} | {'https://github.com/tensorflow/tensorflow/commit/b1b323042264740c398140da32e93fb9c2c9f33e'} |
GHSA | GHSA-c9g6-9335-x697 | Improper Input Validation in SocksJS-Node | Incorrect handling of Upgrade header with the value websocket leads in crashing of containers hosting sockjs apps. This affects the package sockjs before 0.3.20. | {'CVE-2020-7693'} | 2021-04-20T15:25:19Z | 2021-04-13T15:27:51Z | MODERATE | 5.3 | {'CWE-20'} | {'https://github.com/sockjs/sockjs-node/commit/dd7e642cd69ee74385825816d30642c43e051d16', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7693', 'https://github.com/sockjs/sockjs-node/pull/265', 'https://github.com/sockjs/sockjs-node/issues/252', 'https://www.npmjs.com/package/sockjs', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-575448', 'https://snyk.io/vuln/SNYK-JS-SOCKJS-575261', 'https://github.com/advisories/GHSA-c9g6-9335-x697', 'https://github.com/andsnw/sockjs-dos-py'} | null | {'https://github.com/sockjs/sockjs-node/commit/dd7e642cd69ee74385825816d30642c43e051d16'} | {'https://github.com/sockjs/sockjs-node/commit/dd7e642cd69ee74385825816d30642c43e051d16'} |
GHSA | GHSA-pwhf-39xg-4rxw | Script injection | ### Impact
A malicious internal actor is able to upload documentation content with malicious scripts. These scripts would normally be sanitized by the TechDocs frontend, but by tricking a user to visit the content via the TechDocs API, the content sanitazion will be bypassed. If the TechDocs API is hosted on the same origin as the Backstage app or other backend plugins, this may give access to sensitive data.
The ability to upload malicious content may be limited by internal code review processes, unless the chosen TechDocs deployment method is to use an object store and the actor has access to upload files directly to that store.
### Patches
The vulnerability is patched in the `0.6.4` release of `@backstage/techdocs-common`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)
* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage) | {'CVE-2021-32660'} | 2021-06-21T22:43:31Z | 2021-06-04T19:09:35Z | MODERATE | 6.8 | {'CWE-434', 'CWE-77'} | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c', 'https://github.com/advisories/GHSA-pwhf-39xg-4rxw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32660', 'https://github.com/backstage/backstage/releases/tag/release-2021-06-03', 'https://github.com/backstage/backstage/security/advisories/GHSA-pwhf-39xg-4rxw'} | null | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c'} | {'https://github.com/backstage/backstage/commit/aad98c544e59369901fe9e0a85f6357644dceb5c'} |
GHSA | GHSA-wjfq-88q2-r34j | Unhandled exception when decoding form response JSON | ### Impact
When handling form responses from the client (`ModalFormResponsePacket`), the Minecraft Windows client may send weird JSON that `json_decode()` can't understand. A workaround for this is implemented in `InGamePacketHandler::stupid_json_decode()`.
An `InvalidArgumentException` is thrown by this function when it fails to fix an error found in the JSON, which is not caught by the caller. This leads to a server crash.
### Patches
56fe71d939c38fe14e18a31a673a9331bcc0e4ca
### Workarounds
A plugin may handle `DataPacketReceiveEvent`, capture `ModalFormResponsePacket` and run the provided JSON through `stupid_json_decode`.
Note that this requires copying the body of the function to a plugin, since the function is currently private.
### For more information
If you have any questions or comments about this advisory:
* Email us at [team@pmmp.io](mailto:team@pmmp.io)
| null | 2022-04-19T19:03:21Z | 2022-01-21T23:02:14Z | HIGH | 7.5 | null | {'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-wjfq-88q2-r34j', 'https://github.com/pmmp/PocketMine-MP/blob/4.0.7/changelogs/4.0.md#407', 'https://github.com/advisories/GHSA-wjfq-88q2-r34j', 'https://github.com/pmmp/PocketMine-MP/commit/56fe71d939c38fe14e18a31a673a9331bcc0e4ca'} | null | {'https://github.com/pmmp/PocketMine-MP/commit/56fe71d939c38fe14e18a31a673a9331bcc0e4ca'} | {'https://github.com/pmmp/PocketMine-MP/commit/56fe71d939c38fe14e18a31a673a9331bcc0e4ca'} |
GHSA | GHSA-rcjj-h6gh-jf3r | Information Disclosure in Apache Groovy | Apache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2. | {'CVE-2020-17521'} | 2022-04-22T18:24:10Z | 2020-12-09T19:03:03Z | MODERATE | 5.5 | {'CWE-379'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/r4b2f13c302eec98838ff7475253091fb9b75bc1038016ba00ebf6c08@%3Cdev.atlas.apache.org%3E', 'https://lists.apache.org/thread.html/rea63a4666ba245d2892471307772a2d8ce0f0741f341d6576625c1b3@%3Cdev.atlas.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20201218-0006/', 'https://github.com/apache/groovy/commit/bcbe5c4c76db83736166530647c024ac1e47ef28', 'https://groovy-lang.org/security.html#CVE-2020-17521', 'https://lists.apache.org/thread.html/ra9dab34bf8625511f23692ad0fcee2725f782e9aad6c5cdff6cf4465@%3Cnotifications.groovy.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/apache/groovy/pull/1425', 'https://github.com/advisories/GHSA-rcjj-h6gh-jf3r', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17521'} | null | {'https://github.com/apache/groovy/commit/bcbe5c4c76db83736166530647c024ac1e47ef28'} | {'https://github.com/apache/groovy/commit/bcbe5c4c76db83736166530647c024ac1e47ef28'} |
GHSA | GHSA-2rmp-fw5r-j5qv | Improper Authentication in InfluxDB | InfluxDB before 1.7.6 has an authentication bypass vulnerability in the authenticate function in services/httpd/handler.go because a JWT token may have an empty SharedSecret (aka shared secret). | {'CVE-2019-20933'} | 2021-05-18T18:22:05Z | 2021-05-18T18:22:05Z | CRITICAL | 9.8 | {'CWE-287'} | {'https://www.debian.org/security/2021/dsa-4823', 'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0', 'https://github.com/influxdata/influxdb/issues/12927', 'https://lists.debian.org/debian-lts-announce/2020/12/msg00030.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20933', 'https://github.com/influxdata/influxdb/compare/v1.7.5...v1.7.6', 'https://github.com/ticarpi/jwt_tool/blob/a6ca3e0524a204b5add070bc6874cb4e7e5a9864/jwt_tool.py#L1368', 'https://github.com/advisories/GHSA-2rmp-fw5r-j5qv'} | null | {'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0'} | {'https://github.com/influxdata/influxdb/commit/761b557315ff9c1642cf3b0e5797cd3d983a24c0'} |
GHSA | GHSA-q3j3-w37x-hq2q | Webcache Poisoning in symfony/http-kernel | Description
-----------
When a Symfony application is running behind a proxy or a load-balancer, you can tell Symfony to look for the `X-Forwarded-*` HTTP headers. HTTP headers that are not part of the "trusted_headers" allowed list are ignored and protect you from "Cache poisoning" attacks.
In Symfony 5.2, we've added support for the `X-Forwarded-Prefix` header, but this header was accessible in sub-requests, even if it was not part of the "trusted_headers" allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` HTTP header, leading to a web cache poisoning issue.
Resolution
----------
Symfony now ensures that the `X-Forwarded-Prefix` HTTP header is not forwarded to sub-requests when it is not trusted.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487) for branch 5.3.
Credits
-------
We would like to thank Soner Sayakci for reporting the issue and Jérémy Derussé for fixing the issue.
| {'CVE-2021-41267'} | 2022-04-19T19:03:15Z | 2021-11-24T20:04:25Z | MODERATE | 6.5 | {'CWE-444'} | {'https://github.com/symfony/symfony/security/advisories/GHSA-q3j3-w37x-hq2q', 'https://github.com/symfony/symfony/pull/44243', 'https://github.com/symfony/symfony/releases/tag/v5.3.12', 'https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41267', 'https://github.com/advisories/GHSA-q3j3-w37x-hq2q'} | null | {'https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487'} | {'https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487'} |
GHSA | GHSA-qm57-vhq3-3fwf | Header injection possible in Django | In Django 2.2 before 2.2.22, 3.1 before 3.1.10, and 3.2 before 3.2.2 (with Python 3.9.5+), URLValidator does not prohibit newlines and tabs (unless the URLField form field is used). If an application uses values with newlines in an HTTP response, header injection can occur. Django itself is unaffected because HttpResponse prohibits newlines in HTTP headers. | {'CVE-2021-32052'} | 2021-06-14T21:29:19Z | 2021-06-09T17:14:51Z | MODERATE | 6.1 | {'CWE-88', 'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32052', 'https://github.com/django/django/commit/e1e81aa1c4427411e3c68facdd761229ffea6f6f', 'http://www.openwall.com/lists/oss-security/2021/05/06/1', 'https://groups.google.com/forum/#!forum/django-announce', 'https://bugzilla.redhat.com/show_bug.cgi?id=1944801', 'https://www.djangoproject.com/weblog/2021/may/06/security-releases/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZVKYPHR3TKR2ESWXBPOJEKRO2OSJRZUE/', 'https://security.netapp.com/advisory/ntap-20210611-0002/', 'https://docs.djangoproject.com/en/3.2/releases/security/', 'https://github.com/advisories/GHSA-qm57-vhq3-3fwf'} | null | {'https://github.com/django/django/commit/e1e81aa1c4427411e3c68facdd761229ffea6f6f'} | {'https://github.com/django/django/commit/e1e81aa1c4427411e3c68facdd761229ffea6f6f'} |
GHSA | GHSA-rj44-gpjc-29r7 | [thi.ng/egf] Potential arbitrary code execution of `#gpg`-tagged property values | ### Impact
Potential for arbitrary code execution in `#gpg`-tagged property values (only if `decrypt: true` option is enabled)
### Patches
[A fix](https://github.com/thi-ng/umbrella/commit/3e14765d6bfd8006742c9e7860bc7d58ae94dfa5) has already been released as v0.4.0
### Workarounds
By default, EGF parse functions do NOT attempt to decrypt values (since GPG is only available in non-browser env).
However, if GPG encrypted values are used/required:
1. Perform a regex search for `#gpg`-tagged values in the EGF source file/string and check for backtick (\`) chars in the encrypted value string
2. Replace/remove them or skip parsing if present...
### References
https://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7#advisory-comment-65261
### For more information
If you have any questions or comments about this advisory, please open an issue in the [thi.ng/umbrella repo](https://github.com/thi-ng/umbrella/issues), of which this package is part of. | {'CVE-2021-21412'} | 2022-04-19T19:02:52Z | 2021-04-06T17:22:41Z | MODERATE | 6.4 | {'CWE-78'} | {'https://www.npmjs.com/package/@thi.ng/egf', 'https://github.com/thi-ng/umbrella/commit/88f61656e5f5cfba960013b8133186389efaf243', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21412', 'https://github.com/thi-ng/umbrella/security/advisories/GHSA-rj44-gpjc-29r7', 'https://github.com/thi-ng/umbrella/blob/develop/packages/egf/CHANGELOG.md#040-2021-03-27', 'https://github.com/advisories/GHSA-rj44-gpjc-29r7'} | null | {'https://github.com/thi-ng/umbrella/commit/88f61656e5f5cfba960013b8133186389efaf243'} | {'https://github.com/thi-ng/umbrella/commit/88f61656e5f5cfba960013b8133186389efaf243'} |
GHSA | GHSA-rhm9-p9w5-fwm7 | Symmetrically encrypting large values can lead to integer overflow | cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. When certain sequences of `update()` calls with large values (multiple GBs) for symetric encryption or decryption occur, it's possible for an integer overflow to happen, leading to mishandling of buffers. This is patched in version 3.3.2 and newer.
| {'CVE-2020-36242'} | 2022-04-22T18:32:24Z | 2021-02-10T01:32:27Z | CRITICAL | 9.1 | {'CWE-787', 'CWE-190'} | {'https://github.com/pyca/cryptography/security/advisories/GHSA-rhm9-p9w5-fwm7', 'https://github.com/pyca/cryptography/compare/3.3.1...3.3.2', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/pyca/cryptography/issues/5615', 'https://github.com/advisories/GHSA-rhm9-p9w5-fwm7', 'https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36242', 'https://github.com/pyca/cryptography/commit/82b6ce28389f0a317bc55ba2091a74b346db7cae', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L7RGQLK4J5ZQFRLKCHVVG6BKZTUQMG7E/'} | null | {'https://github.com/pyca/cryptography/commit/82b6ce28389f0a317bc55ba2091a74b346db7cae'} | {'https://github.com/pyca/cryptography/commit/82b6ce28389f0a317bc55ba2091a74b346db7cae'} |
GHSA | GHSA-p4pj-mg4r-x6v4 | Denial of Service in uap-core | ## Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
## Patches
Please update uap-core to >= v0.11.0
Downstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes. | {'CVE-2021-21317'} | 2021-02-17T17:18:55Z | 2021-02-02T15:46:38Z | HIGH | 5.3 | {'CWE-400'} | {'https://www.npmjs.com/package/uap-core', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21317', 'https://github.com/ua-parser/uap-core/commit/dc9925d458214cfe87b93e35346980612f6ae96c', 'https://github.com/ua-parser/uap-core/security/advisories/GHSA-p4pj-mg4r-x6v4', 'https://github.com/advisories/GHSA-p4pj-mg4r-x6v4'} | null | {'https://github.com/ua-parser/uap-core/commit/dc9925d458214cfe87b93e35346980612f6ae96c'} | {'https://github.com/ua-parser/uap-core/commit/dc9925d458214cfe87b93e35346980612f6ae96c'} |
GHSA | GHSA-93xj-8mrv-444m | Regular Expression Denial of Service (REDoS) in httplib2 | ### Impact
A malicious server which responds with long series of `\xa0` characters in the `www-authenticate` header may cause Denial of Service (CPU burn while parsing header) of the httplib2 client accessing said server.
### Patches
Version 0.19.0 contains new implementation of auth headers parsing, using pyparsing library.
https://github.com/httplib2/httplib2/pull/182
### Workarounds
```py
import httplib2
httplib2.USE_WWW_AUTH_STRICT_PARSING = True
```
### Technical Details
The vulnerable regular expression is https://github.com/httplib2/httplib2/blob/595e248d0958c00e83cb28f136a2a54772772b50/python3/httplib2/__init__.py#L336-L338
The section before the equals sign contains multiple overlapping groups. Ignoring the optional part containing a comma, we have:
\s*[^ \t\r\n=]+\s*=
Since all three infinitely repeating groups accept the non-breaking space character `\xa0`, a long string of `\xa0` causes catastrophic backtracking.
The complexity is cubic, so doubling the length of the malicious string of `\xa0` makes processing take 8 times as long.
### Reproduction Steps
Run a malicious server which responds with
www-authenticate: x \xa0\xa0\xa0\xa0x
but with many more `\xa0` characters.
An example malicious python server is below:
```py
from http.server import BaseHTTPRequestHandler, HTTPServer
def make_header_value(n_spaces):
repeat = "\xa0" * n_spaces
return f"x {repeat}x"
class Handler(BaseHTTPRequestHandler):
def do_GET(self):
self.log_request(401)
self.send_response_only(401) # Don't bother sending Server and Date
n_spaces = (
int(self.path[1:]) # Can GET e.g. /100 to test shorter sequences
if len(self.path) > 1 else
65512 # Max header line length 65536
)
value = make_header_value(n_spaces)
self.send_header("www-authenticate", value) # This header can actually be sent multiple times
self.end_headers()
if __name__ == "__main__":
HTTPServer(("", 1337), Handler).serve_forever()
```
Connect to the server with httplib2:
```py
import httplib2
httplib2.Http(".cache").request("http://localhost:1337", "GET")
```
To benchmark performance with shorter strings, you can set the path to a number e.g. http://localhost:1337/1000
### References
Thanks to [Ben Caller](https://github.com/b-c-ds) ([Doyensec](https://doyensec.com)) for finding vulnerability and discrete notification.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)
* Email [current maintainer at 2021-01](mailto:temotor@gmail.com) | {'CVE-2021-21240'} | 2022-04-19T19:02:44Z | 2021-02-08T19:41:59Z | LOW | 0 | {'CWE-400'} | {'https://github.com/advisories/GHSA-93xj-8mrv-444m', 'https://pypi.org/project/httplib2', 'https://github.com/httplib2/httplib2/pull/182', 'https://github.com/httplib2/httplib2/security/advisories/GHSA-93xj-8mrv-444m', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21240', 'https://github.com/httplib2/httplib2/commit/bd9ee252c8f099608019709e22c0d705e98d26bc'} | null | {'https://github.com/httplib2/httplib2/commit/bd9ee252c8f099608019709e22c0d705e98d26bc'} | {'https://github.com/httplib2/httplib2/commit/bd9ee252c8f099608019709e22c0d705e98d26bc'} |
GHSA | GHSA-6r3c-8xf3-ggrr | Directory traversal outside of SENDFILE_ROOT in django-sendfile2 | django-sendfile2 currently relies on the backend to correctly limit file paths to `SENDFILE_ROOT`. This is not the case for the `simple` and `development` backends, it is also not necessarily the case for any of the other backends either (it's just an assumption that was made by the original author).
This will be fixed in 0.6.0 which is to be released the same day as this advisory is made public.
When upgrading, you will need to make sure `SENDFILE_ROOT` is set in your settings module if it wasn't already. | null | 2022-04-19T19:02:28Z | 2020-06-24T17:15:26Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/advisories/GHSA-6r3c-8xf3-ggrr', 'https://github.com/moggers87/django-sendfile2/security/advisories/GHSA-6r3c-8xf3-ggrr', 'https://github.com/moggers87/django-sendfile2/commit/f870c52398a55b9b5189932dd8caa24efb4bc1e1'} | null | {'https://github.com/moggers87/django-sendfile2/commit/f870c52398a55b9b5189932dd8caa24efb4bc1e1'} | {'https://github.com/moggers87/django-sendfile2/commit/f870c52398a55b9b5189932dd8caa24efb4bc1e1'} |
GHSA | GHSA-pfj7-2qfw-vwgm | Path traversal in translator module in NodeBB | ### Impact
Prior to v1.18.5, a path traversal vulnerability was present that allowed users to access JSON files outside of the expected `languages/` directory.
### Patches
The vulnerability has been patched as of v1.18.5.
### Workarounds
Cherry-pick commit hash `c8b2fc46dc698db687379106b3f01c71b80f495f` to receive this patch in lieu of a full upgrade.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@nodebb.org](mailto:security@nodebb.org)
| {'CVE-2021-43788'} | 2022-04-19T19:03:13Z | 2021-11-30T22:20:43Z | MODERATE | 5 | {'CWE-22'} | {'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-pfj7-2qfw-vwgm', 'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43788', 'https://github.com/advisories/GHSA-pfj7-2qfw-vwgm', 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5'} | null | {'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f'} | {'https://github.com/NodeBB/NodeBB/commit/c8b2fc46dc698db687379106b3f01c71b80f495f'} |
GHSA | GHSA-rc8h-3fv6-pxv8 | Denial of Service in hapi | Versions of `hapi` prior to 11.1.3 are affected by a denial of service vulnerability.
The vulnerability is triggered when certain input is passed into the If-Modified-Since or Last-Modified headers.
This causes an 'illegal access' exception to be raised, and instead of sending a HTTP 500 error back to the sender, hapi will continue to hold the socket open until timed out (default node timeout is 2 minutes).
## Recommendation
Update to v11.1.3 or later | {'CVE-2015-9241'} | 2021-01-08T01:58:05Z | 2018-06-07T19:43:15Z | HIGH | 0 | {'CWE-400'} | {'https://nodesecurity.io/advisories/63', 'https://github.com/jfhbrook/node-ecstatic/pull/179', 'https://github.com/advisories/GHSA-rc8h-3fv6-pxv8', 'https://nodesecurity.io/advisories/64', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9241', 'https://github.com/hapijs/hapi/commit/aab2496e930dce5ee1ab28eecec94e0e45f03580', 'https://www.npmjs.com/advisories/63'} | null | {'https://github.com/hapijs/hapi/commit/aab2496e930dce5ee1ab28eecec94e0e45f03580'} | {'https://github.com/hapijs/hapi/commit/aab2496e930dce5ee1ab28eecec94e0e45f03580'} |
GHSA | GHSA-fxwf-45c7-4ppr | Prototype pollution in object-hierarchy-access | Overview:Prototype pollution vulnerability in ‘object-hierarchy-access’ versions 0.2.0 through 0.32.0 allows attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2020-28270'} | 2022-01-07T16:07:29Z | 2021-10-12T16:40:58Z | CRITICAL | 9.8 | {'CWE-1321', 'CWE-915'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28270', 'https://github.com/advisories/GHSA-fxwf-45c7-4ppr', 'https://github.com/mjpclab/object-hierarchy-access/commit/7b1aa134a8bc4a376296bcfac5c3463aef2b7572', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28270', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28270,'} | null | {'https://github.com/mjpclab/object-hierarchy-access/commit/7b1aa134a8bc4a376296bcfac5c3463aef2b7572'} | {'https://github.com/mjpclab/object-hierarchy-access/commit/7b1aa134a8bc4a376296bcfac5c3463aef2b7572'} |
GHSA | GHSA-jj47-x69x-mxrm | Buffer Overflow in yajl-ruby | yajl-ruby is a streaming JSON parsing and encoding library for Ruby (C bindings to yajl) based on the YAJL library.
The 1.x branch and the 2.x branch of [yajl](https://github.com/lloyd/yajl) contain an integer overflow which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs.
### Details
The [reallocation logic at yajl_buf.c#L64](https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64) may result in the `need` 32bit integer wrapping to 0 when `need` approaches a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation of buf->alloc into a small heap chunk.
These integers are declared as `size_t` in the 2.x branch of `yajl`, which practically prevents the issue from triggering on 64bit platforms, however this does not preclude this issue triggering on 32bit builds on which `size_t` is a 32bit integer.
Subsequent population of this under-allocated heap chunk is based on the original buffer size, leading to heap memory corruption.
### Impact
We rate this as a moderate severity vulnerability which mostly impacts process availability as we believe exploitation for arbitrary code execution to be unlikely.
### Patches
Patched in yajl-ruby 1.4.2
### Workarounds
Avoid passing large inputs to YAJL
### References
https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [yajl-ruby](https://github.com/brianmario/yajl-ruby/issues)
| {'CVE-2022-24795'} | 2022-04-06T21:08:35Z | 2022-04-05T15:55:51Z | MODERATE | 5.9 | {'CWE-122', 'CWE-190'} | {'https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6', 'https://github.com/brianmario/yajl-ruby/security/advisories/GHSA-jj47-x69x-mxrm', 'https://github.com/advisories/GHSA-jj47-x69x-mxrm', 'https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24795'} | null | {'https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6'} | {'https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6'} |
GHSA | GHSA-7cqx-92hp-x6wh | Heap buffer overflow in `MaxPool3DGradGrad` | ### Impact
The implementation of `tf.raw_ops.MaxPool3DGradGrad` is vulnerable to a heap buffer overflow:
```python
import tensorflow as tf
values = [0.01] * 11
orig_input = tf.constant(values, shape=[11, 1, 1, 1, 1], dtype=tf.float32)
orig_output = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)
grad = tf.constant([0.01], shape=[1, 1, 1, 1, 1], dtype=tf.float32)
ksize = [1, 1, 1, 1, 1]
strides = [1, 1, 1, 1, 1]
padding = "SAME"
tf.raw_ops.MaxPool3DGradGrad(
orig_input=orig_input, orig_output=orig_output, grad=grad, ksize=ksize,
strides=strides, padding=padding)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L694-L696) does not check that the initialization of `Pool3dParameters` completes successfully:
```cc
Pool3dParameters params{context, ksize_, stride_,
padding_, data_format_, tensor_in.shape()};
```
Since [the constructor](https://github.com/tensorflow/tensorflow/blob/596c05a159b6fbb9e39ca10b3f7753b7244fa1e9/tensorflow/core/kernels/pooling_ops_3d.cc#L48-L88) uses `OP_REQUIRES` to validate conditions, the first assertion that fails interrupts the initialization of `params`, making it contain invalid data. In turn, this might cause a heap buffer overflow, depending on default initialized values.
### Patches
We have patched the issue in GitHub commit [63c6a29d0f2d692b247f7bf81f8732d6442fad09](https://github.com/tensorflow/tensorflow/commit/63c6a29d0f2d692b247f7bf81f8732d6442fad09).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Ying Wang and Yakun Zhang of Baidu X-Team. | {'CVE-2021-29576'} | 2022-04-26T18:10:15Z | 2021-05-21T14:26:16Z | LOW | 2.5 | {'CWE-119', 'CWE-787'} | {'https://github.com/tensorflow/tensorflow/commit/63c6a29d0f2d692b247f7bf81f8732d6442fad09', 'https://github.com/advisories/GHSA-7cqx-92hp-x6wh', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7cqx-92hp-x6wh', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29576'} | null | {'https://github.com/tensorflow/tensorflow/commit/63c6a29d0f2d692b247f7bf81f8732d6442fad09'} | {'https://github.com/tensorflow/tensorflow/commit/63c6a29d0f2d692b247f7bf81f8732d6442fad09'} |
GHSA | GHSA-947x-pv47-pp3q | Cross-site scripting in pywb | Webrecorder pywb before 2.6.0 allows XSS because it does not ensure that Jinja2 templates are autoescaped. | {'CVE-2021-39286'} | 2021-09-02T17:16:18Z | 2021-09-02T17:16:18Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/webrecorder/pywb/compare/v-2.5.0...v-2.6.0', 'https://github.com/webrecorder/pywb/commit/f7bd84cdacdd665ff73ae8d09a202f60be2ebae9', 'https://github.com/advisories/GHSA-947x-pv47-pp3q', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39286'} | null | {'https://github.com/webrecorder/pywb/commit/f7bd84cdacdd665ff73ae8d09a202f60be2ebae9'} | {'https://github.com/webrecorder/pywb/commit/f7bd84cdacdd665ff73ae8d09a202f60be2ebae9'} |
GHSA | GHSA-mfjm-vh54-3f96 | Cookie-setting is not restricted based on the public suffix list | ### Impact
Responses from domain names whose public domain name suffix contains 1 or more periods (e.g. responses from `example.co.uk`, given its public domain name suffix is `co.uk`) are able to set cookies that are included in requests to any other domain sharing the same domain name suffix.
### Patches
Upgrade to Scrapy 2.6.0, which restricts cookies with their domain set to any of those in the [public suffix list](https://publicsuffix.org/).
If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.6.0 is not an option, you may upgrade to Scrapy 1.8.2 instead.
### Workarounds
The only workaround for unpatched versions of Scrapy is to [disable cookies altogether](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#std-setting-COOKIES_ENABLED), or [limit target domains](https://docs.scrapy.org/en/latest/topics/spiders.html#scrapy.spiders.Spider.allowed_domains) to a subset that does not include domain names with one of the public domain suffixes affected (those with 1 or more periods).
### References
* https://publicsuffix.org/
### For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/scrapy/scrapy/issues)
* [Email us](mailto:opensource@zyte.com)
| null | 2022-03-02T14:52:47Z | 2022-03-01T22:13:28Z | MODERATE | 0 | null | {'https://github.com/scrapy/scrapy/commit/e865c4430e58a4faa0e0766b23830f8423d6167a', 'https://github.com/scrapy/scrapy/security/advisories/GHSA-mfjm-vh54-3f96', 'https://github.com/advisories/GHSA-mfjm-vh54-3f96'} | null | {'https://github.com/scrapy/scrapy/commit/e865c4430e58a4faa0e0766b23830f8423d6167a'} | {'https://github.com/scrapy/scrapy/commit/e865c4430e58a4faa0e0766b23830f8423d6167a'} |
GHSA | GHSA-rmr5-cpv2-vgjf | Denial of Service by injecting highly recursive collections or maps in XStream | ### Impact
The vulnerability may allow a remote attacker to allocate 100% CPU time on the target system depending on CPU type or parallel execution of such a payload resulting in a denial of service only by manipulating the processed input stream.
### Patches
XStream 1.4.19 monitors and accumulates the time it takes to add elements to collections and throws an exception if a set threshold is exceeded.
### Workarounds
The attack uses the hash code implementation for collections and maps to force an exponential calculation time due to highly recursive structures with in the collection or map. Following types of the Java runtime are affected in Java versions available in December 2021:
- java.util.HashMap
- java.util.HashSet
- java.util.Hashtable
- java.util.LinkedHashMap
- java.util.LinkedHashSet
- java.util.Stack (older Java revisions only)
- java.util.Vector (older Java revisions only)
- Other third party collection implementations that use their element's hash code may also be affected
If your object graph does not use referenced elements at all, you may simply set the NO_REFERENCE mode:
```Java
XStream xstream = new XStream();
xstream.setMode(XStream.NO_REFERENCES);
```
If your object graph contains neither a Hashtable, HashMap nor a HashSet (or one of the linked variants of it) then you can use the security framework to deny the usage of these types:
```Java
XStream xstream = new XStream();
xstream.denyTypes(new Class[]{
java.util.HashMap.class, java.util.HashSet.class, java.util.Hashtable.class, java.util.LinkedHashMap.class, java.util.LinkedHashSet.class
});
```
Unfortunately these types are very common. If you only use HashMap or HashSet and your XML refers these only as default map or set, you may additionally change the default implementation of java.util.Map and java.util.Set at unmarshalling time::
```Java
xstream.addDefaultImplementation(java.util.TreeMap.class, java.util.Map.class);
xstream.addDefaultImplementation(java.util.TreeSet.class, java.util.Set.class);
```
However, this implies that your application does not care about the implementation of the map and all elements are comparable.
### References
See full information about the nature of the vulnerability and the steps to reproduce it in XStream's documentation for [CVE-2021-43859](https://x-stream.github.io/CVE-2021-43859.html).
### Credits
The vulnerability was discovered and reported by r00t4dm at Cloud-Penetrating Arrow Lab.
### 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)
* Contact us at [XStream Google Group](https://groups.google.com/group/xstream-user)
| {'CVE-2021-43859'} | 2022-04-22T15:34:22Z | 2022-02-01T00:48:15Z | HIGH | 7.5 | {'CWE-400', 'CWE-502'} | {'https://github.com/x-stream/xstream/security/advisories/GHSA-rmr5-cpv2-vgjf', 'https://github.com/x-stream/xstream/commit/e8e88621ba1c85ac3b8620337dd672e0c0c3a846', 'http://www.openwall.com/lists/oss-security/2022/02/09/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XODFRE2ZL64FICBJDOPWOLPTSSAI4U7X/', 'https://lists.debian.org/debian-lts-announce/2022/02/msg00018.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/advisories/GHSA-rmr5-cpv2-vgjf', 'https://x-stream.github.io/CVE-2021-43859.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VACQYG356OHUTD5WQGAQ4L2TTFTAV3SJ/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43859'} | null | {'https://github.com/x-stream/xstream/commit/e8e88621ba1c85ac3b8620337dd672e0c0c3a846'} | {'https://github.com/x-stream/xstream/commit/e8e88621ba1c85ac3b8620337dd672e0c0c3a846'} |
GHSA | GHSA-645p-88qh-w398 | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging failure to block the slf4j-ext class from polymorphic deserialization. | {'CVE-2018-14718'} | 2021-06-11T15:54:20Z | 2019-01-04T19:06:55Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://access.redhat.com/errata/RHSA-2019:3140', 'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://nvd.nist.gov/vuln/detail/CVE-2018-14718', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://lists.apache.org/thread.html/r1d4a247329a8478073163567bbc8c8cb6b49c6bfc2bf58153a857af1@%3Ccommits.druid.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://www.debian.org/security/2019/dsa-4452', 'https://github.com/advisories/GHSA-645p-88qh-w398', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://lists.apache.org/thread.html/ba973114605d936be276ee6ce09dfbdbf78aa56f6cdc6e79bfa7b8df@%3Cdev.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.7', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://lists.apache.org/thread.html/82b01bfb6787097427ce97cec6a7127e93718bc05d1efd5eaffc228f@%3Cdev.lucene.apache.org%3E', 'http://www.securityfocus.com/bid/106601', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://github.com/FasterXML/jackson-databind/issues/2097', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823', 'https://lists.apache.org/thread.html/6a78f88716c3c57aa74ec05764a37ab3874769a347805903b393b286@%3Cdev.lucene.apache.org%3E'} | null | {'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44'} | {'https://github.com/FasterXML/jackson-databind/commit/87d29af25e82a249ea15858e2d4ecbf64091db44'} |
GHSA | GHSA-wxj7-97fp-j53j | Exposure of Resource to Wrong Sphere in Zip-Local | The package zip-local before 0.3.5 are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) which can lead to an extraction of a crafted file outside the intended extraction directory. | {'CVE-2021-23484'} | 2022-02-07T21:20:29Z | 2022-02-01T00:46:01Z | CRITICAL | 9.8 | {'CWE-668', 'CWE-29'} | {'https://snyk.io/vuln/SNYK-JS-ZIPLOCAL-2327477', 'https://github.com/advisories/GHSA-wxj7-97fp-j53j', 'https://github.com/Mostafa-Samir/zip-local/blob/master/main.js%23L365', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23484', 'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085'} | null | {'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085'} | {'https://github.com/Mostafa-Samir/zip-local/commit/949446a95a660c0752b1db0c654f0fd619ae6085'} |
GHSA | GHSA-r5qj-cvf9-p85h | Code Injection in PyTorch Lightning | PyTorch Lightning version 1.5.10 and prior is vulnerable to code injection. There is currently a [patch](https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae) available, anticipated to be part of the `1.6.0` release. | {'CVE-2022-0845'} | 2022-03-18T21:16:06Z | 2022-03-06T00:00:16Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0845', 'https://github.com/advisories/GHSA-r5qj-cvf9-p85h', 'https://github.com/PyTorchLightning/pytorch-lightning/pull/12212', 'https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae', 'https://huntr.dev/bounties/a795bf93-c91e-4c79-aae8-f7d8bda92e2a'} | null | {'https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae'} | {'https://github.com/pytorchlightning/pytorch-lightning/commit/8b7a12c52e52a06408e9231647839ddb4665e8ae'} |
GHSA | GHSA-f5cx-5wr3-5qrc | Reference binding to nullptr in boosted trees | ### Impact
An attacker can generate undefined behavior via a reference binding to nullptr in `BoostedTreesCalculateBestGainsPerFeature`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesCalculateBestGainsPerFeature(
node_id_range=[],
stats_summary_list=[[1,2,3]],
l1=[1.0],
l2=[1.0],
tree_complexity =[1.0],
min_node_weight =[1.17],
max_splits=5)
```
A similar attack can occur in `BoostedTreesCalculateBestFeatureSplitV2`:
```python
import tensorflow as tf
tf.raw_ops.BoostedTreesCalculateBestFeatureSplitV2(
node_id_range=[],
stats_summaries_list=[[1,2,3]],
split_types=[''],
candidate_feature_ids=[1,2,3,4],
l1=[1],
l2=[1],
tree_complexity=[1.0],
min_node_weight=[1.17],
logits_dimension=5)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/84d053187cb80d975ef2b9684d4b61981bca0c41/tensorflow/core/kernels/boosted_trees/stats_ops.cc) does not validate the input values.
### Patches
We have patched the issue in GitHub commit [9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad](https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad) and in commit. [429f009d2b2c09028647dd4bb7b3f6f414bbaad7](https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7).
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-37662'} | 2021-08-25T14:42:26Z | 2021-08-25T14:42:26Z | HIGH | 7.1 | {'CWE-824'} | {'https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad', 'https://github.com/advisories/GHSA-f5cx-5wr3-5qrc', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f5cx-5wr3-5qrc', 'https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37662'} | null | {'https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7', 'https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad'} | {'https://github.com/tensorflow/tensorflow/commit/429f009d2b2c09028647dd4bb7b3f6f414bbaad7', 'https://github.com/tensorflow/tensorflow/commit/9c87c32c710d0b5b53dc6fd3bfde4046e1f7a5ad'} |
GHSA | GHSA-2p6r-37p9-89p2 | Authz Module Non-Determinism | ### Impact
Consensus failure for 0.43.x and 0.44.{0,1} users.
Funds and balances are safe.
### Patches
0.44.2
### Workarounds
Manually patch the code.
---
Full details posted in https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349. | {'CVE-2021-41135'} | 2022-04-19T19:03:11Z | 2021-10-21T17:46:57Z | MODERATE | 6.5 | {'CWE-754'} | {'https://forum.cosmos.network/t/cosmos-sdk-vulnerability-retrospective-security-advisory-jackfruit-october-12-2021/5349', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41135', 'https://github.com/cosmos/cosmos-sdk/security/advisories/GHSA-2p6r-37p9-89p2', 'https://github.com/cosmos/cosmos-sdk/releases/tag/v0.44.2', 'https://github.com/advisories/GHSA-2p6r-37p9-89p2', 'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee'} | null | {'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee'} | {'https://github.com/cosmos/cosmos-sdk/commit/68ab790a761e80d3674f821794cf18ccbfed45ee'} |
GHSA | GHSA-r4pj-74mg-8868 | Division by 0 in `Conv2DBackpropFilter` | ### Impact
An attacker can trigger a division by 0 in `tf.raw_ops.Conv2DBackpropFilter`:
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[0, 0, 1, 0], dtype=tf.float32)
filter_sizes = tf.constant([1, 1, 1, 1], shape=[4], dtype=tf.int32)
out_backprop = tf.constant([], shape=[0, 0, 1, 1], dtype=tf.float32)
tf.raw_ops.Conv2DBackpropFilter(input=input_tensor, filter_sizes=filter_sizes,
out_backprop=out_backprop,
strides=[1, 66, 18, 1], use_cudnn_on_gpu=True,
padding='SAME', explicit_paddings=[],
data_format='NHWC', dilations=[1, 1, 1, 1])
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/496c2630e51c1a478f095b084329acedb253db6b/tensorflow/core/kernels/conv_grad_shape_utils.cc#L130) does a modulus operation where the divisor is controlled by the caller:
```cc
if (dims->in_depth % filter_shape.dim_size(num_dims - 2)) { ... }
```
### Patches
We have patched the issue in GitHub commit [fca9874a9b42a2134f907d2fb46ab774a831404a](https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29524'} | 2021-05-21T14:21:47Z | 2021-05-21T14:21:47Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-r4pj-74mg-8868', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29524', 'https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r4pj-74mg-8868'} | null | {'https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a'} | {'https://github.com/tensorflow/tensorflow/commit/fca9874a9b42a2134f907d2fb46ab774a831404a'} |
GHSA | GHSA-98j8-c9q4-r38g | Memory exhaustion in Tensorflow | ### Impact
The [implementation of `StringNGrams`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/string_ngrams_op.cc#L29-L161) can be used to trigger a denial of service attack by causing an OOM condition after an integer overflow:
```python
import tensorflow as tf
tf.raw_ops.StringNGrams(
data=['123456'],
data_splits=[0,1],
separator='a'*15,
ngram_widths=[],
left_pad='',
right_pad='',
pad_width=-5,
preserve_short_sequences=True)
```
We are missing a validation on `pad_witdh` and that result in computing a negative value for `ngram_width` which is later used to allocate parts of the output.
### Patches
We have patched the issue in GitHub commit [f68fdab93fb7f4ddb4eb438c8fe052753c9413e8](https://github.com/tensorflow/tensorflow/commit/f68fdab93fb7f4ddb4eb438c8fe052753c9413e8).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team. | {'CVE-2022-21733'} | 2022-02-11T17:04:39Z | 2022-02-10T00:20:51Z | MODERATE | 4.3 | {'CWE-400', 'CWE-190'} | {'https://github.com/tensorflow/tensorflow/commit/f68fdab93fb7f4ddb4eb438c8fe052753c9413e8', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/string_ngrams_op.cc#L29-L161', 'https://github.com/advisories/GHSA-98j8-c9q4-r38g', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21733', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-98j8-c9q4-r38g'} | null | {'https://github.com/tensorflow/tensorflow/commit/f68fdab93fb7f4ddb4eb438c8fe052753c9413e8'} | {'https://github.com/tensorflow/tensorflow/commit/f68fdab93fb7f4ddb4eb438c8fe052753c9413e8'} |
GHSA | GHSA-64rh-r86q-75ff | Hard coded cryptographic key in Kiali | A hard-coded cryptographic key vulnerability in the default configuration file was found in Kiali, all versions prior to 1.15.1. A remote attacker could abuse this flaw by creating their own JWT signed tokens and bypass Kiali authentication mechanisms, possibly gaining privileges to view and alter the Istio configuration. | {'CVE-2020-1764'} | 2021-05-18T18:28:59Z | 2021-05-18T18:28:59Z | HIGH | 8.6 | {'CWE-798', 'CWE-321'} | {'https://github.com/advisories/GHSA-64rh-r86q-75ff', 'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1764', 'https://kiali.io/news/security-bulletins/kiali-security-001/', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1764', 'https://github.com/jpts/cve-2020-1764-poc', 'https://bugzilla.redhat.com/show_bug.cgi?id=1810383', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad', 'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1'} | null | {'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1'} | {'https://github.com/kiali/kiali/commit/ce48af57113c805a25179aaab1a0fac2fb93653f', 'https://github.com/kiali/kiali/commit/faed1f5f90efae3df9fd6fb793f00ccc242b3a96', 'https://github.com/kiali/kiali/commit/93f5cd0b6698e8fe8772afb8f35816f6c086aef1', 'https://github.com/kiali/kiali/commit/ac7bd6c7ddb2e01356e21d360dd1c718a90706ad'} |
GHSA | GHSA-w5gh-2wr2-pm6g | Denial of Service in Tensorflow | ### Impact
Changing the TensorFlow's `SavedModel` protocol buffer and altering the name of required keys results in segfaults and data corruption while loading the model. This can cause a denial of service in products using `tensorflow-serving` or other inference-as-a-service installments.
We have added fixes to this in f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d (both going into TensorFlow 2.2.0 and 2.3.0 but not yet backported to earlier versions). However, this was not enough, as #41097 reports a different failure mode.
### Patches
We have patched the issue in adf095206f25471e864a8e63a0f1caef53a0e3a6 and will release patch releases for all versions between 1.15 and 2.3. Patch releases for versions between 1.15 and 2.1 will also contain cherry-picks of f760f88b4267d981e13f4b302c437ae800445968 and fcfef195637c6e365577829c4d67681695956e7d.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Shuaike Dong, from Alipay Tian Qian Security Lab && Lab for Applied Security Research, CUHK. | {'CVE-2020-15206'} | 2021-08-26T15:16:58Z | 2020-09-25T18:28:40Z | CRITICAL | 9 | {'CWE-20'} | {'https://github.com/tensorflow/tensorflow/commit/adf095206f25471e864a8e63a0f1caef53a0e3a6', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15206', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-w5gh-2wr2-pm6g', 'https://github.com/advisories/GHSA-w5gh-2wr2-pm6g', 'https://github.com/tensorflow/tensorflow/commit/f760f88b4267d981e13f4b302c437ae800445968', 'https://github.com/tensorflow/tensorflow/commit/fcfef195637c6e365577829c4d67681695956e7d'} | null | {'https://github.com/tensorflow/tensorflow/commit/fcfef195637c6e365577829c4d67681695956e7d', 'https://github.com/tensorflow/tensorflow/commit/adf095206f25471e864a8e63a0f1caef53a0e3a6', 'https://github.com/tensorflow/tensorflow/commit/f760f88b4267d981e13f4b302c437ae800445968'} | {'https://github.com/tensorflow/tensorflow/commit/f760f88b4267d981e13f4b302c437ae800445968', 'https://github.com/tensorflow/tensorflow/commit/fcfef195637c6e365577829c4d67681695956e7d', 'https://github.com/tensorflow/tensorflow/commit/adf095206f25471e864a8e63a0f1caef53a0e3a6'} |
GHSA | GHSA-9h4h-8w5p-f28w | Denial of Service in geth | cmd/evm/runner.go in Go Ethereum (aka geth) allows attackers to cause a denial of service (SEGV) via crafted bytecode. | {'CVE-2018-19184'} | 2021-06-29T21:23:15Z | 2021-06-29T21:23:15Z | HIGH | 7.5 | {'CWE-476'} | {'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19184', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834', 'https://github.com/ethereum/go-ethereum/issues/18069', 'https://github.com/advisories/GHSA-9h4h-8w5p-f28w'} | null | {'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834'} | {'https://github.com/ethereum/go-ethereum/commit/83e2761c3a13524bd5d6597ac08994488cf872ef', 'https://github.com/ethereum/go-ethereum/commit/fb9f7261ec51e38eedb454594fc19f00de1a6834'} |
GHSA | GHSA-c5f8-35qr-q4fm | HTML injection in email and account expiry notifications | ### Impact
The notification emails sent for notifications for missed messages or for an expiring account are subject to HTML injection. In the case of the notification for missed messages, this could allow an attacker to insert forged content into the email.
The account expiry feature is not enabled by default and the HTML injection is not controllable by an attacker.
### Patches
This issue is fixed in #9200.
### Workarounds
For the missed messages notifications:
The `notif.html`, `notif_mail.html`, and `room.html` templates can be overridden with custom templates that manually escapes the variables using [JInja2's `escape` filter](https://jinja.palletsprojects.com/en/2.11.x/templates/#escape). See the `email.template_dir` setting.
For the account expiry notifications:
1. Account expiry can be disabled via the `account_validity.enabled` setting.
2. The `notice_expiry.html` template can be overridden with a custom template that manually escapes the variables using [JInja2's `escape` filter](https://jinja.palletsprojects.com/en/2.11.x/templates/#escape). See the `email.template_dir` setting. | {'CVE-2021-21333'} | 2021-08-31T21:07:09Z | 2021-03-26T19:53:04Z | MODERATE | 6.1 | {'CWE-74'} | {'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df', 'https://github.com/matrix-org/synapse/releases/tag/v1.27.0', 'https://github.com/advisories/GHSA-c5f8-35qr-q4fm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21333', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TNNAJOZNMVMXM6AS7RFFKB4QLUJ4IFEY/', 'https://github.com/matrix-org/synapse/pull/9200', 'https://github.com/matrix-org/synapse/security/advisories/GHSA-c5f8-35qr-q4fm'} | null | {'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df'} | {'https://github.com/matrix-org/synapse/commit/e54746bdf7d5c831eabe4dcea76a7626f1de73df'} |
GHSA | GHSA-3hjg-vc7r-rcrw | Denial of Service vulnerability in @podium/layout and @podium/proxy | ### Impact
An attacker using the `Trailer` header as part of the request against proxy endpoints has the ability to take down the server.
All Podium layouts that include podlets with proxy endpoints are affected.
### Patches
`@podium/layout` which is the main way developers/users are vulnerable to this exploit, has been patched in version `4.6.110`. All earlier versions are vulnerable.
`@podium/proxy` which is the source of the vulnerability and is used by `@podium/layout` has been patched in version `4.2.74`. All earlier versions are vulnerable.
### Workarounds
It is not easily possible to work around this issue without upgrading. We recommend upgrading `@podium/layout` and/or `@podium/proxy` as soon as possible.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [podium-lib/issues](https://github.com/podium-lib/issues)
### Credits
The vulnerability was reported by [krynos](https://hackerone.com/krynos) from [Ercoli Consulting](https://www.ercoliconsulting.eu/) via FINN.no's private bug bounty program
| {'CVE-2022-24822'} | 2022-04-12T21:50:50Z | 2022-04-07T15:20:23Z | HIGH | 7.5 | {'CWE-248'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24822', 'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf', 'https://github.com/podium-lib/layout/releases/tag/v4.6.110', 'https://github.com/podium-lib/proxy/security/advisories/GHSA-3hjg-vc7r-rcrw', 'https://github.com/podium-lib/proxy/releases/tag/v4.2.74', 'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039', 'https://github.com/advisories/GHSA-3hjg-vc7r-rcrw'} | null | {'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf', 'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039'} | {'https://github.com/podium-lib/layout/commit/fe43e655432b0a5f07b6475f67babcc2588fb039', 'https://github.com/podium-lib/proxy/commit/9698a40df081217ce142d4de71f929baaa339cdf'} |
GHSA | GHSA-cx2r-mf6x-55rx | Stored XSS with custom URLs in PrestaShop module ps_linklist | ### Impact
Stored XSS when using custom URLs.
### Patches
The problem is fixed in 3.1.0
### References
[Cross-site Scripting (XSS) - Stored (CWE-79)](https://cwe.mitre.org/data/definitions/79.html) | {'CVE-2020-5273'} | 2021-10-12T16:01:36Z | 2021-10-12T16:01:36Z | MODERATE | 4.1 | {'CWE-79'} | {'https://github.com/PrestaShop/ps_linklist/commit/83e6e0bdda2287f4d6e64127cb90c41d26b5ad82', 'https://github.com/PrestaShop/ps_linklist/security/advisories/GHSA-cx2r-mf6x-55rx', 'https://github.com/advisories/GHSA-cx2r-mf6x-55rx', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5273'} | null | {'https://github.com/PrestaShop/ps_linklist/commit/83e6e0bdda2287f4d6e64127cb90c41d26b5ad82'} | {'https://github.com/PrestaShop/ps_linklist/commit/83e6e0bdda2287f4d6e64127cb90c41d26b5ad82'} |
GHSA | GHSA-934w-hvj4-7fr6 | Path Traversal in jsreport-chrome-pdf | This affects the package jsreport-chrome-pdf before 1.10.0. | {'CVE-2020-7762'} | 2021-08-02T15:38:02Z | 2021-04-13T15:25:15Z | MODERATE | 6.5 | {'CWE-22'} | {'https://github.com/advisories/GHSA-934w-hvj4-7fr6', 'https://snyk.io/vuln/SNYK-JS-JSREPORTCHROMEPDF-1037310', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7762', 'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2'} | null | {'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2'} | {'https://github.com/jsreport/jsreport-chrome-pdf/commit/6750b2f77d05cb843aefc1c4a98097a3bd33a6a2'} |
GHSA | GHSA-f8mr-jv2c-v8mg | Invalid root may become trusted root in The Update Framework (TUF) | ### Impact
The Python TUF reference implementation `tuf<0.12` will incorrectly trust a previously downloaded root metadata file which failed verification at download time. This allows an attacker who is able to serve multiple new versions of root metadata (i.e. by a man-in-the-middle attack) culminating in a version which has not been correctly signed to control the trust chain for future updates.
While investigating the reported vulnerability, we discovered that the detailed client workflow was not fully implemented. Specifically, for step 1.3 the newly downloaded root metadata was not being verified with a threshold of keys specified in the new root metadata file.
This missing step of the client workflow has been implemented in [PR #1101](https://github.com/theupdateframework/tuf/pull/1101), which is included in [v0.14.0](https://github.com/theupdateframework/tuf/releases/tag/v0.14.0) of tuf.
### Patches
A [fix](https://github.com/theupdateframework/tuf/pull/885), is available in version [0.12](https://github.com/theupdateframework/tuf/releases/tag/v0.12.0) and newer.
### Workarounds
No workarounds are known for this issue.
### References
* Pull request resolving the invalid root becoming trusted issue [PR 885](https://github.com/theupdateframework/tuf/pull/885)
* Pull request implementing self verification of newly downloaded root metadata [PR 1101](https://github.com/theupdateframework/tuf/pull/1101) | {'CVE-2020-15163'} | 2022-04-19T19:02:30Z | 2020-09-09T17:29:27Z | HIGH | 8.7 | {'CWE-863', 'CWE-345'} | {'https://github.com/theupdateframework/tuf/releases/tag/v0.12.0', 'https://github.com/theupdateframework/tuf/security/advisories/GHSA-f8mr-jv2c-v8mg', 'https://github.com/advisories/GHSA-f8mr-jv2c-v8mg', 'https://pypi.org/project/tuf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15163', 'https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7', 'https://github.com/theupdateframework/tuf/pull/885'} | null | {'https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7'} | {'https://github.com/theupdateframework/tuf/commit/3d342e648fbacdf43a13d7ba8886aaaf07334af7'} |
GHSA | GHSA-h563-xh25-x54q | Workflow re-write vulnerability using input parameter | ### Impact
* Allow end-users to set input parameters, but otherwise expect workflows to be secure.
### Patches
Not yet.
### Workarounds
* Set `EXPRESSION_TEMPLATES=false` for the workflow controller
### References
* https://github.com/argoproj/argo-workflows/issues/6441
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
| {'CVE-2021-37914'} | 2021-08-30T23:23:12Z | 2021-08-09T20:37:50Z | MODERATE | 0 | {'CWE-20'} | {'https://github.com/argoproj/argo-workflows/security/advisories/GHSA-h563-xh25-x54q', 'https://github.com/advisories/GHSA-h563-xh25-x54q', 'https://github.com/argoproj/argo-workflows/issues/6441', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37914', 'https://github.com/argoproj/argo-workflows/pull/6285', 'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1', 'https://github.com/argoproj/argo-workflows/pull/6442'} | null | {'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1'} | {'https://github.com/argoproj/argo-workflows/commit/2a2ecc916925642fd8cb1efd026588e6828f82e1'} |
GHSA | GHSA-3r3g-g73x-g593 | Improper Verification of Cryptographic Signature in coreos | ### Impact
coreos-installer fails to correctly verify GPG signatures when decompressing gzip-compressed artifacts. This allows bypass of signature verification in cases where coreos-installer decompresses a downloaded OS image, allowing an attacker who can modify the OS image to compromise a newly-installed system.
Default installations from ISO or PXE media in Fedora CoreOS, RHEL CoreOS, and RHEL for Edge are **not** affected, as coreos-installer installs from an OS image shipped as part of the install media.
These flows are affected:
1. Installing with `--image-file`, `--image-url`, or `coreos.inst.image_url`. For example, if a user has a local mirror of installation images, an attacker could replace an image with a gzip-compressed alternative (even if the file extension is `.xz`). The result:
```
$ coreos-installer install --image-url http://localhost:8080/image.xz /dev/loop0
Downloading image from http://localhost:8080/image.xz
Downloading signature from http://localhost:8080/image.xz.sig
> Read disk 749.9 MiB/749.9 MiB (100%)
gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT
gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39
gpg: BAD signature from "Fedora (34) <fedora-34-primary@fedoraproject.org>" [ultimate]
Install complete.
```
Notice that GPG reports a bad signature, but coreos-installer continues anyway. Automation that relies on coreos-installer's exit status will not notice either.
2. `coreos-installer download --decompress --image-url`:
```
$ coreos-installer download --decompress --image-url http://localhost:8080/image.xz
> Read disk 749.9 MiB/749.9 MiB (100%)
gpg: Signature made Mon 20 Sep 2021 02:41:50 PM EDT
gpg: using RSA key 8C5BA6990BDB26E19F2A1A801161AE6945719A39
gpg: BAD signature from "Fedora (34) <fedora-34-primary@fedoraproject.org>" [ultimate]
./image
```
Again, coreos-installer reports success.
3. Installing with default parameters, when **not** installing from the image built into live ISO or PXE media, if the hosting service is compromised or if an active attacker gains control of the HTTPS response.
4. `coreos-installer download --decompress` if the hosting service is compromised or if an active attacker gains control of the HTTPS response.
### Patches
The vulnerability is [fixed](https://github.com/coreos/coreos-installer/pull/659) in coreos-installer 0.10.1.
### Workarounds
For `coreos-installer download`, do not use the `-d` or `--decompress` options.
For `coreos-installer install`, manually inspect the stderr output. If `BAD signature` appears, do not boot from the target disk. Note, however, that some OS services may have already accessed data on the compromised disk.
### References
For more information, see [PR 655](https://github.com/coreos/coreos-installer/pull/655).
### For more information
If you have any questions or comments about this advisory, [open an issue in coreos-installer](https://github.com/coreos/coreos-installer/issues/new/choose) or email the CoreOS [development mailing list](https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org/). | {'CVE-2021-20319'} | 2022-04-19T19:03:12Z | 2021-10-12T16:06:47Z | HIGH | 7.8 | {'CWE-347'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=2011862', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20319', 'https://github.com/coreos/coreos-installer/pull/655', 'https://github.com/coreos/coreos-installer/pull/659/commits/ad243c6f0eff2835b2da56ca5f7f33af76253c89', 'https://github.com/advisories/GHSA-3r3g-g73x-g593', 'https://github.com/coreos/coreos-installer/security/advisories/GHSA-3r3g-g73x-g593'} | null | {'https://github.com/coreos/coreos-installer/pull/659/commits/ad243c6f0eff2835b2da56ca5f7f33af76253c89'} | {'https://github.com/coreos/coreos-installer/pull/659/commits/ad243c6f0eff2835b2da56ca5f7f33af76253c89'} |
GHSA | GHSA-rwv7-3v45-hg29 | Out-of-bounds Read | An issue was discovered in Pillow before 8.2.0. There is an out-of-bounds read in J2kDecode, in j2ku_gray_i. This dates to Pillow 2.4.0. | {'CVE-2021-25288'} | 2022-03-03T21:46:05Z | 2021-06-08T18:49:28Z | CRITICAL | 9.1 | {'CWE-125'} | {'https://github.com/advisories/GHSA-rwv7-3v45-hg29', 'https://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-25287-cve-2021-25288-fix-oob-read-in-jpeg2kdecode', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25288', 'https://github.com/python-pillow/Pillow/pull/5377#issuecomment-833821470', 'https://security.gentoo.org/glsa/202107-33', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/', 'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87'} | null | {'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87'} | {'https://github.com/python-pillow/Pillow/commit/3bf5eddb89afdf690eceaa52bc4d3546ba9a5f87'} |
GHSA | GHSA-wp77-4gmm-7cq8 | Incorrect validation of `SaveV2` inputs | ### Impact
The code for `tf.raw_ops.SaveV2` does not properly validate the inputs and an attacker can trigger a null pointer dereference:
```python
import tensorflow as tf
tf.raw_ops.SaveV2(
prefix=['tensorflow'],
tensor_name=['v'],
shape_and_slices=[],
tensors=[1,2,3])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/save_restore_v2_ops.cc) uses `ValidateInputs` to check that the input arguments are valid. This validation would have caught the illegal state represented by the reproducer above.
However, the validation uses `OP_REQUIRES` which translates to setting the `Status` object of the current `OpKernelContext` to an error status, followed by an empty `return` statement which just terminates the execution of the function it is present in. However, this does not mean that the kernel execution is finalized: instead, execution continues from the next line in `Compute` that follows the call to `ValidateInputs`. This is equivalent to lacking the validation.
### Patches
We have patched the issue in GitHub commit [9728c60e136912a12d99ca56e106b7cce7af5986](https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986).
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-37648'} | 2021-08-25T14:43:29Z | 2021-08-25T14:43:29Z | HIGH | 7.8 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37648', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wp77-4gmm-7cq8', 'https://github.com/advisories/GHSA-wp77-4gmm-7cq8', 'https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986'} | null | {'https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986'} | {'https://github.com/tensorflow/tensorflow/commit/9728c60e136912a12d99ca56e106b7cce7af5986'} |
GHSA | GHSA-h6fg-mjxg-hqq4 | Integer truncation in Shard API usage | ### Impact
The `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/util/work_sharder.h#L59-L60
However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L204-L205
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L317-L318
In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.
### Patches
We have patched the issue in 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575. We will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2020-15202'} | 2021-08-26T15:14:00Z | 2020-09-25T18:28:35Z | CRITICAL | 9 | {'CWE-754', 'CWE-197'} | {'https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1', 'https://github.com/advisories/GHSA-h6fg-mjxg-hqq4', 'https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15202'} | null | {'https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575', 'https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832'} | {'https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575', 'https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832'} |
GHSA | GHSA-pm3v-qxf6-fgxv | Cross-site Scripting in pimcore | Cross-site Scripting (XSS) - Stored in Packagist pimcore/pimcore prior to 10.2.9. | {'CVE-2022-0285'} | 2022-01-27T18:32:20Z | 2022-01-21T18:08:43Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0285', 'https://github.com/advisories/GHSA-pm3v-qxf6-fgxv', 'https://huntr.dev/bounties/321918b2-aa01-410e-9f7c-dca5f286bc9c', 'https://github.com/pimcore/pimcore/commit/b432225952e2a5ab0268f401b85a14480369b835'} | null | {'https://github.com/pimcore/pimcore/commit/b432225952e2a5ab0268f401b85a14480369b835'} | {'https://github.com/pimcore/pimcore/commit/b432225952e2a5ab0268f401b85a14480369b835'} |
GHSA | GHSA-4vvg-x86p-mvqc | Leaking of user information on Cross-Domain communication in sysend | ### Impact
Users that use Cross-Origin communication and send sensitive information make it possible for this data to be intercepted.
This is not a big impact because it happens only on the same browser.
### Patches
It has been patched in version 1.10.0
### Workarounds
The only workaround is to not send sensitive information with sysend messages.
| {'CVE-2022-24762'} | 2022-03-28T17:26:42Z | 2022-03-14T22:43:23Z | MODERATE | 6.5 | {'CWE-200'} | {'https://github.com/jcubic/sysend.js/security/advisories/GHSA-4vvg-x86p-mvqc', 'https://github.com/jcubic/sysend.js/issues/33', 'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24762', 'https://github.com/advisories/GHSA-4vvg-x86p-mvqc', 'https://github.com/jcubic/sysend.js/releases/tag/1.10.0'} | null | {'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a'} | {'https://github.com/jcubic/sysend.js/commit/a24f4b776fb18191ae0f7e3d90c2c7bec459431a'} |
GHSA | GHSA-8vq6-5f66-hp3r | Logic error in dolibarr/dolibarr | In dolibarr/dolibarr prior to 16.0 any low privileged users could update their login name which should only be updated by admin. | {'CVE-2022-0746'} | 2022-03-07T13:41:24Z | 2022-02-26T00:00:44Z | MODERATE | 4.3 | null | {'https://huntr.dev/bounties/b812ea22-0c02-46fe-b89f-04519dfb1ebd', 'https://github.com/dolibarr/dolibarr/commit/4973019630d51ad76b7c1a4141ec7a33053a7d21', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0746', 'https://github.com/advisories/GHSA-8vq6-5f66-hp3r'} | null | {'https://github.com/dolibarr/dolibarr/commit/4973019630d51ad76b7c1a4141ec7a33053a7d21'} | {'https://github.com/dolibarr/dolibarr/commit/4973019630d51ad76b7c1a4141ec7a33053a7d21'} |
GHSA | GHSA-9gj3-hwp5-pmwc | XSS in the `altField` option of the Datepicker widget in jquery-ui | ### Impact
Accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. For example, initializing the datepicker in the following way:
```js
$( "#datepicker" ).datepicker( {
altField: "<img onerror='doEvilThing()' src='/404' />",
} );
```
will call the `doEvilThing` function.
### Patches
The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector.
### Workarounds
A workaround is to not accept the value of the `altField` option from untrusted sources.
### For more information
If you have any questions or comments about this advisory, search for a relevant issue in [the jQuery UI repo](https://github.com/jquery/jquery-ui/issues). If you don't find an answer, open a new issue. | {'CVE-2021-41182'} | 2022-04-22T15:40:54Z | 2021-10-26T14:55:02Z | MODERATE | 6.5 | {'CWE-79'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NXIUUBRVLA4E7G7MMIKCEN75YN7UFERW/', 'https://security.netapp.com/advisory/ntap-20211118-0004/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41182', 'https://blog.jqueryui.com/2021/10/jquery-ui-1-13-0-released/', 'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00014.html', 'https://www.drupal.org/sa-contrib-2022-004', 'https://github.com/jquery/jquery-ui/security/advisories/GHSA-9gj3-hwp5-pmwc', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/O74SXYY7RGXREQDQUDQD4BPJ4QQTD2XQ/', 'https://www.drupal.org/sa-core-2022-002', 'https://www.tenable.com/security/tns-2022-09', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SNXA7XRKGINWSUIPIZ6ZBCTV6N3KSHES/', 'https://github.com/advisories/GHSA-9gj3-hwp5-pmwc'} | null | {'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63'} | {'https://github.com/jquery/jquery-ui/pull/1954/commits/6809ce843e5ac4128108ea4c15cbc100653c2b63'} |
GHSA | GHSA-36xw-fx78-c5r4 | containerd-shim API Exposed to Host Network Containers | ## Impact
Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges.
## Patches
This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade.
## Workarounds
If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the "host" network namespace, for example with `docker run --net=host` or `hostNetwork: true` in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue.
If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to `deny unix addr=@**,` to your policy.
It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.
## Credits
The containerd maintainers would like to thank Jeff Dileo of NCC Group for responsibly disclosing this issue in accordance with the [containerd security policy](https://github.com/containerd/project/blob/master/SECURITY.md) and for reviewing the patch.
## For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/containerd/containerd/issues/new/choose)
* Email us at security@containerd.io if you think you’ve found a security bug. | {'CVE-2020-15257'} | 2022-04-19T19:02:38Z | 2021-05-24T17:00:22Z | MODERATE | 5.2 | {'CWE-669'} | {'https://github.com/containerd/containerd/releases/tag/v1.4.3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15257', 'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad', 'https://www.debian.org/security/2021/dsa-4865', 'https://security.gentoo.org/glsa/202105-33', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNKXLOLZWO5FMAPX63ZL7JNKTNNT5NQD/', 'https://research.nccgroup.com/2020/12/10/abstract-shimmer-cve-2020-15257-host-networking-is-root-equivalent-again/', 'https://github.com/advisories/GHSA-36xw-fx78-c5r4', 'https://github.com/containerd/containerd/security/advisories/GHSA-36xw-fx78-c5r4'} | null | {'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad'} | {'https://github.com/containerd/containerd/commit/4a4bb851f5da563ff6e68a83dc837c7699c469ad'} |
GHSA | GHSA-wwgf-3xp7-cxj4 | Potentially sensitive data exposure in Symfony Web Socket Bundle | ### Impact
Inside `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()`, messages are arbitrarily broadcasted to the related Topic if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` does not succeed. The `dispatch()` method can be considered to not succeed if (depending on the version of the bundle) the callback defined on a topic route is misconfigured, a `Gos\Bundle\WebSocketBundle\Topic\TopicInterface` implementation is not found for the callback, a topic which also implements `Gos\Bundle\WebSocketBundle\Topic\SecuredTopicInterface` rejects the connection, or an Exception is unhandled. This can result in an unintended broadcast to the websocket server potentially with data that should be considered sensitive.
### Patches
In 1.10.4, 2.6.1, and 3.3.0, `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()` has been changed to no longer broadcast an event's data if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` fails.
### Workarounds
Upgrade to 1.10.4, 2.6.1, and 3.3.0
Note, the 1.x branch is considered end of support as of July 1, 2020.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repository](https://github.com/GeniusesOfSymfony/WebSocketBundle) | null | 2022-04-19T19:02:30Z | 2020-07-07T16:33:45Z | MODERATE | 5.9 | {'CWE-200'} | {'https://snyk.io/vuln/SNYK-PHP-GOSWEBSOCKETBUNDLE-575401', 'https://github.com/FriendsOfPHP/security-advisories/commit/942fd37245cb724ba8cc8d6f11f075a1bd53b338', 'https://github.com/advisories/GHSA-wwgf-3xp7-cxj4', 'https://github.com/GeniusesOfSymfony/WebSocketBundle/security/advisories/GHSA-wwgf-3xp7-cxj4'} | null | {'https://github.com/FriendsOfPHP/security-advisories/commit/942fd37245cb724ba8cc8d6f11f075a1bd53b338'} | {'https://github.com/FriendsOfPHP/security-advisories/commit/942fd37245cb724ba8cc8d6f11f075a1bd53b338'} |
GHSA | GHSA-cc2p-4jhr-xhhx | False-positive validity for NFT1 genesis transactions in SLPJS | ### Impact
In the npm package named "slpjs", versions prior to 0.27.4 are vulnerable to false-positive validation outcomes for the NFT1 Child Genesis transaction type. A poorly implemented SLP wallet or opportunistic attacker could create a seemingly valid NFT1 child token without burning any of the NFT1 Group token type as is required by the NFT1 specification.
### Patches
npm package "slpjs" has been patched and is published and tagged as version 0.27.4.
### Workarounds
Upgrade to slpjs 0.27.4.
### References
* Package location: https://www.npmjs.com/package/slpjs
* SLP NFT1 spec: https://slp.dev/specs/slp-nft-1/#nft1-protocol-requirements
* Git commit hash fixing this issue: https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c
* Unit tests have been added to assist validator implementations in avoiding this bug: https://github.com/simpleledger/slp-unit-test-data/commit/8c942eacfae12686dcf1f3366321445a4fba73e7
### For more information
If you have any questions or comments about this advisory please open an issue in the [slp-validate](https://github.com/simpleledger/slpjs/issues) repository. | {'CVE-2020-15130'} | 2021-01-07T23:43:06Z | 2020-07-30T14:58:42Z | CRITICAL | 7.5 | {'CWE-697'} | {'https://github.com/simpleledger/slpjs/security/advisories/GHSA-cc2p-4jhr-xhhx', 'https://github.com/advisories/GHSA-cc2p-4jhr-xhhx', 'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15130'} | null | {'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c'} | {'https://github.com/simpleledger/slpjs/commit/290c20e8bff13ac81459d43e54cac232b5e3456c'} |
GHSA | GHSA-v9j2-q4q5-cxh4 | No CSRF protection on the password change form | ### Impact
It's possible for forge an URL that, when accessed by an admin, will reset the password of any user in XWiki.
### Patches
The problem has been patched in XWiki 12.10.5, 13.2RC1.
### Workarounds
It's possible to apply the patch manually by modifying the `register_macros.vm` template like in https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257.
### References
https://jira.xwiki.org/browse/XWIKI-18315
### 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 ML](mailto:security@xwiki.org)
| {'CVE-2021-32730'} | 2021-07-02T19:19:13Z | 2021-07-02T19:19:13Z | MODERATE | 5.7 | {'CWE-352'} | {'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-v9j2-q4q5-cxh4', 'https://jira.xwiki.org/browse/XWIKI-18315', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32730', 'https://github.com/advisories/GHSA-v9j2-q4q5-cxh4', 'https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257'} | null | {'https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257'} | {'https://github.com/xwiki/xwiki-platform/commit/0a36dbcc5421d450366580217a47cc44d32f7257'} |
GHSA | GHSA-68wm-pfjf-wqp6 | Authentication bypassed with malformed request URI on nginx | ### Impact
This affects uses who are using nginx ngx_http_auth_request_module with Authelia, it allows a malicious individual who crafts a malformed HTTP request to bypass the authentication mechanism. It additionally could theoretically affect other proxy servers, but all of the ones we officially support except nginx do not allow malformed URI paths.
### Patches
The problem is rectified entirely in v4.29.3. As this patch is relatively straightforward we can back port this to any version upon request. Alternatively we are supplying a git patch to 4.25.1 which should be relatively straightforward to apply to any version, the git patches for specific versions can be found below.
<details><summary>Patch for 4.25.1:</summary><p>
```patch
From ca22f3d2c44ca7bef043ffbeeb06d6659c1d550f Mon Sep 17 00:00:00 2001
From: James Elliott <james-d-elliott@users.noreply.github.com>
Date: Wed, 19 May 2021 12:10:13 +1000
Subject: [PATCH] fix(handlers): verify returns 200 on malformed request
This is a git patch for commit at tag v4.25.1 to address a potential method to bypass authentication in proxies that forward malformed information to Authelia in the forward auth process. Instead of returning a 200 this ensures that Authelia returns a 401 when this occurs.
---
internal/handlers/handler_verify.go | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/internal/handlers/handler_verify.go b/internal/handlers/handler_verify.go
index 65c064ce..4dd9702d 100644
--- a/internal/handlers/handler_verify.go
+++ b/internal/handlers/handler_verify.go
@@ -396,7 +396,9 @@ func VerifyGet(cfg schema.AuthenticationBackendConfiguration) middlewares.Reques
targetURL, err := getOriginalURL(ctx)
if err != nil {
- ctx.Error(fmt.Errorf("Unable to parse target URL: %s", err), operationFailedMessage)
+ ctx.Logger.Error(fmt.Errorf("Unable to parse target URL: %s", err))
+ ctx.ReplyUnauthorized()
+
return
}
--
2.31.1
```
</p></details>
### Workarounds
The most relevant workaround is upgrading. **If you need assistance with an upgrade please contact us on [Matrix](https://riot.im/app/#/room/#authelia:matrix.org) or [Discord](https://discord.authelia.com).** Please just let us know you're needing help upgrading to above 4.29.2.
You can add an block which fails requests that contains a malformed URI in the internal location block. We have crafted one that should work in most instances, it basically checks no chars that are required to be URL-encoded for either the path or the query are in the URI. Basically this regex checks that the characters between the square braces are the only characters in the $request_uri header, if they exist, it returns a HTTP 401 status code. The characters in the regex match are tested to not cause a parsing error that would result in a failure, however they are not exhaustive since query strings seem to not always conform to the RFC.
<details><summary>authelia.conf:</summary><p>
```nginx
location /authelia {
internal;
# **IMPORTANT**
# This block rejects requests with a 401 which contain characters that are unable to be parsed.
# It is necessary for security prior to v4.29.3 due to the fact we returned an invalid code in the event of a parser error.
# You may comment this section if you're using Authelia v4.29.3 or above. We strongly recommend upgrading.
# RFC3986: http://tools.ietf.org/html/rfc3986
# Commentary on RFC regarding Query Strings: https://www.456bereastreet.com/archive/201008/what_characters_are_allowed_unencoded_in_query_strings/
if ($request_uri ~ [^a-zA-Z0-9_+-=\!@$%&*?~.:#'\;\(\)\[\]]) {
return 401;
}
# Include the remainder of the block here.
}
````
</p></details>
### Discovery
This issue was discovered by:
Siemens Energy
Cybersecurity Red Team
- Silas Francisco
- Ricardo Pesqueira
### Identifying active exploitation of the vulnerability
The following regex should match log entries that are an indication of the vulnerability being exploited:
```regex
level=error msg="Unable to parse target URL: Unable to parse URL (extracted from X-Original-URL header)?.*?: parse.*?net/url:.*github\.com/authelia/authelia/internal/handlers/handler_verify\.go
```
Example log entry ***with*** X-Original-URL configured:
```log
time="2021-05-21T16:31:15+10:00" level=error msg="Unable to parse target URL: Unable to parse URL extracted from X-Original-URL header: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
Example log entry ***without*** X-Original-URL configured:
```log
time="2021-05-21T16:30:17+10:00" level=error msg="Unable to parse target URL: Unable to parse URL https://example.com/: parse \"https://example.com/": net/url: invalid control character in URL" method=GET path=/api/verify remote_ip=192.168.1.10 stack="github.com/authelia/authelia/internal/middlewares/authelia_context.go:65 (*AutheliaCtx).Error\ngithub.com/authelia/authelia/internal/handlers/handler_verify.go:431 VerifyGet.func1\ngithub.com/authelia/authelia/internal/middlewares/authelia_context.go:50 AutheliaMiddleware.func1.1\ngithub.com/fasthttp/router@v1.3.12/router.go:414 (*Router).Handler\ngithub.com/authelia/authelia/internal/middlewares/log_request.go:14 LogRequestMiddleware.func1\ngithub.com/valyala/fasthttp@v1.24.0/server.go:2219 (*Server).serveConn\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:223 (*workerPool).workerFunc\ngithub.com/valyala/fasthttp@v1.24.0/workerpool.go:195 (*workerPool).getCh.func1\nruntime/asm_amd64.s:1371 goexit"
```
### For more information
If you have any questions or comments about this advisory:
* Open an issue at [authelia](https://github.com/authelia/authelia/issues)
* Email us at [security@authelia.com](mailto:security@authelia.com)
| {'CVE-2021-32637'} | 2022-04-19T19:02:58Z | 2021-12-20T16:57:16Z | CRITICAL | 10 | {'CWE-287'} | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda', 'https://github.com/authelia/authelia/security/advisories/GHSA-68wm-pfjf-wqp6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32637', 'https://github.com/advisories/GHSA-68wm-pfjf-wqp6'} | null | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda'} | {'https://github.com/authelia/authelia/commit/c62dbd43d6e69ae81530e7c4f8763857f8ff1dda'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.