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-4j46-mp85-mv8c | Path traversal in rollup-plugin-serve | Path traversal in npm package `rollup-plugin-serve` before version 1.0.2. There is no path sanitization in `readFile` operation. | {'CVE-2020-7684'} | 2021-05-18T01:52:24Z | 2021-05-18T01:52:24Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://github.com/advisories/GHSA-4j46-mp85-mv8c', 'https://github.com/thgh/rollup-plugin-serve/commit/3d144f2f47e86fcba34f5a144968da94220e3969', 'https://vuldb.com/?id.158745', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7684', 'https://github.com/thgh/rollup-plugin-serve/releases/tag/v1.0.2'} | null | {'https://github.com/thgh/rollup-plugin-serve/commit/3d144f2f47e86fcba34f5a144968da94220e3969'} | {'https://github.com/thgh/rollup-plugin-serve/commit/3d144f2f47e86fcba34f5a144968da94220e3969'} |
GHSA | GHSA-xhw6-hjc9-679m | Token validation bypass in Pac4j | Pac4j v5.1 and earlier allows (by default) clients to accept and successfully validate ID Tokens with "none" algorithm (i.e., tokens with no signature) which is not secure and violates the OpenID Core Specification. The "none" algorithm does not require any signature verification when validating the ID tokens, which allows the attacker to bypass the token validation by injecting a malformed ID token using "none" as the value of "alg" key in the header with an empty signature value. | {'CVE-2021-44878'} | 2022-04-01T18:07:15Z | 2022-01-08T00:36:05Z | HIGH | 7.5 | {'CWE-347'} | {'https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44878', 'https://github.com/advisories/GHSA-xhw6-hjc9-679m', 'https://www.pac4j.org/blog/cve_2021_44878_is_this_serious.html', 'https://openid.net/specs/openid-connect-core-1_0.html#IDToken'} | null | {'https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae'} | {'https://github.com/pac4j/pac4j/commit/22b82ffd702a132d9f09da60362fc6264fc281ae'} |
GHSA | GHSA-rgjg-66cx-5x9m | Authentication Bypass | Grafana before 4.6.4 and 5.x before 5.2.3 allows authentication bypass because an attacker can generate a valid "remember me" cookie knowing only a username of an LDAP or OAuth user. | {'CVE-2018-15727'} | 2022-04-12T22:18:16Z | 2022-02-15T01:57:18Z | CRITICAL | 9.8 | {'CWE-287'} | {'https://github.com/advisories/GHSA-rgjg-66cx-5x9m', 'https://grafana.com/blog/2018/08/29/grafana-5.2.3-and-4.6.4-released-with-important-security-fix/', 'https://access.redhat.com/errata/RHSA-2019:0019', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15727', 'https://www.securityfocus.com/bid/105184', 'https://access.redhat.com/errata/RHSA-2018:3829', 'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137'} | null | {'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137'} | {'https://github.com/grafana/grafana/commit/7baecf0d0deae0d865e45cf03e082bc0db3f28c3', 'https://github.com/grafana/grafana/commit/df83bf10a225811927644bdf6265fa80bdea9137'} |
GHSA | GHSA-c5r5-7pfh-6qg6 | OS command injection in BibTeX-Ruby | BibTeX-ruby before 5.1.0 allows shell command injection due to unsanitized user input being passed directly to the built-in Ruby Kernel.open method through BibTeX.open. | {'CVE-2019-10780'} | 2021-08-19T17:15:39Z | 2020-02-14T23:10:01Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://snyk.io/vuln/SNYK-RUBY-BIBTEXRUBY-542602', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10780', 'https://github.com/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11', 'https://github.com/advisories/GHSA-c5r5-7pfh-6qg6'} | null | {'https://github.com/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11'} | {'https://github.com/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11'} |
GHSA | GHSA-763g-fqq7-48wg | XML external entity (XXE) processing ('external-parameter-entities' feature was not fully disabled)) | Due to an incomplete fix for [CVE-2019-9658](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9658), checkstyle was still vulnerable to XML External Entity (XXE) Processing.
### Impact
#### User: Build Maintainers
This vulnerability probably doesn't impact Maven/Gradle users as, in most cases, these builds are processing files that are trusted, or pre-vetted by a pull request reviewer before being run on internal CI infrastructure.
#### User: Static Analysis as a Service
If you operate a site/service that parses "untrusted" Checkstyle XML configuration files, you are vulnerable to this and should patch.
Note from the discoverer of the original CVE-2019-9658:
> While looking at a few companies that run Checkstyle/PMD/ect... as a service I notice that it's a common pattern to run the static code analysis tool inside of a Docker container with the following flags:
> ```
> --net=none \
> --privileged=false \
> --cap-drop=ALL
> ```
> Running the analysis in Docker has the advantage that there should be no sensitive local file information that XXE can exfiltrate from the container. Additionally, these flags prevent vulnerabilities in static analysis tools like Checkstyle from being used to exfiltrate data via XXE or to perform SSRF.
> \- [Jonathan Leitschuh](https://twitter.com/jlleitschuh)
### Patches
_Has the problem been patched? What versions should users upgrade to?_
Patched, will be released with version 8.29 at 26 Jan 2020.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
No workaround are available
### References
- [CWE-611: Improper Restriction of XML External Entity Reference](https://cwe.mitre.org/data/definitions/611.html)
- GitHub Issue https://github.com/checkstyle/checkstyle/issues/7468
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/checkstyle/checkstyle/issues
| {'CVE-2019-10782'} | 2022-04-19T19:02:47Z | 2020-01-31T18:00:07Z | MODERATE | 5.3 | {'CWE-611'} | {'https://snyk.io/vuln/SNYK-JAVA-COMPUPPYCRAWLTOOLS-543266', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10782', 'https://github.com/advisories/GHSA-763g-fqq7-48wg', 'https://github.com/checkstyle/checkstyle/security/advisories/GHSA-763g-fqq7-48wg', 'https://lists.apache.org/thread.html/r8aaf4ee16bbaf6204731d4770d96ebb34b258cd79b491f9cdd7f2540@%3Ccommits.nifi.apache.org%3E', 'https://github.com/checkstyle/checkstyle/commit/c46a16d177e6797895b195c288ae9a9a096254b8', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00008.html', 'https://github.com/checkstyle/checkstyle/issues/7468'} | null | {'https://github.com/checkstyle/checkstyle/commit/c46a16d177e6797895b195c288ae9a9a096254b8'} | {'https://github.com/checkstyle/checkstyle/commit/c46a16d177e6797895b195c288ae9a9a096254b8'} |
GHSA | GHSA-cjjf-94ff-43w7 | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Jodd-db jar (for database access for the Jodd framework) in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload. | {'CVE-2018-12022'} | 2021-06-11T15:58:50Z | 2019-03-25T18:03:09Z | HIGH | 7.5 | {'CWE-502'} | {'https://access.redhat.com/errata/RHSA-2019:1108', 'https://github.com/advisories/GHSA-cjjf-94ff-43w7', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://www.blackhat.com/docs/us-16/materials/us-16-Munoz-A-Journey-From-JNDI-LDAP-Manipulation-To-RCE.pdf', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:1140', 'https://lists.apache.org/thread.html/7fcf88aff0d1deaa5c3c7be8d58c05ad7ad5da94b59065d8e7c50c5d@%3Cissues.lucene.apache.org%3E', 'https://github.com/FasterXML/jackson-databind/issues/2052', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://bugzilla.redhat.com/show_bug.cgi?id=1671098', 'https://www.debian.org/security/2019/dsa-4452', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', '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://access.redhat.com/errata/RHSA-2019:1106', 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a', 'https://access.redhat.com/errata/RHSA-2019:1107', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZEDLDUYBSTDY4GWDBUXGJNS2RFYTFVRC/', '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://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823', 'https://nvd.nist.gov/vuln/detail/CVE-2018-12022', 'http://www.securityfocus.com/bid/107585'} | null | {'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a'} | {'https://github.com/FasterXML/jackson-databind/commit/28badf7ef60ac3e7ef151cd8e8ec010b8479226a'} |
GHSA | GHSA-2363-cqg2-863c | XML External Entity (XXE) Injection in JDOM | An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP request. At this time there is not released fixed version of JDOM. As a workaround, to avoid external entities being expanded, one can call `builder.setExpandEntities(false)` and they won't be expanded. | {'CVE-2021-33813'} | 2022-04-22T15:47:57Z | 2021-07-27T19:02:56Z | HIGH | 7.5 | {'CWE-611'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EWFVYTHGILOQXUA7U3SPOERQXL7OPSZG/', 'https://lists.apache.org/thread.html/rfb7a93e40ebeb1e0068cde0bf3834dcab46bb1ef06d6424db48ed9fd@%3Cdev.tika.apache.org%3E', 'https://github.com/hunterhacker/jdom/commit/dd4f3c2fc7893edd914954c73eb577f925a7d361', 'https://lists.apache.org/thread.html/r845e987b7cd8efe610284958e997b84583f5a98d3394adc09e3482fe@%3Cissues.solr.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/r21c406c7ed88fe340db7dbae75e58355159e6c324037c7d5547bf40b@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r5674106135bb1a6ef57483f4c63a9c44bca85d0e2a8a05895a8f1d89@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r6db397ae7281ead825338200d1f62d2827585a70797cc9ac0c4bd23f@%3Cissues.solr.apache.org%3E', 'https://github.com/hunterhacker/jdom/pull/188', 'https://github.com/hunterhacker/jdom/releases', 'https://lists.apache.org/thread.html/rbc075a4ac85e7a8e47420b7383f16ffa0af3b792b8423584735f369f@%3Cissues.solr.apache.org%3E', 'https://alephsecurity.com/vulns/aleph-2021003', 'https://lists.apache.org/thread.html/r89b3800cfabb1e773e49425e5d4239c28a659839a2eca6af3431482e@%3Cissues.solr.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/07/msg00012.html', 'https://github.com/advisories/GHSA-2363-cqg2-863c', 'https://lists.apache.org/thread.html/r9974f64723875052e02787b2a5eda689ac5247c71b827d455e5dc9a6@%3Cissues.solr.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/06/msg00026.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33813', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AH46QHE5GIMT6BL6C3GDTOYF27JYILXM/'} | null | {'https://github.com/hunterhacker/jdom/commit/dd4f3c2fc7893edd914954c73eb577f925a7d361'} | {'https://github.com/hunterhacker/jdom/commit/dd4f3c2fc7893edd914954c73eb577f925a7d361'} |
GHSA | GHSA-3pxp-6963-46r9 | Command Injection in pdfinfojs | Versions of `pdfinfojs` before 0.4.1 are vulnerable to command injection. This is exploitable if an attacker can control the filename parameter that is passed into the `pdfinfojs` constructor.
## Recommendation
Update to version 0.4.1 or later. | {'CVE-2018-3746'} | 2021-01-08T20:00:19Z | 2018-06-07T19:43:00Z | HIGH | 0 | {'CWE-77'} | {'https://hackerone.com/reports/330957', 'https://www.npmjs.com/advisories/643', 'https://github.com/advisories/GHSA-3pxp-6963-46r9', 'https://github.com/fagbokforlaget/pdfinfojs/commit/5cc59cd8aa13ca8d16bb41da8affdfef370ad4fd', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3746'} | null | {'https://github.com/fagbokforlaget/pdfinfojs/commit/5cc59cd8aa13ca8d16bb41da8affdfef370ad4fd'} | {'https://github.com/fagbokforlaget/pdfinfojs/commit/5cc59cd8aa13ca8d16bb41da8affdfef370ad4fd'} |
GHSA | GHSA-g2xc-35jw-c63p | HTTP Request Smuggling: Invalid Transfer-Encoding in Waitress | ### Impact
Waitress would parse the `Transfer-Encoding` header and only look for a single string value, if that value was not `chunked` it would fall through and use the `Content-Length` header instead.
According to the HTTP standard `Transfer-Encoding` should be a comma separated list, with the inner-most encoding first, followed by any further transfer codings, ending with `chunked`.
Requests sent with:
```
Transfer-Encoding: gzip, chunked
```
Would incorrectly get ignored, and the request would use a `Content-Length` header instead to determine the body size of the HTTP message.
This could allow for Waitress to treat a single request as multiple requests in the case of HTTP pipelining.
### Patches
This issue is fixed in Waitress 1.4.0. This brings a range of changes to harden Waitress against potential HTTP request confusions, and may change the behaviour of Waitress behind non-conformist proxies.
Waitress will now return a 501 Not Implemented error if the `Transfer-Encoding` is not `chunked` or contains multiple elements. Waitress does not support any transfer codings such as `gzip` or `deflate`.
The Pylons Project recommends upgrading as soon as possible, while validating that the changes in Waitress don't cause any changes in behavior.
### Workarounds
Various reverse proxies may have protections against sending potentially bad HTTP requests to the backend, and or hardening against potential issues like this. If the reverse proxy doesn't use HTTP/1.1 for connecting to the backend issues are also somewhat mitigated, as HTTP pipelining does not exist in HTTP/1.0 and Waitress will close the connection after every single request (unless the Keep Alive header is explicitly sent... so this is not a fool proof security method).
### Issues/more security issues:
* open an issue at https://github.com/Pylons/waitress/issues (if not sensitive or security related)
* email the Pylons Security mailing list: pylons-project-security@googlegroups.com (if security related) | {'CVE-2019-16786'} | 2022-04-25T23:07:25Z | 2019-12-20T23:04:18Z | HIGH | 7.1 | {'CWE-444'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-16786', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LYEOTGWJZVKPRXX2HBNVIYWCX73QYPM5/', 'https://github.com/Pylons/waitress/commit/f11093a6b3240fc26830b6111e826128af7771c3', 'https://access.redhat.com/errata/RHSA-2020:0720', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GVDHR2DNKCNQ7YQXISJ45NT4IQDX3LJ7/', 'https://github.com/Pylons/waitress/security/advisories/GHSA-g2xc-35jw-c63p', 'https://docs.pylonsproject.org/projects/waitress/en/latest/#security-fixes', 'https://github.com/advisories/GHSA-g2xc-35jw-c63p'} | null | {'https://github.com/Pylons/waitress/commit/f11093a6b3240fc26830b6111e826128af7771c3'} | {'https://github.com/Pylons/waitress/commit/f11093a6b3240fc26830b6111e826128af7771c3'} |
GHSA | GHSA-rch9-xh7r-mqgw | Cross-Site Scripting in simple-server | Versions of `simple-server` before 1.1.0 are vulnerable to stored cross-site scripting (XSS). This is exploitable if an attacker can control a filename on the server.
## Recommendation
Update to version 1.1.0 or later. | {'CVE-2018-3717'} | 2021-01-08T01:58:09Z | 2018-07-26T15:08:05Z | HIGH | 0 | {'CWE-79'} | {'https://github.com/senchalabs/connect/commit/6d5dd30075d2bc4ee97afdbbe3d9d98d8d52d74b', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3717', 'https://hackerone.com/reports/309394', 'https://hackerone.com/reports/309641', 'https://www.npmjs.com/advisories/595', 'https://www.npmjs.com/advisories/584', 'https://github.com/JacksonTian/anywhere/issues/33#issuecomment-366527448', 'https://github.com/advisories/GHSA-rch9-xh7r-mqgw'} | null | {'https://github.com/senchalabs/connect/commit/6d5dd30075d2bc4ee97afdbbe3d9d98d8d52d74b'} | {'https://github.com/senchalabs/connect/commit/6d5dd30075d2bc4ee97afdbbe3d9d98d8d52d74b'} |
GHSA | GHSA-qg54-694p-wgpp | Regular expression denial of service vulnerability (ReDoS) in date | Date’s parsing methods including Date.parse are using Regexps internally, some of which are vulnerable against regular expression denial of service. Applications and libraries that apply such methods to untrusted input may be affected.
The fix limits the input length up to 128 bytes by default instead of changing the regexps. This is because Date gem uses many Regexps and it is possible that there are still undiscovered vulnerable Regexps. For compatibility, it is allowed to remove the limitation by explicitly passing limit keywords as nil like Date.parse(str, limit: nil), but note that it may take a long time to parse.
Please update the date gem to version 3.2.1, 3.1.2, 3.0.2, and 2.0.1, or later. You can use gem update date to update it. If you are using bundler, please add gem "date", ">= 3.2.1" to your Gemfile. If you import `date` from the standard library rather than as a gem you should update your Ruby install to `3.0.3`, `2.7.5`, `2.6.9` or later.
Users unable to upgrade may consider using `Date.strptime` instead with a predefined date format
```ruby
Date.strptime('2001-02-20', '%Y-%m-%d')
``` | {'CVE-2021-41817'} | 2022-03-17T23:00:37Z | 2021-11-16T00:32:30Z | MODERATE | 0 | {'CWE-1333'} | {'https://github.com/advisories/GHSA-qg54-694p-wgpp', 'https://hackerone.com/reports/1254844', 'https://www.ruby-lang.org/en/news/2021/11/15/date-parsing-method-regexp-dos-cve-2021-41817/', 'https://github.com/ruby/date/commit/3959accef8da5c128f8a8e2fd54e932a4fb253b0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41817'} | null | {'https://github.com/ruby/date/commit/3959accef8da5c128f8a8e2fd54e932a4fb253b0'} | {'https://github.com/ruby/date/commit/3959accef8da5c128f8a8e2fd54e932a4fb253b0'} |
GHSA | GHSA-9j59-75qj-795w | Path traversal in Pillow | If the path to the temporary directory on Linux or macOS contained a space, this would break removal of the temporary image file after im.show() (and related actions), and potentially remove an unrelated file. This been present since PIL. | {'CVE-2022-24303'} | 2022-04-07T15:09:46Z | 2022-03-11T23:10:32Z | CRITICAL | 9.1 | null | {'https://github.com/python-pillow/Pillow/pull/3450', 'https://pillow.readthedocs.io/en/stable/releasenotes/9.0.1.html#security', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XR6UP2XONXOVXI4446VY72R63YRO2YTP/', 'https://github.com/python-pillow/Pillow/commit/427221ef5f19157001bf8b1ad7cfe0b905ca8c26', 'https://github.com/advisories/GHSA-9j59-75qj-795w', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/W4ZUXPKEX72O3E5IHBPVY5ZCPMJ4GHHV/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24303'} | null | {'https://github.com/python-pillow/Pillow/commit/427221ef5f19157001bf8b1ad7cfe0b905ca8c26'} | {'https://github.com/python-pillow/Pillow/commit/427221ef5f19157001bf8b1ad7cfe0b905ca8c26'} |
GHSA | GHSA-v648-p92f-9996 | 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-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937. | {'CVE-2019-0925'} | 2021-03-29T20:57:39Z | 2021-03-29T20:57:39Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0925', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0925', 'https://github.com/chakra-core/ChakraCore/commit/32ca10f3955f2a3ca56c6671c721b1264eca06b8', 'https://github.com/advisories/GHSA-v648-p92f-9996'} | null | {'https://github.com/chakra-core/ChakraCore/commit/32ca10f3955f2a3ca56c6671c721b1264eca06b8', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/32ca10f3955f2a3ca56c6671c721b1264eca06b8'} |
GHSA | GHSA-jfcc-rm7f-xgf8 | Cross-Site Scripting in mavon-editor | All versions of `mavon-editor` are vulnerable to Cross-Site Scripting. The package fails to sanitize entered input, allowing attackers to execute arbitrary JavaScript in a victim's browser.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | null | 2021-11-29T17:41:18Z | 2020-09-03T20:36:35Z | MODERATE | 6.5 | {'CWE-79'} | {'https://github.com/hinesboy/mavonEditor/commit/5592ec3761bd3b5a12ba6f99ce3c4057c6e33f72', 'https://www.npmjs.com/advisories/1169', 'https://www.npmjs.com/package/mavon-editor', 'https://github.com/hinesboy/mavonEditor/pull/548', 'https://snyk.io/vuln/SNYK-JS-MAVONEDITOR-459108', 'https://github.com/hinesboy/mavonEditor/issues/472', 'https://github.com/advisories/GHSA-jfcc-rm7f-xgf8'} | null | {'https://github.com/hinesboy/mavonEditor/commit/5592ec3761bd3b5a12ba6f99ce3c4057c6e33f72'} | {'https://github.com/hinesboy/mavonEditor/commit/5592ec3761bd3b5a12ba6f99ce3c4057c6e33f72'} |
GHSA | GHSA-5875-p652-2ppm | Exposure of Resource to Wrong Sphere in microweber | Exposure of Resource to Wrong Sphere in microweber prior to 1.3 allows users to add deleted products to a cart and buy it. | {'CVE-2022-0762'} | 2022-03-09T20:31:40Z | 2022-02-27T00:00:16Z | MODERATE | 4.3 | {'CWE-668'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0762', 'https://github.com/advisories/GHSA-5875-p652-2ppm', 'https://huntr.dev/bounties/125b5244-5099-485e-bf75-e5f1ed80dd48', 'https://github.com/microweber/microweber/commit/76361264d9fdfff38a1af79c63141455cc4d36e3'} | null | {'https://github.com/microweber/microweber/commit/76361264d9fdfff38a1af79c63141455cc4d36e3'} | {'https://github.com/microweber/microweber/commit/76361264d9fdfff38a1af79c63141455cc4d36e3'} |
GHSA | GHSA-4v5p-v5h9-6xjx | `CHECK`-failures in Tensorflow | ### Impact
An attacker can trigger denial of service via assertion failure by altering a `SavedModel` on disk such that `AttrDef`s of some operation are duplicated.
### Patches
We have patched the issue in GitHub commit [c2b31ff2d3151acb230edc3f5b1832d2c713a9e0](https://github.com/tensorflow/tensorflow/commit/c2b31ff2d3151acb230edc3f5b1832d2c713a9e0).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2022-23565'} | 2022-02-11T15:06:54Z | 2022-02-09T23:49:01Z | MODERATE | 6.5 | {'CWE-617'} | {'https://github.com/advisories/GHSA-4v5p-v5h9-6xjx', 'https://github.com/tensorflow/tensorflow/commit/c2b31ff2d3151acb230edc3f5b1832d2c713a9e0', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4v5p-v5h9-6xjx', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23565'} | null | {'https://github.com/tensorflow/tensorflow/commit/c2b31ff2d3151acb230edc3f5b1832d2c713a9e0'} | {'https://github.com/tensorflow/tensorflow/commit/c2b31ff2d3151acb230edc3f5b1832d2c713a9e0'} |
GHSA | GHSA-5x33-h32w-6vr2 | Cross site-scripting (XSS) moodle | The filter in the tag manager required extra sanitizing to prevent a reflected XSS risk. This affects 3.9 to 3.9.1, 3.8 to 3.8.4, 3.7 to 3.7.7, 3.5 to 3.5.13 and earlier unsupported versions. Fixed in 3.9.2, 3.8.5, 3.7.8 and 3.5.14. | {'CVE-2020-25628'} | 2021-03-29T20:43:15Z | 2021-03-29T20:43:15Z | MODERATE | 6.1 | {'CWE-79'} | {'https://moodle.org/mod/forum/discuss.php?d=410840', 'https://github.com/moodle/moodle/commit/e8632a4ad0b4da3763cbbe5949594aa449b483bb', 'http://git.moodle.org/gw?p=moodle.git&a=search&h=HEAD&st=commit&s=MDL-69340', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25628', 'https://github.com/advisories/GHSA-5x33-h32w-6vr2'} | null | {'https://github.com/moodle/moodle/commit/e8632a4ad0b4da3763cbbe5949594aa449b483bb'} | {'https://github.com/moodle/moodle/commit/e8632a4ad0b4da3763cbbe5949594aa449b483bb'} |
GHSA | GHSA-vgwr-773q-7j3c | Path Traversal within joomla/archive zip class | An issue was discovered in Joomla! 3.0.0 through 3.9.24. Extracting an specifilcy crafted zip package could write files outside of the intended path. | {'CVE-2021-26028'} | 2021-03-24T17:58:13Z | 2021-03-24T17:58:13Z | MODERATE | 0 | {'CWE-22'} | {'https://github.com/FriendsOfPHP/security-advisories/blob/master/joomla/archive/CVE-2021-26028.yaml', 'https://github.com/joomla-framework/archive/commit/32c9009a1020d16bc1060c0d06339898b697cf2c', 'https://github.com/advisories/GHSA-vgwr-773q-7j3c', 'https://developer.joomla.org/security-centre/848-20210308-core-path-traversal-within-joomla-archive-zip-class.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26028'} | null | {'https://github.com/joomla-framework/archive/commit/32c9009a1020d16bc1060c0d06339898b697cf2c'} | {'https://github.com/joomla-framework/archive/commit/32c9009a1020d16bc1060c0d06339898b697cf2c'} |
GHSA | GHSA-56cx-wf47-hx7w | Improper Restriction of Excessive Authentication Attempts | firefly-iii is vulnerable to Improper Restriction of Excessive Authentication Attempts | {'CVE-2021-3663'} | 2021-08-31T20:58:22Z | 2021-08-09T20:38:37Z | MODERATE | 5.3 | {'CWE-307'} | {'https://github.com/firefly-iii/firefly-iii/releases/tag/5.5.13', 'https://github.com/firefly-iii/firefly-iii/commit/afc9f4b7ebc8a240c85864a6e1abda62bfeefae8', 'https://github.com/advisories/GHSA-56cx-wf47-hx7w', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3663', 'https://huntr.dev/bounties/497bdf6d-7dba-49c3-8011-1c64dfbb3380'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/afc9f4b7ebc8a240c85864a6e1abda62bfeefae8'} | {'https://github.com/firefly-iii/firefly-iii/commit/afc9f4b7ebc8a240c85864a6e1abda62bfeefae8'} |
GHSA | GHSA-3fjq-93xj-3f3f | Cross-Site Scripting in serialize-to-js | Versions of `serialize-to-js` prior to 3.0.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.
## Recommendation
Upgrade to version 3.0.1 or later. | {'CVE-2019-16772'} | 2021-01-08T20:02:21Z | 2019-12-06T23:20:26Z | MODERATE | 3.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-3fjq-93xj-3f3f', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16772', 'https://www.npmjs.com/advisories/1429', 'https://github.com/commenthol/serialize-to-js/security/advisories/GHSA-3fjq-93xj-3f3f', 'https://github.com/commenthol/serialize-to-js/commit/181d7d583ae5293cd47cc99b14ad13352875f3e3'} | null | {'https://github.com/commenthol/serialize-to-js/commit/181d7d583ae5293cd47cc99b14ad13352875f3e3'} | {'https://github.com/commenthol/serialize-to-js/commit/181d7d583ae5293cd47cc99b14ad13352875f3e3'} |
GHSA | GHSA-wv23-pfj7-2mjj | Authenticated file write leads to remote code execution in october/system | ### Impact
Assuming an attacker with "create, modify and delete website pages" privileges in the backend is able to execute PHP code by running specially crafted Twig code in the template markup.
### Patches
Issue has been patched in Build 473 and v1.1.6
### Workarounds
Apply https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26 to your installation manually if you are unable to upgrade.
### References
Credits to:
• David Miller
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
| {'CVE-2021-32649'} | 2022-04-19T19:03:20Z | 2022-01-14T21:08:23Z | HIGH | 8.8 | {'CWE-74'} | {'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26', 'https://github.com/advisories/GHSA-wv23-pfj7-2mjj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32649', 'https://github.com/octobercms/october/security/advisories/GHSA-wv23-pfj7-2mjj'} | null | {'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26'} | {'https://github.com/octobercms/october/commit/167b592eed291ae1563c8fcc5b9b34a03a300f26'} |
GHSA | GHSA-mcx4-f5f5-4859 | Prevent cache poisoning via a Response Content-Type header in Symfony | Description
-----------
When a `Response` does not contain a `Content-Type` header, Symfony falls back to the format defined in the `Accept` header of the request, leading to a possible mismatch between the response's content and `Content-Type` header. When the response is cached, this can lead to a corrupted cache where the cached format is not the right one.
Resolution
----------
Symfony does not use the `Accept` header anymore to guess the `Content-Type`.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6) for the 4.4 branch.
Credits
-------
I would like to thank Xavier Lacot from JoliCode for reporting & Yonel Ceruto and Tobias Schultze for fixing the issue. | {'CVE-2020-5255'} | 2022-04-19T19:02:57Z | 2020-03-30T20:09:16Z | LOW | 2.6 | {'CWE-435'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C36JLPHUPKDFAX6D5WYFC4ALO2K7RDUQ/', 'https://github.com/advisories/GHSA-mcx4-f5f5-4859', 'https://github.com/symfony/symfony/security/advisories/GHSA-mcx4-f5f5-4859', 'https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6', 'https://symfony.com/blog/cve-2020-5255-prevent-cache-poisoning-via-a-response-content-type-header', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5255'} | null | {'https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6'} | {'https://github.com/symfony/symfony/commit/dca343442e6a954f96a2609e7b4e9c21ed6d74e6'} |
GHSA | GHSA-qr82-2c78-4m8h | Reference binding to nullptr in map operations | ### Impact
An attacker can cause undefined behavior via binding a reference to null pointer in `tf.raw_ops.Map*` and `tf.raw_ops.OrderedMap*` operations:
```python
import tensorflow as tf
tf.raw_ops.MapPeek(
key=tf.constant([8],dtype=tf.int64),
indices=[],
dtypes=[tf.int32],
capacity=8,
memory_limit=128)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/map_stage_op.cc#L222-L248) has a check in place to ensure that `indices` is in ascending order, but does not check that `indices` is not empty.
### Patches
We have patched the issue in GitHub commit [532f5c5a547126c634fefd43bbad1dc6417678ac](https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac).
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-37671'} | 2021-08-25T14:41:42Z | 2021-08-25T14:41:42Z | HIGH | 7.8 | {'CWE-824'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qr82-2c78-4m8h', 'https://github.com/advisories/GHSA-qr82-2c78-4m8h', 'https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37671'} | null | {'https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac'} | {'https://github.com/tensorflow/tensorflow/commit/532f5c5a547126c634fefd43bbad1dc6417678ac'} |
GHSA | GHSA-j7px-6hwj-hpjg | Open Redirect in OAuth2 Proxy | ### Impact
As users can provide a redirect address for the proxy to send the authenticated user to at the end of the authentication flow. This is expected to be the original URL that the user was trying to access.
This redirect URL is checked within the proxy and validated before redirecting the user to prevent malicious actors providing redirects to potentially harmful sites.
However, by crafting a redirect URL with HTML encoded whitespace characters (eg. `%0a`, `%0b`,`%09`,`%0d`) the validation could be bypassed and allow a redirect to any URL provided.
### Patches
@rootxharsh and @iamnoooob provided this patch as potential solution:
```
From 4b941f56eda310b5c4dc8080b7635a6bfabccad4 Mon Sep 17 00:00:00 2001
From: Harsh Jaiswal <harsh@pop-os.localdomain>
Date: Fri, 1 May 2020 20:38:31 +0530
Subject: [PATCH] Fixes redirect issue
---
oauthproxy.go | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/oauthproxy.go b/oauthproxy.go
index 1e9bb7c..f8beb4d 100644
--- a/oauthproxy.go
+++ b/oauthproxy.go
@@ -577,8 +577,9 @@ func validOptionalPort(port string) bool {
// IsValidRedirect checks whether the redirect URL is whitelisted
func (p *OAuthProxy) IsValidRedirect(redirect string) bool {
+ matched, _ := regexp.MatchString(`^/\s+/|\\`, redirect)
switch {
- case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"):
+ case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !matched:
return true
case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"):
redirectURL, err := url.Parse(redirect)
--
2.17.1
```
This issue was also reported to us separately by @mik317 several hours later
The fix was implemented in [#xxx]() and released as version 5.1.1 | {'CVE-2020-11053'} | 2022-04-19T19:02:25Z | 2021-12-20T17:59:10Z | HIGH | 7.1 | {'CWE-601'} | {'https://github.com/advisories/GHSA-j7px-6hwj-hpjg', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-j7px-6hwj-hpjg', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11053'} | null | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43'} | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/0d5fa211df8ef2449347a56b22c779eb8d894c43'} |
GHSA | GHSA-hwvq-6gjx-j797 | Special Element Injection in notebook | ### Impact
Untrusted notebook can execute code on load. This is a remote code execution, but requires user action to open a notebook.
### Patches
5.7.11, 6.4.1
### References
[OWASP Page on Injection Prevention](https://cheatsheetseries.owasp.org/cheatsheets/Injection_Prevention_Cheat_Sheet.html#injection-prevention-rules)
### For more information
If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list security@ipython.org.
Credit: Guillaume Jeanne from Google
### Example:
A notebook with the following content in a cell and it would display an alert when opened for the first time in Notebook (in an untrusted state):
```
{ "cell_type": "code", "execution_count": 0, "metadata": {}, "outputs": [ { "data": { "text/html": [ "<select><iframe></select><img src=x: onerror=alert('xss')>\n"], "text/plain": [] }, "metadata": {}, "output_type": "display_data" } ], "source": [ "" ] }
```` | {'CVE-2021-32798'} | 2022-04-19T19:03:05Z | 2021-08-23T19:40:38Z | CRITICAL | 10 | {'CWE-79'} | {'https://github.com/jupyter/notebook/security/advisories/GHSA-hwvq-6gjx-j797', 'https://github.com/advisories/GHSA-hwvq-6gjx-j797', 'https://github.com/jupyter/notebook/commit/79fc76e890a8ec42f73a3d009e44ef84c14ef0d5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32798'} | null | {'https://github.com/jupyter/notebook/commit/79fc76e890a8ec42f73a3d009e44ef84c14ef0d5'} | {'https://github.com/jupyter/notebook/commit/79fc76e890a8ec42f73a3d009e44ef84c14ef0d5'} |
GHSA | GHSA-6gv8-p3vj-pxvr | Null pointer dereference in `UncompressElement` | ### Impact
The code for `tf.raw_ops.UncompressElement` can be made to trigger a null pointer dereference:
```python
import tensorflow as tf
data = tf.data.Dataset.from_tensors([0.0])
tf.raw_ops.UncompressElement(
compressed=tf.data.experimental.to_variant(data),
output_types=[tf.int64],
output_shapes=[2])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/data/experimental/compression_ops.cc#L50-L53) obtains a pointer to a `CompressedElement` from a `Variant` tensor and then proceeds to dereference it for decompressing. There is no check that the `Variant` tensor contained a `CompressedElement`, so the pointer is actually `nullptr`.
### Patches
We have patched the issue in GitHub commit [7bdf50bb4f5c54a4997c379092888546c97c3ebd](https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd).
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-37649'} | 2021-08-25T14:43:27Z | 2021-08-25T14:43:27Z | HIGH | 7.7 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37649', 'https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6gv8-p3vj-pxvr', 'https://github.com/advisories/GHSA-6gv8-p3vj-pxvr'} | null | {'https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd'} | {'https://github.com/tensorflow/tensorflow/commit/7bdf50bb4f5c54a4997c379092888546c97c3ebd'} |
GHSA | GHSA-x8h6-xgqx-jqgp | Undefined behavior and `CHECK`-fail in `FractionalMaxPoolGrad` | ### Impact
The implementation of `tf.raw_ops.FractionalMaxPoolGrad` triggers an undefined behavior if one of the input tensors is empty:
```python
import tensorflow as tf
orig_input = tf.constant([2, 3], shape=[1, 1, 1, 2], dtype=tf.int64)
orig_output = tf.constant([], dtype=tf.int64)
out_backprop = tf.zeros([2, 3, 6, 6], dtype=tf.int64)
row_pooling_sequence = tf.constant([0], shape=[1], dtype=tf.int64)
col_pooling_sequence = tf.constant([0], shape=[1], dtype=tf.int64)
tf.raw_ops.FractionalMaxPoolGrad(
orig_input=orig_input, orig_output=orig_output, out_backprop=out_backprop,
row_pooling_sequence=row_pooling_sequence,
col_pooling_sequence=col_pooling_sequence, overlapping=False)
```
The code is also vulnerable to a denial of service attack as a `CHECK` condition becomes false and aborts the process
```python
import tensorflow as tf
orig_input = tf.constant([1], shape=[1], dtype=tf.int64)
orig_output = tf.constant([1], shape=[1], dtype=tf.int64)
out_backprop = tf.constant([1, 1], shape=[2, 1, 1, 1], dtype=tf.int64)
row_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)
col_pooling_sequence = tf.constant([1], shape=[1], dtype=tf.int64)
tf.raw_ops.FractionalMaxPoolGrad(
orig_input=orig_input, orig_output=orig_output, out_backprop=out_backprop,
row_pooling_sequence=row_pooling_sequence,
col_pooling_sequence=col_pooling_sequence, overlapping=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/169054888d50ce488dfde9ca55d91d6325efbd5b/tensorflow/core/kernels/fractional_max_pool_op.cc#L215) fails to validate that input and output tensors are not empty and are of the same rank. Each of these unchecked assumptions is responsible for the above issues.
### Patches
We have patched the issue in GitHub commit [32fdcbff9d06d010d908fcc4bd4b36eb3ce15925](https://github.com/tensorflow/tensorflow/commit/32fdcbff9d06d010d908fcc4bd4b36eb3ce15925).
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-29580'} | 2021-05-21T14:26:26Z | 2021-05-21T14:26:26Z | LOW | 2.5 | {'CWE-908'} | {'https://github.com/tensorflow/tensorflow/commit/32fdcbff9d06d010d908fcc4bd4b36eb3ce15925', 'https://github.com/advisories/GHSA-x8h6-xgqx-jqgp', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29580', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x8h6-xgqx-jqgp'} | null | {'https://github.com/tensorflow/tensorflow/commit/32fdcbff9d06d010d908fcc4bd4b36eb3ce15925'} | {'https://github.com/tensorflow/tensorflow/commit/32fdcbff9d06d010d908fcc4bd4b36eb3ce15925'} |
GHSA | GHSA-wm77-q74p-5763 | Path Traversal in superstatic | Affected of `superstatic` are vulnerable to path traversal when used on Windows.
Additionally, it is vulnerable to path traversal on other platforms combined with certain Node.js versions which erroneously normalize `\\` to `/` in paths on all platforms (a known example being Node.js v9.9.0).
## Recommendation
Update to version 5.0.2 or later. | null | 2021-08-09T22:21:04Z | 2018-07-27T17:06:03Z | HIGH | 0 | {'CWE-177'} | {'https://github.com/firebase/superstatic/commit/e396ff62f588732989137d6c40d46b310e51ef2b', 'https://github.com/firebase/superstatic/blob/v5.0.1/lib/providers/fs.js#L71', 'https://www.npmjs.com/advisories/652', 'https://github.com/firebase/superstatic/pull/255', 'https://github.com/advisories/GHSA-wm77-q74p-5763'} | null | {'https://github.com/firebase/superstatic/commit/e396ff62f588732989137d6c40d46b310e51ef2b'} | {'https://github.com/firebase/superstatic/commit/e396ff62f588732989137d6c40d46b310e51ef2b'} |
GHSA | GHSA-753c-phhg-cj29 | Improper Neutralization of Special Elements used in a Command | This affects the package madge before 4.0.1. It is possible to specify a custom Graphviz path via the graphVizPath option parameter which when the .image(), .svg() or .dot() functions are called, is executed by the childprocess.exec function. | {'CVE-2021-23352'} | 2021-03-15T18:08:06Z | 2021-03-12T23:01:49Z | HIGH | 0 | {'CWE-89', 'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23352', 'https://snyk.io/vuln/SNYK-JS-MADGE-1082875', 'https://github.com/pahen/madge/commit/da5cbc9ab30372d687fa7c324b22af7ffa5c6332', 'https://github.com/pahen/madge/blob/master/lib/graph.js%23L27', 'https://github.com/advisories/GHSA-753c-phhg-cj29'} | null | {'https://github.com/pahen/madge/commit/da5cbc9ab30372d687fa7c324b22af7ffa5c6332'} | {'https://github.com/pahen/madge/commit/da5cbc9ab30372d687fa7c324b22af7ffa5c6332'} |
GHSA | GHSA-fm9p-5m9f-rq85 | 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-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937. | {'CVE-2019-0915'} | 2021-03-29T21:00:03Z | 2021-03-29T21:00:03Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0915', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0915', 'https://github.com/advisories/GHSA-fm9p-5m9f-rq85', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f'} | null | {'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/d85b5025b047f10784c53c6c1dd771775d417f5f'} |
GHSA | GHSA-xfv3-rrfm-f2rv | Information Exposure in Netty | Netty before 3.9.8.Final, 3.10.x before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5 and Play Framework 2.x before 2.3.9 might allow remote attackers to bypass the httpOnly flag on cookies and obtain sensitive information by leveraging improper validation of cookie name and value characters. | {'CVE-2015-2156'} | 2021-09-22T18:45:31Z | 2020-06-30T21:01:21Z | HIGH | 7.5 | {'CWE-20'} | {'https://github.com/netty/netty/pull/3748/commits/4ac519f534493bb0ca7a77e1c779138a54faa7b9', 'https://github.com/advisories/GHSA-xfv3-rrfm-f2rv', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2015/05/17/1', 'https://lists.apache.org/thread.html/9317fd092b257a0815434b116a8af8daea6e920b6673f4fd5583d5fe@%3Ccommits.druid.apache.org%3E', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-May/159166.html', 'https://github.com/netty/netty/commit/31815598a2af37f0b71ea94eada70d6659c23752', 'https://snyk.io/vuln/SNYK-JAVA-IONETTY-73571', 'http://www.securityfocus.com/bid/74704', 'https://www.playframework.com/security/vulnerability/CVE-2015-2156-HttpOnlyBypass', 'https://lists.apache.org/thread.html/a19bb1003b0d6cd22475ba83c019b4fc7facfef2a9e13f71132529d3@%3Ccommits.cassandra.apache.org%3E', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-June/159379.html', 'https://github.com/netty/netty/commit/2caa38a2795fe1f1ae6ceda4d69e826ed7c55e55', 'https://github.com/netty/netty/pull/3754', 'https://nvd.nist.gov/vuln/detail/CVE-2015-2156', 'http://netty.io/news/2015/05/08/3-9-8-Final-and-3.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=1222923', 'https://lists.apache.org/thread.html/dc1275aef115bda172851a231c76c0932d973f9ffd8bc375c4aba769@%3Ccommits.cassandra.apache.org%3E'} | null | {'https://github.com/netty/netty/commit/2caa38a2795fe1f1ae6ceda4d69e826ed7c55e55', 'https://github.com/netty/netty/pull/3748/commits/4ac519f534493bb0ca7a77e1c779138a54faa7b9', 'https://github.com/netty/netty/commit/31815598a2af37f0b71ea94eada70d6659c23752'} | {'https://github.com/netty/netty/pull/3748/commits/4ac519f534493bb0ca7a77e1c779138a54faa7b9', 'https://github.com/netty/netty/commit/2caa38a2795fe1f1ae6ceda4d69e826ed7c55e55', 'https://github.com/netty/netty/commit/31815598a2af37f0b71ea94eada70d6659c23752'} |
GHSA | GHSA-mh74-4m5g-fcjx | Malicious users could control the content of invitation emails | ### Impact
A malicious user could abuse Sydent to send out arbitrary emails from the Sydent email address. This could be used to construct plausible phishing emails, for example.
### Patches
Fixed in 4469d1d, 6b405a8, 65a6e91.
Note that these patches include changes to the *default* email templates. If these templates have been locally modified, they must also be updated.
### For more information
If you have any questions or comments about this advisory, email us at security@matrix.org. | {'CVE-2021-29432'} | 2021-04-19T14:54:24Z | 2021-04-19T14:54:24Z | MODERATE | 5.3 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29432', 'https://github.com/matrix-org/sydent/security/advisories/GHSA-mh74-4m5g-fcjx', 'https://github.com/matrix-org/sydent/commit/4469d1d42b2b1612b70638224c07e19623039c42', 'https://github.com/advisories/GHSA-mh74-4m5g-fcjx', 'https://github.com/matrix-org/sydent/releases/tag/v2.3.0', 'https://pypi.org/project/matrix-sydent/'} | null | {'https://github.com/matrix-org/sydent/commit/4469d1d42b2b1612b70638224c07e19623039c42'} | {'https://github.com/matrix-org/sydent/commit/4469d1d42b2b1612b70638224c07e19623039c42'} |
GHSA | GHSA-9fcc-7g44-mxrj | Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to stored cross-site scripting via uploading files with files in `.xsd`, `.asa`, and `.aspx` formats. | {'CVE-2022-0942'} | 2022-03-29T21:28:00Z | 2022-03-16T00:00:47Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-9fcc-7g44-mxrj', 'https://huntr.dev/bounties/a412707c-18da-4c84-adc0-9801ed8068c9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0942', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | null | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} |
GHSA | GHSA-f522-ffg8-j8r6 | Regular Expression Denial of Service in is-my-json-valid | Version of `is-my-json-valid` before 1.4.1 or 2.17.2 are vulnerable to regular expression denial of service (ReDoS) via the email validation function.
## Recommendation
Update to version 1.4.1, 2.17.2 or later. | {'CVE-2016-2537'} | 2021-09-09T21:38:37Z | 2017-10-24T18:33:35Z | HIGH | 7.5 | {'CWE-20'} | {'https://www.npmjs.com/advisories/76', 'https://www.npmjs.com/advisories/572', 'https://nodesecurity.io/advisories/76', 'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976', 'https://github.com/advisories/GHSA-f522-ffg8-j8r6', 'https://nvd.nist.gov/vuln/detail/CVE-2016-2537', 'https://hackerone.com/reports/317548', 'https://github.com/mafintosh/is-my-json-valid/commit/eca4beb21e61877d76fdf6bea771f72f39544d9b', 'https://github.com/mafintosh/is-my-json-valid/pull/159'} | null | {'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976', 'https://github.com/mafintosh/is-my-json-valid/commit/eca4beb21e61877d76fdf6bea771f72f39544d9b'} | {'https://github.com/mafintosh/is-my-json-valid/commit/eca4beb21e61877d76fdf6bea771f72f39544d9b', 'https://github.com/mafintosh/is-my-json-valid/commit/b3051b277f7caa08cd2edc6f74f50aeda65d2976'} |
GHSA | GHSA-m56g-3g8v-2rxw | XSS in Adminer | **Withdrawn:** Duplicate of GHSA-9pgx-gcph-mpqr.
Adminer before 4.7.9 allows XSS via the history parameter to the default URI. | {'CVE-2020-35572'} | 2021-02-11T20:46:56Z | 2021-02-11T20:46:53Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-m56g-3g8v-2rxw', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35572', 'https://sourceforge.net/p/adminer/bugs-and-features/775/', 'https://sourceforge.net/p/adminer/news/', 'https://sourceforge.net/p/adminer/news/2021/02/adminer-479-released/', 'https://github.com/vrana/adminer/commit/5c395afc098e501be3417017c6421968aac477bd', 'https://github.com/vrana/adminer'} | null | {'https://github.com/vrana/adminer/commit/5c395afc098e501be3417017c6421968aac477bd'} | {'https://github.com/vrana/adminer/commit/5c395afc098e501be3417017c6421968aac477bd'} |
GHSA | GHSA-m434-m5pv-p35w | Insufficient user authorization in Moodle | A flaw was found in Moodle in versions 3.11 to 3.11.4, 3.10 to 3.10.8, 3.9 to 3.9.11 and earlier unsupported versions. The calendar:manageentries capability allowed managers to access or modify any calendar event, but should have been restricted from accessing user level events. | {'CVE-2022-0333'} | 2022-02-02T16:12:14Z | 2022-01-28T22:08:02Z | LOW | 3.8 | {'CWE-863'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0333', 'https://github.com/advisories/GHSA-m434-m5pv-p35w', 'https://github.com/moodle/moodle/commit/2ee27313cea0d7073f5a6a35eccdfddcb3a9adad', 'https://moodle.org/mod/forum/discuss.php?d=431100', 'https://bugzilla.redhat.com/show_bug.cgi?id=2043663'} | null | {'https://github.com/moodle/moodle/commit/2ee27313cea0d7073f5a6a35eccdfddcb3a9adad'} | {'https://github.com/moodle/moodle/commit/2ee27313cea0d7073f5a6a35eccdfddcb3a9adad'} |
GHSA | GHSA-7hmh-8gwv-mfvq | SQL Injection in Kylin | Kylin has some restful apis which will concatenate SQLs with the user input string, a user is likely to be able to run malicious database queries. | {'CVE-2020-1937'} | 2021-09-22T21:57:08Z | 2020-07-27T22:51:47Z | MODERATE | 6.5 | {'CWE-89'} | {'https://lists.apache.org/thread.html/r021baf9d8d4ae41e8c8332c167c4fa96c91b5086563d9be55d2d7acf@%3Ccommits.kylin.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1937', 'https://lists.apache.org/thread.html/r61666760d8a4e8764b2d5fe158d8a48b569414480fbfadede574cdc0@%3Ccommits.kylin.apache.org%3E', 'https://lists.apache.org/thread.html/rc574fef23740522f62ab3bbda4f6171be98aa7a25f3f54be143a80a8%40%3Cuser.kylin.apache.org%3E', 'https://github.com/advisories/GHSA-7hmh-8gwv-mfvq', 'https://snyk.io/vuln/SNYK-JAVA-ORGAPACHEKYLIN-552148', 'https://github.com/apache/kylin/commit/e373c64c96a54a7abfe4bccb82e8feb60db04749'} | null | {'https://github.com/apache/kylin/commit/e373c64c96a54a7abfe4bccb82e8feb60db04749'} | {'https://github.com/apache/kylin/commit/e373c64c96a54a7abfe4bccb82e8feb60db04749'} |
GHSA | GHSA-cfx7-2xpc-8w4h | Division by zero in TFLite's implementation of `BatchToSpaceNd` | ### Impact
The implementation of the `BatchToSpaceNd` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/b5ed552fe55895aee8bd8b191f744a069957d18d/tensorflow/lite/kernels/batch_to_space_nd.cc#L81-L82):
```cc
TF_LITE_ENSURE_EQ(context, output_batch_size % block_shape[dim], 0);
output_batch_size = output_batch_size / block_shape[dim];
```
An attacker can craft a model such that one dimension of the `block` input is 0. Hence, the corresponding value in `block_shape` is 0.
### Patches
We have patched the issue in GitHub commit [2c74674348a4708ced58ad6eb1b23354df8ee044](https://github.com/tensorflow/tensorflow/commit/2c74674348a4708ced58ad6eb1b23354df8ee044).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29593'} | 2021-05-21T14:27:01Z | 2021-05-21T14:27:01Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cfx7-2xpc-8w4h', 'https://github.com/advisories/GHSA-cfx7-2xpc-8w4h', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29593', 'https://github.com/tensorflow/tensorflow/commit/2c74674348a4708ced58ad6eb1b23354df8ee044'} | null | {'https://github.com/tensorflow/tensorflow/commit/2c74674348a4708ced58ad6eb1b23354df8ee044'} | {'https://github.com/tensorflow/tensorflow/commit/2c74674348a4708ced58ad6eb1b23354df8ee044'} |
GHSA | GHSA-gf7x-2j2x-7f73 | Missing authorization in xwiki-platform | ### Impact
Any user with edit right can copy the content of a page it does not have access to by using it as template of a new page.
### Patches
It has been patched in XWiki 13.2CR1 and 12.10.6
### Workarounds
There is no workaround beside patching.
### References
https://jira.xwiki.org/browse/XWIKI-18430
### 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 [our security mailing list](mailto:security@xwiki.org)
| {'CVE-2022-23617'} | 2022-02-11T15:01:15Z | 2022-02-09T21:41:46Z | MODERATE | 6.5 | {'CWE-862'} | {'https://github.com/xwiki/xwiki-platform/commit/b35ef0edd4f2ff2c974cbeef6b80fcf9b5a44554', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23617', 'https://jira.xwiki.org/browse/XWIKI-18430', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-gf7x-2j2x-7f73', 'https://github.com/advisories/GHSA-gf7x-2j2x-7f73', 'https://github.com/xwiki/xwiki-platform/commit/30c52b01559b8ef5ed1035dac7c34aaf805764d5'} | null | {'https://github.com/xwiki/xwiki-platform/commit/30c52b01559b8ef5ed1035dac7c34aaf805764d5', 'https://github.com/xwiki/xwiki-platform/commit/b35ef0edd4f2ff2c974cbeef6b80fcf9b5a44554'} | {'https://github.com/xwiki/xwiki-platform/commit/30c52b01559b8ef5ed1035dac7c34aaf805764d5', 'https://github.com/xwiki/xwiki-platform/commit/b35ef0edd4f2ff2c974cbeef6b80fcf9b5a44554'} |
GHSA | GHSA-pch5-whg9-qr2r | netmask npm package vulnerable to octal input data | The netmask package before 2.0.1 for Node.js mishandles certain unexpected characters in an IP address string, such as an octal digit of 9. This (in some situations) allows attackers to bypass access control that is based on IP addresses. NOTE: this issue exists because of an incomplete fix for CVE-2021-28918. | {'CVE-2021-29418'} | 2021-06-09T23:10:54Z | 2021-03-29T21:32:05Z | MODERATE | 5.3 | {'CWE-20'} | {'https://github.com/advisories/GHSA-pch5-whg9-qr2r', 'https://www.npmjs.com/package/netmask', 'https://security.netapp.com/advisory/ntap-20210604-0001/', 'https://sick.codes/universal-netmask-npm-package-used-by-270000-projects-vulnerable-to-octal-input-data-server-side-request-forgery-remote-file-inclusion-local-file-inclusion-and-more-cve-2021-28918/', 'https://sick.codes/sick-2021-011', 'https://vuln.ryotak.me/advisories/6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29418', 'https://github.com/rs/node-netmask/commit/3f19a056c4eb808ea4a29f234274c67bc5a848f4'} | null | {'https://github.com/rs/node-netmask/commit/3f19a056c4eb808ea4a29f234274c67bc5a848f4'} | {'https://github.com/rs/node-netmask/commit/3f19a056c4eb808ea4a29f234274c67bc5a848f4'} |
GHSA | GHSA-mj63-64x7-57xf | Path traversal in impacket | Multiple path traversal vulnerabilities exist in smbserver.py in Impacket before 0.9.23. An attacker that connects to a running smbserver instance can list and write to arbitrary files via ../ directory traversal. This could potentially be abused to achieve arbitrary code execution by replacing /etc/shadow or an SSH authorized key. | {'CVE-2021-31800'} | 2021-06-18T18:43:14Z | 2021-06-18T18:43:14Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://github.com/SecureAuthCorp/impacket/releases', 'https://github.com/SecureAuthCorp/impacket/blob/cb6d43a677c338db930bc4e9161620832c1ec624/impacket/smbserver.py#L2958', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31800', 'https://github.com/SecureAuthCorp/impacket/blob/cb6d43a677c338db930bc4e9161620832c1ec624/impacket/smbserver.py#L2008', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IPXDPWCAPVX3UWYZ3N2T5OLBSBBUHJP6/', 'https://github.com/SecureAuthCorp/impacket/blob/cb6d43a677c338db930bc4e9161620832c1ec624/impacket/smbserver.py#L3485', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KRV2C5DATXBHG6TF6CEEX54KZ75THQS3/', 'https://github.com/SecureAuthCorp/impacket/blob/cb6d43a677c338db930bc4e9161620832c1ec624/impacket/smbserver.py#L876', 'https://github.com/SecureAuthCorp/impacket/commit/99bd29e3995c254e2d6f6c2e3454e4271665955a', 'https://github.com/SecureAuthCorp/impacket/releases/tag/impacket_0_9_23', 'https://github.com/SecureAuthCorp/impacket/commit/49c643bf66620646884ed141c94e5fdd85bcdd2f', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UF56LYB27LHEIFJTFHU3M75NMNNK2SCG/', 'https://github.com/advisories/GHSA-mj63-64x7-57xf'} | null | {'https://github.com/SecureAuthCorp/impacket/commit/49c643bf66620646884ed141c94e5fdd85bcdd2f', 'https://github.com/SecureAuthCorp/impacket/commit/99bd29e3995c254e2d6f6c2e3454e4271665955a'} | {'https://github.com/SecureAuthCorp/impacket/commit/99bd29e3995c254e2d6f6c2e3454e4271665955a', 'https://github.com/SecureAuthCorp/impacket/commit/49c643bf66620646884ed141c94e5fdd85bcdd2f'} |
GHSA | GHSA-rjmq-6v55-4rjv | Improper Authorization in org.cometd.oort | ### Impact
Internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels.
By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other user's (possibly sensitive) data.
By publishing to those channels, a remote user may be able to create/modify/delete other user's data and modify the cluster structure.
The issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5.
### Patches
The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.
### Workarounds
The workaround is to install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.
This workaround could be implemented in any affected version.
### References
cometd/cometd#1146
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@webtide.com](mailto:security@webtide.com)
### Credits
https://www.redteam-pentesting.de/ | {'CVE-2022-24721'} | 2022-04-19T19:03:24Z | 2022-03-15T19:02:36Z | HIGH | 8.1 | {'CWE-863'} | {'https://github.com/cometd/cometd/issues/1146', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24721', 'https://github.com/cometd/cometd/commit/bb445a143fbf320f17c62e340455cd74acfb5929', 'https://github.com/cometd/cometd/security/advisories/GHSA-rjmq-6v55-4rjv', 'https://github.com/advisories/GHSA-rjmq-6v55-4rjv'} | null | {'https://github.com/cometd/cometd/commit/bb445a143fbf320f17c62e340455cd74acfb5929'} | {'https://github.com/cometd/cometd/commit/bb445a143fbf320f17c62e340455cd74acfb5929'} |
GHSA | GHSA-8mjx-h23h-w2pg | Double free in stack_dst | An issue was discovered in the stack_dst crate before 0.6.1 for Rust. Because of the push_inner behavior, a double free can occur upon a val.clone() panic. | {'CVE-2021-28034'} | 2021-09-01T18:30:44Z | 2021-09-01T18:30:44Z | CRITICAL | 9.8 | {'CWE-415'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-28034', 'https://rustsec.org/advisories/RUSTSEC-2021-0033.html', 'https://github.com/advisories/GHSA-8mjx-h23h-w2pg', 'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d53809e3000f40085f2b229b6b1a33759881d'} | null | {'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d53809e3000f40085f2b229b6b1a33759881d'} | {'https://github.com/thepowersgang/stack_dst-rs/commit/2a4d53809e3000f40085f2b229b6b1a33759881d'} |
GHSA | GHSA-6qq8-5wq3-86rp | Open redirect in Traefik | ## Summary
There exists a potential open redirect vulnerability in Traefik's handling of the `X-Forwarded-Prefix` header. Active Exploitation of this issue is unlikely as it would require active header injection, however the Traefik team addressed this issue nonetheless to prevent abuse in e.g. cache poisoning scenarios.
## Details
The Traefik API dashboard component doesn't validate that the value of the header `X-Forwarded-Prefix` is a site relative path and will redirect to any header provided URI.
e.g.
```
$ curl --header 'Host:traefik.localhost' --header 'X-Forwarded-Prefix:https://example.org' 'http://localhost:8081'
<a href="https://example.org/dashboard/">Found</a>.`
```
### Impact
A successful exploitation of an open redirect can be used to entice victims to disclose sensitive information.
### Workarounds
By using the `headers` middleware, the request header `X-Forwarded-Prefix` value can be overridden by the value `.` (dot)
- https://docs.traefik.io/v2.2/middlewares/headers/#customrequestheaders
- https://docs.traefik.io/v1.7/basics/#custom-headers
### For more information
If you have any questions or comments about this advisory, open an issue in [Traefik](https://github.com/containous/traefik/issues).
## Credit
This issue was found by the GitHub Application Security Team and reported on behalf of the GHAS by the GitHub Security Lab Team. | {'CVE-2020-15129'} | 2022-04-19T19:02:31Z | 2022-02-11T23:19:21Z | MODERATE | 6.1 | {'CWE-601'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15129', 'https://github.com/containous/traefik/pull/7109', 'https://github.com/containous/traefik/releases/tag/v2.3.0-rc3', 'https://github.com/advisories/GHSA-6qq8-5wq3-86rp', 'https://github.com/containous/traefik/security/advisories/GHSA-6qq8-5wq3-86rp', 'https://github.com/containous/traefik/releases/tag/v1.7.26', 'https://github.com/containous/traefik/releases/tag/v2.2.8', 'https://github.com/containous/traefik/commit/cfa04c300c5db95ae8a52c31a9d973b6dd9c2254', 'https://github.com/containous/traefik/commit/e63db782c11c7b8bfce30be4c902e7ef8f9f33d2'} | null | {'https://github.com/containous/traefik/commit/cfa04c300c5db95ae8a52c31a9d973b6dd9c2254', 'https://github.com/containous/traefik/commit/e63db782c11c7b8bfce30be4c902e7ef8f9f33d2'} | {'https://github.com/containous/traefik/commit/cfa04c300c5db95ae8a52c31a9d973b6dd9c2254', 'https://github.com/containous/traefik/commit/e63db782c11c7b8bfce30be4c902e7ef8f9f33d2'} |
GHSA | GHSA-rc75-cf5c-mxvh | Use of Cryptographically Weak Pseudo-Random Number Generator in org.pac4j:pac4j-saml | The SAML identifier generated within SAML2Utils.java was found to make use of the apache commons-lang3 RandomStringUtils class which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong. This issue only affects the 3.X release of pac4j-saml. | {'CVE-2019-10755'} | 2021-08-18T22:08:18Z | 2019-11-06T17:06:28Z | MODERATE | 4.9 | {'CWE-338'} | {'https://github.com/advisories/GHSA-rc75-cf5c-mxvh', 'https://github.com/pac4j/pac4j/commit/34d5b1028a2db201ee81ec51b52a782fe073f609', 'https://snyk.io/vuln/SNYK-JAVA-ORGPAC4J-467407', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10755'} | null | {'https://github.com/pac4j/pac4j/commit/34d5b1028a2db201ee81ec51b52a782fe073f609'} | {'https://github.com/pac4j/pac4j/commit/34d5b1028a2db201ee81ec51b52a782fe073f609'} |
GHSA | GHSA-h73q-5wmj-q8pj | Cross site scripting in datatables.net | This affects the package datatables.net before 1.11.3. If an array is passed to the HTML escape entities function it would not have its contents escaped. | {'CVE-2021-23445'} | 2021-10-13T17:26:02Z | 2021-09-29T17:11:28Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/DataTables/Dist-DataTables/commit/59a8d3f8a3c1138ab08704e783bc52bfe88d7c9b', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1715376', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23445', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1715371', 'https://cdn.datatables.net/1.11.3/', 'https://github.com/advisories/GHSA-h73q-5wmj-q8pj', 'https://snyk.io/vuln/SNYK-JS-DATATABLESNET-1540544'} | null | {'https://github.com/DataTables/Dist-DataTables/commit/59a8d3f8a3c1138ab08704e783bc52bfe88d7c9b'} | {'https://github.com/DataTables/Dist-DataTables/commit/59a8d3f8a3c1138ab08704e783bc52bfe88d7c9b'} |
GHSA | GHSA-c5x2-p679-95wc | Null pointer dereference in `SparseTensorSliceDataset` | ### Impact
When a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer:
```python
import tensorflow as tf
tf.raw_ops.SparseTensorSliceDataset(
indices=[[],[],[]],
values=[1,2,3],
dense_shape=[3,3])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not.
If `indices` is empty (as in the example above), then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference:
```cc
for (int64_t i = 0; i < indices->dim_size(0); ++i) {
int64_t next_batch_index = indices->matrix<int64>()(i, 0);
...
}
```
If `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector).
### Patches
We have patched the issue in GitHub commit [02cc160e29d20631de3859c6653184e3f876b9d7](https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7).
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-37647'} | 2021-08-25T14:43:32Z | 2021-08-25T14:43:32Z | HIGH | 7.7 | {'CWE-476'} | {'https://github.com/advisories/GHSA-c5x2-p679-95wc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37647', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c5x2-p679-95wc', 'https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7'} | null | {'https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7'} | {'https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7'} |
GHSA | GHSA-cpgw-2wxr-pww3 | Open Redirect | Open redirect vulnerability in Gogs before 0.12 allows remote attackers to redirect users to arbitrary websites and conduct phishing attacks via an initial /\ substring in the user/login redirect_to parameter, related to the function isValidRedirect in routes/user/auth.go. | {'CVE-2018-15178'} | 2021-06-29T18:32:39Z | 2021-06-29T18:32:39Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/gogs/gogs/pull/5365', 'https://github.com/gogs/gogs/issues/5364', 'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2', 'https://github.com/advisories/GHSA-cpgw-2wxr-pww3', 'https://nvd.nist.gov/vuln/detail/CVE-2018-15178'} | null | {'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2'} | {'https://github.com/gogs/gogs/commit/1f247cf8139cb483276cd8dd06385a800ce9d4b2'} |
GHSA | GHSA-qqxp-xp9v-vvx6 | Moderate severity vulnerability that affects jquery-ui | Cross-site scripting (XSS) vulnerability in the default content option in jquery.ui.tooltip.js in the Tooltip widget in jQuery UI before 1.10.0 allows remote attackers to inject arbitrary web script or HTML via the title attribute, which is not properly handled in the autocomplete combo box demo. | {'CVE-2012-6662'} | 2021-09-16T20:04:39Z | 2017-10-24T18:33:37Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-qqxp-xp9v-vvx6', 'https://github.com/jquery/jquery-ui/commit/5fee6fd5000072ff32f2d65b6451f39af9e0e39e', 'http://bugs.jqueryui.com/ticket/8859', 'http://www.securityfocus.com/bid/71107', 'http://seclists.org/oss-sec/2014/q4/613', 'http://seclists.org/oss-sec/2014/q4/616', 'https://github.com/jquery/jquery-ui/commit/f2854408cce7e4b7fc6bf8676761904af9c96bde', 'https://nvd.nist.gov/vuln/detail/CVE-2012-6662', 'http://rhn.redhat.com/errata/RHSA-2015-1462.html', 'https://github.com/jquery/jquery/issues/2432', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98697', 'http://bugs.jqueryui.com/ticket/8861', 'http://rhn.redhat.com/errata/RHSA-2015-0442.html'} | null | {'https://github.com/jquery/jquery-ui/commit/f2854408cce7e4b7fc6bf8676761904af9c96bde', 'https://github.com/jquery/jquery-ui/commit/5fee6fd5000072ff32f2d65b6451f39af9e0e39e'} | {'https://github.com/jquery/jquery-ui/commit/f2854408cce7e4b7fc6bf8676761904af9c96bde', 'https://github.com/jquery/jquery-ui/commit/5fee6fd5000072ff32f2d65b6451f39af9e0e39e'} |
GHSA | GHSA-jm6p-wfjg-xm7x | bookstack is vulnerable to Improper Access Control | bookstack is vulnerable to Improper Access Control. | {'CVE-2021-4026'} | 2021-12-02T15:29:38Z | 2021-12-01T18:26:48Z | MODERATE | 4.3 | {'CWE-668', 'CWE-284'} | {'https://github.com/advisories/GHSA-jm6p-wfjg-xm7x', 'https://github.com/BookStackApp/BookStack/releases/tag/v21.11.2', 'https://github.com/bookstackapp/bookstack/commit/b4fa82e3298a15443ca40bff205b7a16a1031d92', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4026', 'https://huntr.dev/bounties/c6dfa80d-43e6-4b49-95af-cc031bb66b1d'} | null | {'https://github.com/bookstackapp/bookstack/commit/b4fa82e3298a15443ca40bff205b7a16a1031d92'} | {'https://github.com/bookstackapp/bookstack/commit/b4fa82e3298a15443ca40bff205b7a16a1031d92'} |
GHSA | GHSA-p2j5-3f4c-224r | Improper Input Validation in HashiCorp Consul | HashiCorp Consul and Consul Enterprise did not appropriately enforce scope for local tokens issued by a primary data center, where replication to a secondary data center was not enabled. Introduced in 1.4.0, fixed in 1.6.6 and 1.7.4. | {'CVE-2020-13170'} | 2021-05-18T18:21:21Z | 2021-05-18T18:21:21Z | MODERATE | 5.3 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-13170', 'https://github.com/hashicorp/consul/blob/v1.7.4/CHANGELOG.md', 'https://github.com/hashicorp/consul/pull/8068', 'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216', 'https://github.com/advisories/GHSA-p2j5-3f4c-224r', 'https://github.com/hashicorp/consul/blob/v1.6.6/CHANGELOG.md'} | null | {'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216'} | {'https://github.com/hashicorp/consul/commit/242994a016a181d6c62a5bb83189716ad13d4216'} |
GHSA | GHSA-5cmw-fhq9-8fhh | Type Confusion in LiveHelperChat | Live Helper Chat provides live support for your website. Loose comparison causes IDOR on multiple endpoints in LiveHelperChat prior to 3.96. There is a fix released in versions 3.96 and 3.97. Currently, there is no known workaround. | {'CVE-2022-1176'} | 2022-04-12T18:10:01Z | 2022-04-01T00:00:40Z | HIGH | 7.5 | {'CWE-843'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-1176', 'https://github.com/advisories/GHSA-5cmw-fhq9-8fhh', 'https://github.com/livehelperchat/livehelperchat/commit/72c0df160bfe9838c618652facef29af99392ce3', 'https://huntr.dev/bounties/3e30171b-c9bf-415c-82f1-6f55a44d09d3'} | null | {'https://github.com/livehelperchat/livehelperchat/commit/72c0df160bfe9838c618652facef29af99392ce3'} | {'https://github.com/livehelperchat/livehelperchat/commit/72c0df160bfe9838c618652facef29af99392ce3'} |
GHSA | GHSA-q448-6c3m-cxmj | Cross-site Scripting in jeecg-boot | jeecg-boot is a code generator. A Cross Site Scripting (XSS) vulnerabilitiy exists in jeecg-boot 3.0 in /jeecg-boot/jmreport/view with a mouseover event. | {'CVE-2021-44585'} | 2022-03-28T14:30:55Z | 2022-03-11T00:01:59Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/jeecgboot/jeecg-boot/issues/3223', 'https://github.com/jeecgboot/jeecg-boot/commit/dbba190980fe44ab5377703dc1a9487806ee2a91', 'https://github.com/advisories/GHSA-q448-6c3m-cxmj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44585'} | null | {'https://github.com/jeecgboot/jeecg-boot/commit/dbba190980fe44ab5377703dc1a9487806ee2a91'} | {'https://github.com/jeecgboot/jeecg-boot/commit/dbba190980fe44ab5377703dc1a9487806ee2a91'} |
GHSA | GHSA-j6jg-w79c-7p8v | File Upload Restriction Bypass leading to Cross-site Scripting in ShowDoc | ShowDoc prior to 2.10.4 is vulnerable to a file upload restriction bypass leading to stored cross-site scripting. | {'CVE-2022-0951'} | 2022-03-29T21:23:38Z | 2022-03-16T00:00:48Z | MODERATE | 6.1 | {'CWE-434', 'CWE-79'} | {'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0951', 'https://github.com/advisories/GHSA-j6jg-w79c-7p8v', 'https://huntr.dev/bounties/b3a983a3-17f9-4aa8-92d7-8a0c92a93932'} | null | {'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3'} | {'https://github.com/star7th/showdoc/commit/237ac6d43bf3728bf3587c486a23b4a48ea7acb3'} |
GHSA | GHSA-8xx9-rxrj-2m2w | Cross-site Scripting in pimcore | pimcore is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-4139'} | 2022-01-05T20:35:12Z | 2022-01-05T20:35:12Z | MODERATE | 6.6 | {'CWE-79'} | {'https://github.com/pimcore/pimcore/commit/d5c3e876d910784000335061c3bd24d301351245', 'https://huntr.dev/bounties/6ec59e43-095f-4ba3-8b75-e92250da8e3a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4139', 'https://github.com/advisories/GHSA-8xx9-rxrj-2m2w'} | null | {'https://github.com/pimcore/pimcore/commit/d5c3e876d910784000335061c3bd24d301351245'} | {'https://github.com/pimcore/pimcore/commit/d5c3e876d910784000335061c3bd24d301351245'} |
GHSA | GHSA-94vp-rmqv-5875 | Twig Sandbox Escape by authenticated users with access to editing CMS templates when safemode is enabled. | ### Impact
An authenticated backend user with the `cms.manage_pages`, `cms.manage_layouts`, or `cms.manage_partials` permissions who would **normally** not be permitted to provide PHP code to be executed by the CMS due to `cms.enableSafeMode` being enabled is able to write specific Twig code to escape the Twig sandbox and execute arbitrary PHP.
This is not a problem for anyone that trusts their users with those permissions to normally write & manage PHP within the CMS by not having `cms.enableSafeMode` enabled, but would be a problem for anyone relying on `cms.enableSafeMode` to ensure that users with those permissions in production do not have access to write & execute arbitrary PHP.
### Patches
Issue has been patched in Build 469 (v1.0.469) and v1.1.0.
### Workarounds
Apply https://github.com/octobercms/october/compare/106daa2930de4cebb18732732d47d4056f01dd5b...7cb148c1677373ac30ccfd3069d18098e403e1ca to your installation manually if unable to upgrade to Build 469.
### References
Reported by [ka1n4t](https://github.com/ka1n4t)
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="1108" alt="Screen Shot 2020-10-10 at 1 21 13 PM" src="https://user-images.githubusercontent.com/7253840/95663316-7de28b80-0afb-11eb-999d-a6526cf78709.png"> | {'CVE-2020-15247'} | 2022-04-19T19:02:37Z | 2020-11-23T19:48:27Z | MODERATE | 5.2 | {'CWE-862'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15247', 'https://github.com/octobercms/october/security/advisories/GHSA-94vp-rmqv-5875', 'https://github.com/advisories/GHSA-94vp-rmqv-5875', 'https://github.com/octobercms/october/commit/4c650bb775ab849e48202a4923bac93bd74f9982'} | null | {'https://github.com/octobercms/october/commit/4c650bb775ab849e48202a4923bac93bd74f9982'} | {'https://github.com/octobercms/october/commit/4c650bb775ab849e48202a4923bac93bd74f9982'} |
GHSA | GHSA-p867-fxfr-ph2w | b2-sdk-python TOCTOU application key disclosure | ### Impact
Linux and Mac releases of the SDK version 1.14.0 and below contain a key disclosure vulnerability that, in certain conditions, can be exploited by local attackers through a time-of-check-time-of-use (TOCTOU) race condition.
SDK users of the `SqliteAccountInfo` format are vulnerable while users of the `InMemoryAccountInfo` format are safe. The `SqliteAccountInfo` saves API keys (and bucket name-to-id mapping) in a local database file (`$XDG_CONFIG_HOME/b2/account_info`, `~/.b2_account_info` or a user-defined path). When first created, the file is world readable and is (typically a few milliseconds) later altered to be private to the user. If the directory containing the file is readable by a local attacker then during the brief period between file creation and permission modification, a local attacker can race to open the file and maintain a handle to it. This allows the local attacker to read the contents after the file after the sensitive information has been saved to it.
Consumers of this SDK who rely on it to save data using `SqliteAccountInfo` class should upgrade to the latest version of the SDK. Those who believe a local user might have opened a handle using this race condition, should remove the affected database files and regenerate all application keys.
### Patches
Users should upgrade to b2-sdk-python 1.14.1 or later.
### For more information
See the related advisory in the [B2 Command Line Tool](https://github.com/Backblaze/B2_Command_Line_Tool), a consumer of this SDK.
If you have any questions or comments about this advisory:
* Open an issue in [b2-sdk-python](https://github.com/Backblaze/b2-sdk-python)
* Email us at [security@backblaze.com](mailto:security@backblaze.com)
| {'CVE-2022-23651'} | 2022-04-19T19:03:23Z | 2022-02-24T12:08:24Z | MODERATE | 4.7 | {'CWE-367'} | {'https://pypi.org/project/b2sdk/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23651', 'https://github.com/Backblaze/b2-sdk-python/commit/62476638986e5b6d7459aca5ef8ce220760226e0', 'https://github.com/Backblaze/b2-sdk-python/security/advisories/GHSA-p867-fxfr-ph2w', 'https://github.com/advisories/GHSA-p867-fxfr-ph2w'} | null | {'https://github.com/Backblaze/b2-sdk-python/commit/62476638986e5b6d7459aca5ef8ce220760226e0'} | {'https://github.com/Backblaze/b2-sdk-python/commit/62476638986e5b6d7459aca5ef8ce220760226e0'} |
GHSA | GHSA-xm34-v85h-9pg2 | Authentication Bypass by CSRF Weakness | ### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `solidus_auth_devise` are affected if `protect_from_forgery` method is both:
- Executed whether as:
- A `before_action` callback (the default)
- A `prepend_before_action` (option `prepend: true` given) before the `:load_object` hook in `Spree::UserController` (most likely order to find).
- Configured to use `:null_session` or `:reset_session` strategies (`:null_session` is the default in case the no strategy is given, but `rails --new` generated skeleton use `:exception`).
That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
### Patches
Users should promptly update to `solidus_auth_devise` version `2.5.4`.
### Workarounds
A couple of options:
- If possible, change your strategy to `:exception`:
```ruby
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
```
- Add the following to `config/application.rb` to at least run the `:exception` strategy on the affected controller:
```ruby
config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
```
- We've also released new Solidus versions monkey patching `solidus_auth_devise` with the quick fix. Those versions are `v3.1.3`, `v.3.0.3` & `v2.11.12`. See [GHSA-5629-8855-gf4g](https://github.com/solidusio/solidus/security/advisories/GHSA-5629-8855-gf4g) for details.
### References
- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)
- [Solidus security](https://solidus.io/security/)
### Thanks
We'd like to thank [vampire000](https://hackerone.com/vampire000) for reporting this issue.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
| {'CVE-2021-41274'} | 2021-11-18T20:09:32Z | 2021-11-18T20:09:32Z | CRITICAL | 9.3 | {'CWE-352'} | {'https://github.com/solidusio/solidus_auth_devise/releases/tag/v2.5.4', 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2', 'https://github.com/advisories/GHSA-xm34-v85h-9pg2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41274', 'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'} | null | {'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'} | {'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'} |
GHSA | GHSA-q4rf-3fhx-88pf | YAML deserialization can run untrusted code | ### Impact
An authorized user can upload a zip-format plugin with a crafted plugin.yaml, or a crafted aclpolicy yaml file, or upload an untrusted project archive with a crafted aclpolicy yaml file, that can cause the server to run untrusted code on Rundeck Community or Enterprise Edition. An authenticated user can make a POST request, that can cause the server to run untrusted code on Rundeck Enterprise Edition.
The zip-format plugin issues requires authentication and authorization to these access levels, and affects all Rundeck editions:
* `admin` level access to the `system` resource type
The ACL Policy yaml file upload issues requires authentication and authorization to these access levels, and affects all Rundeck editions:
* `create` `update` or `admin` level access to a `project_acl` resource
* `create` `update` or `admin` level access to the `system_acl` resource
The unauthorized POST request requires authentication, but no specific authorization, and affects Rundeck Enterprise only.
### Patches
Versions 3.4.3, 3.3.14
### Workarounds
Please visit [https://rundeck.com/security](https://rundeck.com/security) for information about specific workarounds.
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@rundeck.com](mailto:security@rundeck.com)
To report security issues to Rundeck please use the form at [https://rundeck.com/security](https://rundeck.com/security)
Reporter: Rojan Rijal from Tinder Red Team | {'CVE-2021-39132'} | 2021-09-01T18:27:01Z | 2021-09-01T18:27:01Z | MODERATE | 8.8 | {'CWE-502'} | {'https://github.com/rundeck/rundeck/security/advisories/GHSA-q4rf-3fhx-88pf', 'https://github.com/rundeck/rundeck/commit/850d12e21d22833bc148b7f458d7cb5949f829b6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39132', 'https://github.com/advisories/GHSA-q4rf-3fhx-88pf'} | null | {'https://github.com/rundeck/rundeck/commit/850d12e21d22833bc148b7f458d7cb5949f829b6'} | {'https://github.com/rundeck/rundeck/commit/850d12e21d22833bc148b7f458d7cb5949f829b6'} |
GHSA | GHSA-m6cj-93v6-cvr5 | Infinite loop in junrar | ### Impact
A carefully crafted RAR archive can trigger an infinite loop while extracting said archive. The impact depends solely on how the application uses the library, and whether files can be provided by malignant users.
### Patches
The problem is partially patched in 7.4.1
### Workarounds
None
### References
https://github.com/junrar/junrar/issues/73
https://github.com/junrar/junrar/issues/81
| {'CVE-2022-23596'} | 2022-04-19T17:55:14Z | 2022-02-01T00:47:23Z | HIGH | 7.5 | {'CWE-835', 'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23596', 'https://github.com/junrar/junrar/commit/7b16b3d90b91445fd6af0adfed22c07413d4fab7', 'https://github.com/junrar/junrar/issues/73', 'https://github.com/advisories/GHSA-m6cj-93v6-cvr5', 'https://github.com/junrar/junrar/security/advisories/GHSA-m6cj-93v6-cvr5'} | null | {'https://github.com/junrar/junrar/commit/7b16b3d90b91445fd6af0adfed22c07413d4fab7'} | {'https://github.com/junrar/junrar/commit/7b16b3d90b91445fd6af0adfed22c07413d4fab7'} |
GHSA | GHSA-67j9-c52g-w2q9 | Authorization Bypass in I hate money | ### Impact
An authenticated member of one project can modify and delete members of another project, without knowledge of this other project's private code. This can be further exploited to access all bills of another project without knowledge of this other project's private code.
With the default configuration, anybody is allowed to create a new project. An attacker can create a new project and then use it to become authenticated and exploit this flaw. As such, the exposure is similar to an unauthenticated attack, because it is trivial to become authenticated.
### Patches
```diff
ihatemoney/models.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ihatemoney/models.py b/ihatemoney/models.py
index fe7b519..5691c75 100644
--- a/ihatemoney/models.py
+++ b/ihatemoney/models.py
@@ -380,7 +380,7 @@ class Person(db.Model):
def get_by_name(self, name, project):
return (
Person.query.filter(Person.name == name)
- .filter(Project.id == project.id)
+ .filter(Person.project_id == project.id)
.one()
)
@@ -389,7 +389,7 @@ class Person(db.Model):
project = g.project
return (
Person.query.filter(Person.id == id)
- .filter(Project.id == project.id)
+ .filter(Person.project_id == project.id)
.one()
)
```
### Workarounds
To limit the impact, it is possible to disable public project creation by setting `ALLOW_PUBLIC_PROJECT_CREATION = False` in the configuration (see [documentation](https://ihatemoney.readthedocs.io/en/latest/configuration.html)). Existing users will still be able to exploit the flaw, but this will prevent an external attacker from creating a new project.
### For more information
`Person.query.get()` and `Person.query.get_by_name()` were mistakenly running a database join on the Project table without constraining the result.
As a result, `Person.query.get(42, "projectfoo")` would return the Person with id=42, even if it is not associated to the project "projectfoo". The only condition is that "projectfoo" must exist.
This flaw can be exploited in several places:
1) API: PUT requests to `/api/projects/<project>/members/<personID>` will succeed even though `<personID>` is not a member of `<project>`.
This allows an authenticated attacker to alter the state of a member (name, weight, activated) in any project. In addition, the altered member will no longer be associated with its original project but will be associated to the attacker project instead, breaking many features of IHateMoney. For instance, bills referencing the altered member will no longer be visible in the original project.
This causes an additional information disclosure and loss of integrity on bills: the attacker will now be able to see, edit and delete bills belonging to the altered member, because IHateMoney now believes that these bills are associated to the attacker project through the altered member.
For instance, assume that `Person(id=42)` is a member of project "targetProject", and that the attacker has access to another project "attackerProject" with the private code "attackerPassword". The attacker can modify `Person(id=42)` with this command:
$ curl -X PUT -d "name=Pwn3d&activated=1" --basic -u attackerProject:attackerPassword http://$SERVER/api/projects/attackerProject/members/42
The attacker can now see, edit and delete bills paid by `Person(id=42)` by simply browsing to http://$SERVER/attackerProject/
2) Editing a member through the web interface at `/<project>/members/<personID>/edit` will succeed even though `<personID>` is not a member of `<project>`.
This is very similar to the PUT exploit. Reusing the same example, the attacker needs to login to its "attackerProject" project with the private code "attackerPassword". It can then alter the state of `Person(id=42)` by accessing the edit form at the following URL:
http://$SERVER/attackerProject/members/42/edit
Again, as a result of the alteration, the altered member will become associated to the project "attackerProject", resulting in the same information disclosure and loss of integrity on bills.
3) API: DELETE requests to `/api/projects/<project>/members/<personID>` will similarly allow to delete the member `<personID>` even if it belongs to a different project than `<project>`.
$ curl -X DELETE --basic -u attackerProject:attackerPassword http://$SERVER/api/projects/attackerProject/members/42
The impact is less serious than with PUT, because DELETE only deactivates a member (it does not really delete it).
All these exploits require authentication: an attacker needs to know a valid project name and its associated "private code". Once this requirement is fullfilled, the attacker can exploit this flaw to alter the state of members in any other project, without needing to know the target project name or its private code.
`Person.query.get_by_name()` suffers from the same issue as `Person.query.get()`. It has an additional issue: if multiple Person objects with the same name exist (this is possible if they are associated to different projects), `get_by_name()` will crash with `MultipleResultsFound` because of the call to `one()`.
However, since `Person.query.get_by_name()` is currently not used anywhere in IHateMoney, the bug affecting this function has no impact and is not exploitable. | {'CVE-2020-15120'} | 2022-04-19T19:02:31Z | 2020-07-27T17:47:52Z | MODERATE | 4.9 | {'CWE-863'} | {'https://github.com/spiral-project/ihatemoney/security/advisories/GHSA-67j9-c52g-w2q9', 'https://github.com/advisories/GHSA-67j9-c52g-w2q9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15120', 'https://github.com/spiral-project/ihatemoney/commit/8d77cf5d5646e1d2d8ded13f0660638f57e98471'} | null | {'https://github.com/spiral-project/ihatemoney/commit/8d77cf5d5646e1d2d8ded13f0660638f57e98471'} | {'https://github.com/spiral-project/ihatemoney/commit/8d77cf5d5646e1d2d8ded13f0660638f57e98471'} |
GHSA | GHSA-g452-6rfc-vrvx | Prototype Pollution in open-graph | This affects the package open-graph before 0.2.6. The function parse could be tricked into adding or modifying properties of Object.prototype using a __proto__ or constructor payload. | {'CVE-2021-23419'} | 2021-09-01T18:31:53Z | 2021-09-01T18:31:53Z | MODERATE | 5.3 | {'CWE-915'} | {'https://snyk.io/vuln/SNYK-JS-OPENGRAPH-1536747', 'https://github.com/samholmes/node-open-graph/commit/a0cef507a90adaac7dbbe9c404f09a50bdefb348', 'https://github.com/advisories/GHSA-g452-6rfc-vrvx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23419'} | null | {'https://github.com/samholmes/node-open-graph/commit/a0cef507a90adaac7dbbe9c404f09a50bdefb348'} | {'https://github.com/samholmes/node-open-graph/commit/a0cef507a90adaac7dbbe9c404f09a50bdefb348'} |
GHSA | GHSA-m2r5-4w96-qxg5 | Arbitrary file access through XML parsing in org.xwiki.commons:xwiki-commons-xml | ### Impact
It's possible in a script to access any file accessing to the user running XWiki application server with XML External Entity Injection through the XML script service.
For example:
```
{{velocity}}
#set($xml=$services.get('xml'))
#set($xxe_payload = "<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE root[<!ENTITY xxe SYSTEM 'file:///etc/passwd' >]><root><foo>&xxe;</foo></root>")
#set($doc=$xml.parse($xxe_payload))
$xml.serialize($doc)
{{/velocity}}
```
### Patches
The problem has been patched on versions 12.10.10, 13.4.4 and 13.8RC1.
### Workarounds
There's no easy workaround for fixing this vulnerability other than upgrading and being careful when giving Script rights.
### References
https://jira.xwiki.org/browse/XWIKI-18946
### 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 [XWiki Security mailing-list](mailto:security@xwiki.org) | {'CVE-2022-24898'} | 2022-04-28T19:31:55Z | 2022-04-28T19:31:55Z | MODERATE | 4.9 | {'CWE-611'} | {'https://github.com/xwiki/xwiki-commons/commit/947e8921ebd95462d5a7928f397dd1b64f77c7d5', 'https://github.com/xwiki/xwiki-commons/security/advisories/GHSA-m2r5-4w96-qxg5', 'https://jira.xwiki.org/browse/XWIKI-18946', 'https://github.com/advisories/GHSA-m2r5-4w96-qxg5'} | null | {'https://github.com/xwiki/xwiki-commons/commit/947e8921ebd95462d5a7928f397dd1b64f77c7d5'} | {'https://github.com/xwiki/xwiki-commons/commit/947e8921ebd95462d5a7928f397dd1b64f77c7d5'} |
GHSA | GHSA-6c8p-qphv-668v | Moderate severity vulnerability that affects ruby-openid | The ruby-openid gem before 2.2.2 for Ruby allows remote OpenID providers to cause a denial of service (CPU consumption) via (1) a large XRDS document or (2) an XML Entity Expansion (XEE) attack. | {'CVE-2013-1812'} | 2021-09-02T15:54:33Z | 2017-10-24T18:33:37Z | MODERATE | 0 | null | {'https://github.com/openid/ruby-openid/pull/43', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1812', 'https://github.com/advisories/GHSA-6c8p-qphv-668v', 'https://github.com/openid/ruby-openid/commit/a3693cef06049563f5b4e4824f4d3211288508ed', 'https://bugzilla.redhat.com/show_bug.cgi?id=918134', 'https://github.com/openid/ruby-openid/blob/master/CHANGELOG.md', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-November/120204.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-November/120361.html', 'http://www.openwall.com/lists/oss-security/2013/03/03/8'} | null | {'https://github.com/openid/ruby-openid/commit/a3693cef06049563f5b4e4824f4d3211288508ed'} | {'https://github.com/openid/ruby-openid/commit/a3693cef06049563f5b4e4824f4d3211288508ed'} |
GHSA | GHSA-hhqj-cfjx-vj25 | Cross site scripting in reveal.js | The onmessage event listener in /plugin/notes/speaker-view.html does not check the origin of postMessage before adding the content to the webpage. The vulnerable code allows any origin to postMessage on the browser window and feeds attacker's input to parts using which attacker can execute arbitrary javascript code on victim's browser window hosting reveal.js | {'CVE-2022-0776'} | 2022-03-10T16:00:14Z | 2022-03-02T00:00:20Z | MODERATE | 6.1 | {'CWE-79'} | {'https://huntr.dev/bounties/be2b7ee4-f487-42e1-874a-6bcc410e4001', 'https://github.com/advisories/GHSA-hhqj-cfjx-vj25', 'https://github.com/hakimel/reveal.js/commit/32cdd3b1872ba8e2267c9e87ae216cb55f40f4d2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0776'} | null | {'https://github.com/hakimel/reveal.js/commit/32cdd3b1872ba8e2267c9e87ae216cb55f40f4d2'} | {'https://github.com/hakimel/reveal.js/commit/32cdd3b1872ba8e2267c9e87ae216cb55f40f4d2'} |
GHSA | GHSA-c35v-qwqg-87jc | Timing Attack in express-basic-auth | Versions of `express-basic-auth` prior to 1.2.0 are vulnerable to Timing Attacks. The package uses nating string comparison instead of a constant time string compare which may lead to Timing Attacks. Timing Attacks can be used to increase the efficiency of brute-force attacks by removing the exponential increase in entropy gained from longer secrets.
## Recommendation
Upgrade to version 1.2.0 or later. | null | 2021-08-04T20:58:12Z | 2019-06-06T15:32:32Z | LOW | 3.1 | {'CWE-208'} | {'https://snyk.io/vuln/SNYK-JS-EXPRESSBASICAUTH-174345', 'https://www.npmjs.com/advisories/827', 'https://github.com/LionC/express-basic-auth/pull/21', 'https://github.com/advisories/GHSA-c35v-qwqg-87jc', 'https://github.com/webpack-contrib/webpack-bundle-analyzer/issues/263', 'https://github.com/LionC/express-basic-auth/pull/20', 'https://github.com/LionC/express-basic-auth/commit/00bb29fdd638f5cda8025d4398be97d528ce3f6f'} | null | {'https://github.com/LionC/express-basic-auth/commit/00bb29fdd638f5cda8025d4398be97d528ce3f6f'} | {'https://github.com/LionC/express-basic-auth/commit/00bb29fdd638f5cda8025d4398be97d528ce3f6f'} |
GHSA | GHSA-qjwc-v72v-fq6r | HTTP request smuggling in Undertow | A flaw was found in Undertow. A regression in the fix for CVE-2020-10687 was found. HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a web-cache, perform an XSS attack, or obtain sensitive information from request other than their own. The highest threat from this vulnerability is to data confidentiality and integrity. | {'CVE-2021-20220'} | 2022-02-11T21:11:27Z | 2021-06-16T17:47:52Z | MODERATE | 4.8 | {'CWE-444'} | {'https://bugzilla.redhat.com/show_bug.cgi?id=1923133', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20220', 'https://github.com/advisories/GHSA-qjwc-v72v-fq6r', 'https://security.netapp.com/advisory/ntap-20220210-0013/', 'https://github.com/undertow-io/undertow/commit/9e797b2f99617fdad0471eaa88c711ee7f44605f'} | null | {'https://github.com/undertow-io/undertow/commit/9e797b2f99617fdad0471eaa88c711ee7f44605f'} | {'https://github.com/undertow-io/undertow/commit/9e797b2f99617fdad0471eaa88c711ee7f44605f'} |
GHSA | GHSA-q879-9g95-56mx | Wrong type for `Linker`-define functions when used across two `Engine`s | ### Impact
As a Rust library the `wasmtime` crate clearly marks which functions are safe and which are `unsafe`, guaranteeing that if consumers never use `unsafe` then it should not be possible to have memory unsafety issues in their embeddings of Wasmtime. An issue was discovered in the safe API of `Linker::func_*` APIs. These APIs were previously not sound when one `Engine` was used to create the `Linker` and then a different `Engine` was used to create a `Store` and then the `Linker` was used to instantiate a module into that `Store`. Cross-`Engine` usage of functions is not supported in Wasmtime and this can result in type confusion of function pointers, resulting in being able to safely call a function with the wrong type.
Triggering this bug requires using at least two `Engine` values in an embedding and then additionally using two different values with a `Linker` (one at the creation time of the `Linker` and another when instantiating a module with the `Linker`).
It's expected that usage of more-than-one `Engine` in an embedding is relatively rare since an `Engine` is intended to be a globally shared resource, so the expectation is that the impact of this issue is relatively small.
The fix implemented is to change this behavior to `panic!()` in Rust instead of silently allowing it. Using different `Engine` instances with a `Linker` is a programmer bug that `wasmtime` catches at runtime.
### Patches
This bug has been patched and users should upgrade to Wasmtime version 0.30.0.
### Workarounds
If you cannot upgrade Wasmtime and are using more than one `Engine` in your embedding it's recommended to instead use only one `Engine` for the entire program if possible. An `Engine` is designed to be a globally shared resource that is suitable to have only one for the lifetime of an entire process. If using multiple `Engine`s is required then code should be audited to ensure that `Linker` is only used with one `Engine`.
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/) | {'CVE-2021-39219'} | 2022-04-19T19:03:08Z | 2021-09-20T19:54:26Z | MODERATE | 6.3 | {'CWE-843'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-39219', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-q879-9g95-56mx', 'https://github.com/bytecodealliance/wasmtime/commit/b39f087414f27ae40c44449ed5d1154e03449bff', 'https://crates.io/crates/wasmtime', 'https://github.com/advisories/GHSA-q879-9g95-56mx'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/b39f087414f27ae40c44449ed5d1154e03449bff'} | {'https://github.com/bytecodealliance/wasmtime/commit/b39f087414f27ae40c44449ed5d1154e03449bff'} |
GHSA | GHSA-9r5x-fjv3-q6h4 | Incorrect Access Control in github.com/nats-io/jwt and github.com/nats-io/nats-server/v2 | NATS Server 2.x before 2.2.0 and JWT library before 2.0.1 have Incorrect Access Control because Import Token bindings are mishandled. | {'CVE-2021-3127'} | 2022-04-12T22:11:19Z | 2022-02-15T01:57:18Z | HIGH | 7.5 | {'CWE-863', 'CWE-284'} | {'https://advisories.nats.io/CVE/CVE-2021-3127.txt', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3127', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866', 'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403', 'https://github.com/advisories/GHSA-9r5x-fjv3-q6h4'} | null | {'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866'} | {'https://github.com/nats-io/nats-server/commit/423b79440c80c863de9f4e20548504e6c5d5e403', 'https://github.com/nats-io/jwt/pull/149/commits/a826c77dc9d2671c961b75ceefdb439c41029866'} |
GHSA | GHSA-c65v-p733-9796 | Cross-site Scripting in snipe/snipe-it | snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-3961'} | 2021-11-23T18:17:33Z | 2021-11-23T18:17:33Z | HIGH | 8 | {'CWE-79'} | {'https://github.com/advisories/GHSA-c65v-p733-9796', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3961', 'https://github.com/snipe/snipe-it/commit/7ce5993f5ae9d713a0955c2fd8e2dff7a7ce886e', 'https://huntr.dev/bounties/5987aed5-6613-4937-8a3e-d48009b7da10'} | null | {'https://github.com/snipe/snipe-it/commit/7ce5993f5ae9d713a0955c2fd8e2dff7a7ce886e'} | {'https://github.com/snipe/snipe-it/commit/7ce5993f5ae9d713a0955c2fd8e2dff7a7ce886e'} |
GHSA | GHSA-5fq8-3q2f-4m5g | Session key exposure through session list in Django User Sessions | ### Impact
The views provided by django-user-sessions allow users to terminate specific sessions. The session key is used to identify sessions, and thus included in the rendered HTML. In itself this is not a problem. However if the website has an XSS vulnerability, the session key could be extracted by the attacker and a session takeover could happen.
### Patches
Patch is under way.
### Workarounds
Remove the session_key from the template.
### References
_None._
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Bouke/django-user-sessions](https://github.com/Bouke/django-user-sessions/issues)
* Email us at [bouke@haarsma.eu](mailto:bouke@haarsma.eu) | {'CVE-2020-5224'} | 2021-01-08T20:33:15Z | 2020-01-24T19:56:59Z | LOW | 6.5 | {'CWE-287'} | {'https://github.com/Bouke/django-user-sessions/security/advisories/GHSA-5fq8-3q2f-4m5g', 'https://github.com/advisories/GHSA-5fq8-3q2f-4m5g', 'https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5224'} | null | {'https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9'} | {'https://github.com/jazzband/django-user-sessions/commit/f0c4077e7d1436ba6d721af85cee89222ca5d2d9'} |
GHSA | GHSA-6c3f-p5wp-34mh | OS Command Injection in async-git | The async-git package before 1.13.2 for Node.js allows OS Command Injection via shell metacharacters, as demonstrated by git.reset and git.tag. This issue may lead to remote code execution if a client of the library calls the vulnerable method with untrusted input. Ensure to sanitize untrusted user input before passing it to one of the vulnerable functions as a workaround or update async-git to version 1.13.1. | {'CVE-2021-3190'} | 2022-05-03T02:56:05Z | 2021-01-29T18:14:00Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://github.com/omrilotan/async-git/pull/13/commits/611823bd97dd41e9e8127c38066868ff9dcfa57a', 'https://github.com/omrilotan/async-git/pull/13', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3190', 'https://advisory.checkmarx.net/advisory/CX-2021-4772', 'https://github.com/advisories/GHSA-6c3f-p5wp-34mh', 'https://github.com/omrilotan/async-git/pull/14', 'https://github.com/omrilotan/async-git/pull/13/commits/a5f45f58941006c4cc1699609383b533d9b92c6a', 'https://www.npmjs.com/package/async-git'} | null | {'https://github.com/omrilotan/async-git/pull/13/commits/611823bd97dd41e9e8127c38066868ff9dcfa57a', 'https://github.com/omrilotan/async-git/pull/13/commits/a5f45f58941006c4cc1699609383b533d9b92c6a'} | {'https://github.com/omrilotan/async-git/pull/13/commits/611823bd97dd41e9e8127c38066868ff9dcfa57a', 'https://github.com/omrilotan/async-git/pull/13/commits/a5f45f58941006c4cc1699609383b533d9b92c6a'} |
GHSA | GHSA-8cr8-4vfw-mr7h | Round-trip instability in REXML | The REXML gem before 3.2.5 in Ruby before 2.6.7, 2.7.x before 2.7.3, and 3.x before 3.0.1 does not properly address XML round-trip issues. An incorrect document can be produced after parsing and serializing. | {'CVE-2021-28965'} | 2021-06-01T17:23:48Z | 2021-04-30T17:30:37Z | HIGH | 0 | {'CWE-611', 'CWE-115'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-28965', 'https://github.com/advisories/GHSA-8cr8-4vfw-mr7h', 'https://security.netapp.com/advisory/ntap-20210528-0003/', 'https://www.ruby-lang.org/en/news/2021/04/05/xml-round-trip-vulnerability-in-rexml-cve-2021-28965/', 'https://github.com/ruby/rexml/commit/f9d88e4948b4a43294c25dc0edb16815bd9d8618', 'https://github.com/ruby/rexml/commit/2fe62e29094d95921d7e19abbd2e26b23d78dc5b', 'https://github.com/ruby/rexml/commit/3c137eb119550874b2b3e27d12b733ca67033377', 'https://github.com/ruby/rexml/commit/a659c63e37414506dfb0d4655e031bb7a2e73fc8', 'https://hackerone.com/reports/1104077', 'https://rubygems.org/gems/rexml', 'https://github.com/ruby/rexml/commit/f7bab8937513b1403cea5aff874cbf32fd5e8551', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTVFTLFVCSUE5CXHINJEUCKSHU4SWDMT/', 'https://github.com/ruby/rexml/commit/9b311e59ae05749e082eb6bbefa1cb620d1a786e', 'https://github.com/ruby/rexml/commit/6a250d2cd1194c2be72becbdd9c3e770aa16e752'} | null | {'https://github.com/ruby/rexml/commit/f9d88e4948b4a43294c25dc0edb16815bd9d8618', 'https://github.com/ruby/rexml/commit/3c137eb119550874b2b3e27d12b733ca67033377', 'https://github.com/ruby/rexml/commit/2fe62e29094d95921d7e19abbd2e26b23d78dc5b', 'https://github.com/ruby/rexml/commit/6a250d2cd1194c2be72becbdd9c3e770aa16e752', 'https://github.com/ruby/rexml/commit/f7bab8937513b1403cea5aff874cbf32fd5e8551', 'https://github.com/ruby/rexml/commit/a659c63e37414506dfb0d4655e031bb7a2e73fc8', 'https://github.com/ruby/rexml/commit/9b311e59ae05749e082eb6bbefa1cb620d1a786e'} | {'https://github.com/ruby/rexml/commit/6a250d2cd1194c2be72becbdd9c3e770aa16e752', 'https://github.com/ruby/rexml/commit/2fe62e29094d95921d7e19abbd2e26b23d78dc5b', 'https://github.com/ruby/rexml/commit/f9d88e4948b4a43294c25dc0edb16815bd9d8618', 'https://github.com/ruby/rexml/commit/a659c63e37414506dfb0d4655e031bb7a2e73fc8', 'https://github.com/ruby/rexml/commit/9b311e59ae05749e082eb6bbefa1cb620d1a786e', 'https://github.com/ruby/rexml/commit/3c137eb119550874b2b3e27d12b733ca67033377', 'https://github.com/ruby/rexml/commit/f7bab8937513b1403cea5aff874cbf32fd5e8551'} |
GHSA | GHSA-jjr8-m8g8-p6wv | Null pointer dereference in TFLite's `Reshape` operator | ### Impact
The fix for [CVE-2020-15209](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15209) missed the case when the target shape of `Reshape` operator is given by the elements of a 1-D tensor. As such, the [fix for the vulnerability](https://github.com/tensorflow/tensorflow/blob/9c1dc920d8ffb4893d6c9d27d1f039607b326743/tensorflow/lite/core/subgraph.cc#L1062-L1074) allowed passing a null-buffer-backed tensor with a 1D shape:
```cc
if (tensor->data.raw == nullptr && tensor->bytes > 0) {
if (registration.builtin_code == kTfLiteBuiltinReshape && i == 1) {
// In general, having a tensor here with no buffer will be an error.
// However, for the reshape operator, the second input tensor is only
// used for the shape, not for the data. Thus, null buffer is ok.
continue;
} else {
// In all other cases, we need to return an error as otherwise we will
// trigger a null pointer dereference (likely).
ReportError("Input tensor %d lacks data", tensor_index);
return kTfLiteError;
}
}
```
### Patches
We have patched the issue in GitHub commit [f8378920345f4f4604202d4ab15ef64b2aceaa16](https://github.com/tensorflow/tensorflow/commit/f8378920345f4f4604202d4ab15ef64b2aceaa16).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29592'} | 2021-05-21T14:26:58Z | 2021-05-21T14:26:58Z | MODERATE | 4.4 | {'CWE-476'} | {'https://github.com/advisories/GHSA-jjr8-m8g8-p6wv', 'https://github.com/tensorflow/tensorflow/commit/f8378920345f4f4604202d4ab15ef64b2aceaa16', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jjr8-m8g8-p6wv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29592'} | null | {'https://github.com/tensorflow/tensorflow/commit/f8378920345f4f4604202d4ab15ef64b2aceaa16'} | {'https://github.com/tensorflow/tensorflow/commit/f8378920345f4f4604202d4ab15ef64b2aceaa16'} |
GHSA | GHSA-f78g-q7r4-9wcv | Division by 0 in `FractionalAvgPool` | ### Impact
An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.FractionalAvgPool`:
```python
import tensorflow as tf
value = tf.constant([60], shape=[1, 1, 1, 1], dtype=tf.int32)
pooling_ratio = [1.0, 1.0000014345305555, 1.0, 1.0]
pseudo_random = False
overlapping = False
deterministic = False
seed = 0
seed2 = 0
tf.raw_ops.FractionalAvgPool(
value=value, pooling_ratio=pooling_ratio, pseudo_random=pseudo_random,
overlapping=overlapping, deterministic=deterministic, seed=seed, seed2=seed2)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L85-L89) computes a divisor quantity by dividing two user controlled values:
```cc
for (int i = 0; i < tensor_in_and_out_dims; ++i) {
output_size[i] = static_cast<int>(std::floor(input_size[i] / pooling_ratio_[i]));
DCHECK_GT(output_size[i], 0);
}
```
The user controls the values of `input_size[i]` and `pooling_ratio_[i]` (via the `value.shape()` and `pooling_ratio` arguments). If the value in `input_size[i]` is smaller than the `pooling_ratio_[i]`, then the floor operation results in `output_size[i]` being 0. The `DCHECK_GT` line is a no-op outside of debug mode, so in released versions of TF this does not trigger.
Later, these computed values [are used as arguments](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_avg_pool_op.cc#L96-L99) to [`GeneratePoolingSequence`](https://github.com/tensorflow/tensorflow/blob/acc8ee69f5f46f92a3f1f11230f49c6ac266f10c/tensorflow/core/kernels/fractional_pool_common.cc#L100-L108). There, the first computation is a division in a modulo operation:
```cc
std::vector<int64> GeneratePoolingSequence(int input_length, int output_length,
GuardedPhiloxRandom* generator,
bool pseudo_random) {
...
if (input_length % output_length == 0) {
diff = std::vector<int64>(output_length, input_length / output_length);
}
...
}
```
Since `output_length` can be 0, this results in runtime crashing.
### Patches
We have patched the issue in GitHub commit [548b5eaf23685d86f722233d8fbc21d0a4aecb96](https://github.com/tensorflow/tensorflow/commit/548b5eaf23685d86f722233d8fbc21d0a4aecb96).
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-29550'} | 2021-05-21T14:23:41Z | 2021-05-21T14:23:41Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-f78g-q7r4-9wcv', 'https://github.com/tensorflow/tensorflow/commit/548b5eaf23685d86f722233d8fbc21d0a4aecb96', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f78g-q7r4-9wcv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29550'} | null | {'https://github.com/tensorflow/tensorflow/commit/548b5eaf23685d86f722233d8fbc21d0a4aecb96'} | {'https://github.com/tensorflow/tensorflow/commit/548b5eaf23685d86f722233d8fbc21d0a4aecb96'} |
GHSA | GHSA-rpxh-vg2x-526v | List of order ids, number, items total and token value exposed for unauthorized uses via new API | ### Impact
Part of the details (order ID, order number, items total, and token value) of all placed orders were exposed to unauthorized users. If exploited properly, a few additional information like the number of items in the cart and the date of the shipping may be fetched as well. This data seems to not be crucial nor is personal data, however, could be used for sociotechnical attacks or may expose a few details about shop condition to the third parties. The data possible to aggregate are the number of processed orders or their value in the moment of time.
### Patches
The problem has been patched at Sylius 1.9.5 and 1.10.0
### Workarounds
There are a few ways to fix this without updating the code.
The first possible solution is to hide the problematic endpoints behind the firewall from not logged in users. In order to achieve it one has to add the configuration in `config/packages/security.yaml`:
```yaml
access_control:
# ...
- { path: "%sylius.security.new_api_shop_regex%/orders", role: IS_AUTHENTICATED_ANONYMOUSLY, methods: [POST] }
- { path: "%sylius.security.new_api_shop_regex%/orders", role: ROLE_USER, methods: [GET] }
```
This would put only the order list under the firewall and allow only authorized users to access it. Once a user is authorized, it will have access to theirs orders only.
The second possible solution is to decorate the `\Sylius\Bundle\ApiBundle\Doctrine\QueryCollectionExtension\OrdersByLoggedInUserExtension` and throw `Symfony\Component\Security\Core\Exception\AccessDeniedException` if the class is executed for unauthorized user.
| {'CVE-2021-32720'} | 2022-04-19T19:03:00Z | 2021-06-29T03:12:04Z | MODERATE | 5.3 | {'CWE-200'} | {'https://github.com/advisories/GHSA-rpxh-vg2x-526v', 'https://github.com/Sylius/Sylius/commit/21d509851559230d03292b2a635a6951748c2758', 'https://github.com/Sylius/Sylius/security/advisories/GHSA-rpxh-vg2x-526v', 'https://packagist.org/packages/sylius/sylius', 'https://github.com/Sylius/Sylius/releases/tag/v1.9.5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32720'} | null | {'https://github.com/Sylius/Sylius/commit/21d509851559230d03292b2a635a6951748c2758'} | {'https://github.com/Sylius/Sylius/commit/21d509851559230d03292b2a635a6951748c2758'} |
GHSA | GHSA-r2wf-q3x4-hrv9 | Default development error handler in Ratpack is vulnerable to HTML content injection (XSS) | Versions of Ratpack from 0.9.10 through 1.7.5 are vulnerable to [CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')](https://cwe.mitre.org/data/definitions/79.html) (aka. XSS) in the development error handler. An attacker can utilize this to perform XSS when an exception message contains untrusted data.
As a simplistic example:
```java
RatpackServer startedServer = RatpackServer.start(server -> {
server.handlers(chain -> chain.all(ctx -> {
// User supplied query parameter
String message = ctx.getRequest().getQueryParams().get("message");
// User supplied data appended to the message in an exception
throw new RuntimeException("An error occurred: " + message);
}));
});
```
### Impact
- Cross-Site Scripting
### Patches
This vulnerability has been patched in Ratpack version 1.7.6.
### Workarounds
If you are unable to update your version of Ratpack, we recommend the following workarounds and mitigations.
- Ensure that development mode is disabled in production.
- Don't use real customer data (ie. untrusted user input) in development.
### References
- [Ratpack development mode](https://ratpack.io/manual/current/api/ratpack/server/ServerConfigBuilder.html#development-boolean-)
- [Code Patch - a3cbb13](https://github.com/ratpack/ratpack/commit/a3cbb13be1527874528c3b99fc33517c0297b6d3)
### For more information
If you have any questions or comments about this advisory:
- Open an issue in [ratpack/ratpack](https://github.com/ratpack/ratpack/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
- Ask in our [Slack channel](https://slack-signup.ratpack.io/)
| {'CVE-2019-10770'} | 2022-04-19T19:02:47Z | 2020-01-27T19:28:20Z | MODERATE | 6.1 | {'CWE-779'} | {'https://snyk.io/vuln/SNYK-JAVA-IORATPACK-534882', 'https://github.com/ratpack/ratpack/security/advisories/GHSA-r2wf-q3x4-hrv9', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10770', 'https://github.com/ratpack/ratpack/commit/a3cbb13be1527874528c3b99fc33517c0297b6d3', 'https://github.com/advisories/GHSA-r2wf-q3x4-hrv9'} | null | {'https://github.com/ratpack/ratpack/commit/a3cbb13be1527874528c3b99fc33517c0297b6d3'} | {'https://github.com/ratpack/ratpack/commit/a3cbb13be1527874528c3b99fc33517c0297b6d3'} |
GHSA | GHSA-9697-98pf-4rw7 | Heap OOB in `UpperBound` and `LowerBound` | ### Impact
An attacker can read from outside of bounds of heap allocated data by sending specially crafted illegal arguments to `tf.raw_ops.UpperBound`:
```python
import tensorflow as tf
tf.raw_ops.UpperBound(
sorted_input=[1,2,3],
values=tf.constant(value=[[0,0,0],[1,1,1],[2,2,2]],dtype=tf.int64),
out_type=tf.int64)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/searchsorted_op.cc#L85-L104) does not validate the rank of `sorted_input` argument:
```cc
void Compute(OpKernelContext* ctx) override {
const Tensor& sorted_inputs_t = ctx->input(0);
// ...
OP_REQUIRES(ctx, sorted_inputs_t.dim_size(0) == values_t.dim_size(0),
Status(error::INVALID_ARGUMENT,
"Leading dim_size of both tensors must match."));
// ...
if (output_t->dtype() == DT_INT32) {
OP_REQUIRES(ctx,
FastBoundsCheck(sorted_inputs_t.dim_size(1), ...));
// ...
}
```
As we access the first two dimensions of `sorted_inputs_t` tensor, it must have rank at least 2.
A similar issue occurs in `tf.raw_ops.LowerBound`.
### Patches
We have patched the issue in GitHub commit [42459e4273c2e47a3232cc16c4f4fff3b3a35c38](https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38).
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-37670'} | 2021-08-25T14:41:44Z | 2021-08-25T14:41:44Z | MODERATE | 5.5 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9697-98pf-4rw7', 'https://github.com/advisories/GHSA-9697-98pf-4rw7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37670', 'https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38'} | null | {'https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38'} | {'https://github.com/tensorflow/tensorflow/commit/42459e4273c2e47a3232cc16c4f4fff3b3a35c38'} |
GHSA | GHSA-wx69-rvg3-x7fc | XSS via prototype pollution in NodeBB | ### Impact
A prototype pollution vulnerability in the uploader module allowed a malicious user to inject arbitrary data (i.e. javascript) into the DOM, theoretically allowing for an account takeover when used in conjunction with a path traversal vulnerability disclosed at the same time as this report.
### Patches
The vulnerability has been patched as of v1.18.5.
### Workarounds
Cherry-pick commit hash 1783f918bc19568f421473824461ff2ed7755e4c 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-43787'} | 2022-04-19T19:03:13Z | 2021-11-30T22:21:01Z | CRITICAL | 9 | {'CWE-79'} | {'https://github.com/NodeBB/NodeBB/commit/1783f918bc19568f421473824461ff2ed7755e4c', 'https://github.com/advisories/GHSA-wx69-rvg3-x7fc', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43787', 'https://github.com/NodeBB/NodeBB/releases/tag/v1.18.5', 'https://github.com/NodeBB/NodeBB/security/advisories/GHSA-wx69-rvg3-x7fc'} | null | {'https://github.com/NodeBB/NodeBB/commit/1783f918bc19568f421473824461ff2ed7755e4c'} | {'https://github.com/NodeBB/NodeBB/commit/1783f918bc19568f421473824461ff2ed7755e4c'} |
GHSA | GHSA-cv25-3gmg-c6m8 | Injection in UserFrosting | In Userfrosting, versions v0.3.1 to v4.6.2 are vulnerable to Host Header Injection. By luring a victim application user to click on a link, an unauthenticated attacker can use the “forgot password” functionality to reset the victim’s password and successfully take over their account. | {'CVE-2021-25994'} | 2022-01-14T19:42:48Z | 2022-01-06T22:22:32Z | HIGH | 8.8 | {'CWE-74'} | {'https://github.com/userfrosting/UserFrosting/commit/796dd78757902435d1bd286415feea78098e45ba', 'https://github.com/advisories/GHSA-cv25-3gmg-c6m8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25994', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25994'} | null | {'https://github.com/userfrosting/UserFrosting/commit/796dd78757902435d1bd286415feea78098e45ba'} | {'https://github.com/userfrosting/UserFrosting/commit/796dd78757902435d1bd286415feea78098e45ba'} |
GHSA | GHSA-5qw5-89mw-wcg2 | Out of bounds write in Tensorflow | ### Impact
TensorFlow is vulnerable to a heap OOB write in [Grappler](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/graph_properties.cc#L1132-L1141):
```cc
Status SetUnknownShape(const NodeDef* node, int output_port) {
shape_inference::ShapeHandle shape =
GetUnknownOutputShape(node, output_port);
InferenceContext* ctx = GetContext(node);
if (ctx == nullptr) {
return errors::InvalidArgument("Missing context");
}
ctx->set_output(output_port, shape);
return Status::OK();
}
```
The [`set_output`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.h#L394) function writes to an array at the specified index:
```cc
void set_output(int idx, ShapeHandle shape) { outputs_.at(idx) = shape; }
```
Hence, this gives a malicious user a write primitive.
### Patches
We have patched the issue in GitHub commit [97282c6d0d34476b6ba033f961590b783fa184cd](https://github.com/tensorflow/tensorflow/commit/97282c6d0d34476b6ba033f961590b783fa184cd).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2022-23566'} | 2022-02-11T20:48:39Z | 2022-02-09T23:55:43Z | HIGH | 8.8 | {'CWE-787'} | {'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/grappler/costs/graph_properties.cc#L1132-L1141', 'https://github.com/advisories/GHSA-5qw5-89mw-wcg2', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/shape_inference.h#L394', 'https://github.com/tensorflow/tensorflow/commit/97282c6d0d34476b6ba033f961590b783fa184cd', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-5qw5-89mw-wcg2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23566'} | null | {'https://github.com/tensorflow/tensorflow/commit/97282c6d0d34476b6ba033f961590b783fa184cd'} | {'https://github.com/tensorflow/tensorflow/commit/97282c6d0d34476b6ba033f961590b783fa184cd'} |
GHSA | GHSA-84p7-fh9c-6g8h | Prototype Pollution in mixme | ### Impact
When copying properties from a source object to a target object, the target object can gain access to certain properties of the source object and modify their content.
### Patches
The problem was patch with a more agressive discovery of secured properties to filter out.
| null | 2021-09-20T19:52:24Z | 2021-09-20T19:52:24Z | HIGH | 0 | {'CWE-1321'} | {'https://github.com/adaltas/node-mixme/issues/1', 'https://github.com/adaltas/node-mixme/security/advisories/GHSA-84p7-fh9c-6g8h', 'https://github.com/advisories/GHSA-79jw-6wg7-r9g4', 'https://github.com/adaltas/node-mixme/issues/2', 'https://github.com/adaltas/node-mixme/commit/db70fe9bcbba451e9f8bd794a9fa7cdfa00125ad', 'https://github.com/advisories/GHSA-84p7-fh9c-6g8h'} | null | {'https://github.com/adaltas/node-mixme/commit/db70fe9bcbba451e9f8bd794a9fa7cdfa00125ad'} | {'https://github.com/adaltas/node-mixme/commit/db70fe9bcbba451e9f8bd794a9fa7cdfa00125ad'} |
GHSA | GHSA-r2mj-8wgq-73m6 | XML External Entity Reference in Glances | The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks.
| {'CVE-2021-23418'} | 2021-08-31T21:14:37Z | 2021-08-09T20:43:14Z | MODERATE | 6.3 | {'CWE-611'} | {'https://github.com/nicolargo/glances/commit/85d5a6b4af31fcf785d5a61086cbbd166b40b07a', 'https://github.com/nicolargo/glances/issues/1025', 'https://snyk.io/vuln/SNYK-PYTHON-GLANCES-1311807', 'https://github.com/advisories/GHSA-r2mj-8wgq-73m6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23418', 'https://github.com/nicolargo/glances/commit/4b87e979afdc06d98ed1b48da31e69eaa3a9fb94', 'https://github.com/nicolargo/glances/commit/9d6051be4a42f692392049fdbfc85d5dfa458b32'} | null | {'https://github.com/nicolargo/glances/commit/9d6051be4a42f692392049fdbfc85d5dfa458b32', 'https://github.com/nicolargo/glances/commit/4b87e979afdc06d98ed1b48da31e69eaa3a9fb94', 'https://github.com/nicolargo/glances/commit/85d5a6b4af31fcf785d5a61086cbbd166b40b07a'} | {'https://github.com/nicolargo/glances/commit/4b87e979afdc06d98ed1b48da31e69eaa3a9fb94', 'https://github.com/nicolargo/glances/commit/85d5a6b4af31fcf785d5a61086cbbd166b40b07a', 'https://github.com/nicolargo/glances/commit/9d6051be4a42f692392049fdbfc85d5dfa458b32'} |
GHSA | GHSA-c2jg-hw38-jrqq | Inconsistent Interpretation of HTTP Requests in twisted.web | The Twisted Web HTTP 1.1 server, located in the `twisted.web.http` module, parsed several HTTP request constructs more leniently than permitted by RFC 7230:
1. The Content-Length header value could have a `+` or `-` prefix.
2. Illegal characters were permitted in chunked extensions, such as the LF (`\n`) character.
3. Chunk lengths, which are expressed in hexadecimal format, could have a prefix of `0x`.
4. HTTP headers were stripped of all leading and trailing ASCII whitespace, rather than only space and HTAB (`\t`).
This non-conformant parsing can lead to desync if requests pass through multiple HTTP parsers, potentially resulting in HTTP request smuggling.
### Impact
You may be affected if:
1. You use Twisted Web's HTTP 1.1 server and/or proxy
2. You also pass requests through a different HTTP server and/or proxy
The specifics of the other HTTP parser matter. The original report notes that some versions of Apache Traffic Server and HAProxy have been vulnerable in the past. HTTP request smuggling may be a serious concern if you use a proxy to perform request validation or access control.
The Twisted Web client is not affected. The HTTP 2.0 server uses a different parser, so it is not affected.
### Patches
The issue has been addressed in Twisted 22.4.0rc1 and later.
### Workarounds
Other than upgrading Twisted, you could:
* Ensure any vulnerabilities in upstream proxies have been addressed, such as by upgrading them
* Filter malformed requests by other means, such as configuration of an upstream proxy
### Credits
This issue was initially reported by [Zhang Zeyu](https://github.com/zeyu2001). | {'CVE-2022-24801'} | 2022-05-04T03:49:00Z | 2022-04-04T21:29:41Z | HIGH | 8.1 | {'CWE-444'} | {'https://github.com/twisted/twisted/security/advisories/GHSA-c2jg-hw38-jrqq', 'https://github.com/twisted/twisted/releases/tag/twisted-22.4.0rc1', 'https://github.com/advisories/GHSA-c2jg-hw38-jrqq', 'https://lists.debian.org/debian-lts-announce/2022/05/msg00003.html', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24801', 'https://github.com/twisted/twisted/commit/592217e951363d60e9cd99c5bbfd23d4615043ac'} | null | {'https://github.com/twisted/twisted/commit/592217e951363d60e9cd99c5bbfd23d4615043ac'} | {'https://github.com/twisted/twisted/commit/592217e951363d60e9cd99c5bbfd23d4615043ac'} |
GHSA | GHSA-65f3-3278-7m65 | Improper Authorization in Gogs | ### Impact
Expired PAM accounts and accounts with expired passwords are continued to be seen as valid. Installations use PAM as authentication sources are affected.
### Patches
Expired PAM accounts and accounts with expired passwords are no longer being seen as valid. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.
### Workarounds
In addition to marking PAM accounts as expired, also disable/lock them. Running `usermod -L <username>` will add an exclamation mark to the password hash and would result in wrong passwords responses when trying to login.
### References
https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62/
### For more information
If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/6810.
| {'CVE-2022-0871'} | 2022-03-29T19:10:32Z | 2022-03-12T00:00:34Z | HIGH | 8.2 | {'CWE-863', 'CWE-285'} | {'https://github.com/advisories/GHSA-65f3-3278-7m65', 'https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62', 'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0871'} | null | {'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} | {'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} |
GHSA | GHSA-2p25-55c9-h58q | Overflow/crash in `tf.tile` when tiling tensor is large | ### Impact
If `tf.tile` is called with a large input argument then the TensorFlow process will crash due to a `CHECK`-failure caused by an overflow.
```python
import tensorflow as tf
import numpy as np
tf.keras.backend.tile(x=np.ones((1,1,1)), n=[100000000,100000000, 100000000])
```
The number of elements in the output tensor is too much for the `int64_t` type and the overflow is detected via a `CHECK` statement. This aborts the process.
### Patches
We have patched the issue in GitHub commit [9294094df6fea79271778eb7e7ae1bad8b5ef98f](https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f) (merging [#51138](https://github.com/tensorflow/tensorflow/pull/51138)).
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 externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46911). | {'CVE-2021-41198'} | 2021-11-10T19:33:58Z | 2021-11-10T19:33:58Z | MODERATE | 5.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/issues/46911', 'https://github.com/advisories/GHSA-2p25-55c9-h58q', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41198', 'https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2p25-55c9-h58q'} | null | {'https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f'} | {'https://github.com/tensorflow/tensorflow/commit/9294094df6fea79271778eb7e7ae1bad8b5ef98f'} |
GHSA | GHSA-h23m-w6x5-jwr4 | 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-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937. | {'CVE-2019-0923'} | 2021-03-29T21:00:08Z | 2021-03-29T21:00:08Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/972584709518380a4a3c2410b5fa151f6f0239b1', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0923', 'https://github.com/advisories/GHSA-h23m-w6x5-jwr4', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0923'} | null | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/972584709518380a4a3c2410b5fa151f6f0239b1'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/972584709518380a4a3c2410b5fa151f6f0239b1'} |
GHSA | GHSA-pr38-qpxm-g88x | Uncontrolled Resource Consumption in Apache ActiveMQ Artemis | In Apache ActiveMQ Artemis prior to 2.20.0 or 2.19.1, an attacker could partially disrupt availability (DoS) through uncontrolled resource consumption of memory. | {'CVE-2022-23913'} | 2022-05-03T02:20:46Z | 2022-02-06T00:00:55Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-pr38-qpxm-g88x', 'https://github.com/apache/activemq-artemis/pull/3871', 'https://github.com/github/codeql-java-CVE-coverage/issues/1061', 'https://github.com/apache/activemq-artemis/pull/3862', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23913', 'https://github.com/apache/activemq-artemis/pull/3871/commits/153d2e9a979aead8dff95fbc91d659ecc7d0fb82', 'https://github.com/apache/activemq-artemis/pull/3862/commits/1f92368240229b8f5db92a92a72c703faf83e9b7', 'https://lists.apache.org/thread/fjynj57rd99s814rdn5hzvmx8lz403q2', 'https://security.netapp.com/advisory/ntap-20220303-0003/', 'https://issues.apache.org/jira/browse/ARTEMIS-3593'} | null | {'https://github.com/apache/activemq-artemis/pull/3862/commits/1f92368240229b8f5db92a92a72c703faf83e9b7', 'https://github.com/apache/activemq-artemis/pull/3871/commits/153d2e9a979aead8dff95fbc91d659ecc7d0fb82'} | {'https://github.com/apache/activemq-artemis/pull/3871/commits/153d2e9a979aead8dff95fbc91d659ecc7d0fb82', 'https://github.com/apache/activemq-artemis/pull/3862/commits/1f92368240229b8f5db92a92a72c703faf83e9b7'} |
GHSA | GHSA-m9m5-cg5h-r582 | Improper random number generation in nanorand | An issue was discovered in the nanorand crate before 0.5.1 for Rust. It caused any random number generator (even ChaCha) to return all zeroes because integer truncation was mishandled. | {'CVE-2020-35926'} | 2021-08-25T20:50:24Z | 2021-08-25T20:50:24Z | CRITICAL | 5.1 | {'CWE-338'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-35926', 'https://github.com/advisories/GHSA-m9m5-cg5h-r582', 'https://twitter.com/aspenluxxxy/status/1336684692284772352', 'https://rustsec.org/advisories/RUSTSEC-2020-0089.html', 'https://github.com/Absolucy/nanorand-rs/commit/5ba218ac29df4786b002d7d12b47fa0c04a331f2'} | null | {'https://github.com/Absolucy/nanorand-rs/commit/5ba218ac29df4786b002d7d12b47fa0c04a331f2'} | {'https://github.com/Absolucy/nanorand-rs/commit/5ba218ac29df4786b002d7d12b47fa0c04a331f2'} |
GHSA | GHSA-94xh-2fmc-xf5j | command injection vulnerability | ### Impact
command injection vulnerability
### Patches
Problem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.27.11
### Workarounds
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()
### References
_Are there any links users can visit to find out more?_
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [systeminformation](https://github.com/sebhildebrandt/systeminformation/issues/new?template=bug_report.md) | {'CVE-2020-7752'} | 2021-10-08T21:15:37Z | 2020-10-27T20:30:20Z | HIGH | 8.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7752', 'https://www.npmjs.com/package/systeminformation', 'https://github.com/advisories/GHSA-94xh-2fmc-xf5j', 'https://github.com/sebhildebrandt/systeminformation/commit/931fecaec2c1a7dcc10457bb8cd552d08089da61', 'https://snyk.io/vuln/SNYK-JS-SYSTEMINFORMATION-1021909', 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-94xh-2fmc-xf5j', 'https://github.com/sebhildebrandt/systeminformation/blob/master/lib/internet.js'} | null | {'https://github.com/sebhildebrandt/systeminformation/commit/931fecaec2c1a7dcc10457bb8cd552d08089da61'} | {'https://github.com/sebhildebrandt/systeminformation/commit/931fecaec2c1a7dcc10457bb8cd552d08089da61'} |
GHSA | GHSA-44qp-9wwf-734r | Heap overflow in Tensorflow | ### Impact
The [implementation of `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273) is vulnerable to a heap overflow:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.SparseCountSparseOutput(
indices=[[-1,-1]],
values=[2],
dense_shape=[1, 1],
weights=[1],
binary_output=True,
minlength=-1,
maxlength=-1,
name=None)
```
### Patches
We have patched the issue in GitHub commits [2b7100d6cdff36aa21010a82269bc05a6d1cc74a](https://github.com/tensorflow/tensorflow/commit/2b7100d6cdff36aa21010a82269bc05a6d1cc74a) and [adbbabdb0d3abb3cdeac69e38a96de1d678b24b3](https://github.com/tensorflow/tensorflow/commit/adbbabdb0d3abb3cdeac69e38a96de1d678b24b3).
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 Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-21740'} | 2022-02-11T16:21:12Z | 2022-02-09T23:47:14Z | HIGH | 7.6 | {'CWE-787', 'CWE-120'} | {'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273', 'https://github.com/tensorflow/tensorflow/commit/adbbabdb0d3abb3cdeac69e38a96de1d678b24b3', 'https://github.com/advisories/GHSA-44qp-9wwf-734r', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-44qp-9wwf-734r', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21740', 'https://github.com/tensorflow/tensorflow/commit/2b7100d6cdff36aa21010a82269bc05a6d1cc74a'} | null | {'https://github.com/tensorflow/tensorflow/commit/adbbabdb0d3abb3cdeac69e38a96de1d678b24b3', 'https://github.com/tensorflow/tensorflow/commit/2b7100d6cdff36aa21010a82269bc05a6d1cc74a'} | {'https://github.com/tensorflow/tensorflow/commit/adbbabdb0d3abb3cdeac69e38a96de1d678b24b3', 'https://github.com/tensorflow/tensorflow/commit/2b7100d6cdff36aa21010a82269bc05a6d1cc74a'} |
GHSA | GHSA-prxj-c66c-4gcf | 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-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933, CVE-2019-0937. | {'CVE-2019-0924'} | 2021-03-29T21:00:12Z | 2021-03-29T21:00:12Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/advisories/GHSA-prxj-c66c-4gcf', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0924', 'https://github.com/chakra-core/ChakraCore/commit/6615113a09c0618ecc10e5680ffb978bf665641f', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0924'} | null | {'https://github.com/chakra-core/ChakraCore/commit/6615113a09c0618ecc10e5680ffb978bf665641f', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/6615113a09c0618ecc10e5680ffb978bf665641f'} |
GHSA | GHSA-m43c-649m-pm48 | Integer Overflow or Wraparound in OpenCV. | In opencv/modules/imgcodecs/src/utils.cpp, functions FillUniColor and FillUniGray do not check the input length, which can lead to integer overflow. If the image is from remote, may lead to remote code execution or denial of service. This affects Opencv 3.3 (corresponding with OpenCV-Python 3.3.0.9) and earlier. | {'CVE-2017-1000450'} | 2021-11-18T15:31:29Z | 2021-10-12T22:03:32Z | HIGH | 8.8 | {'CWE-190'} | {'https://lists.debian.org/debian-lts-announce/2018/01/msg00008.html', 'https://github.com/opencv/opencv/pull/9726/commits/c58152d94ba878b2d7d76bcac59146312199b9eb', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000450', 'https://github.com/blendin/pocs/blob/master/opencv/0.OOB_Write_FillUniColor', 'https://github.com/opencv/opencv/issues/9723', 'https://github.com/advisories/GHSA-m43c-649m-pm48', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html'} | null | {'https://github.com/opencv/opencv/pull/9726/commits/c58152d94ba878b2d7d76bcac59146312199b9eb'} | {'https://github.com/opencv/opencv/pull/9726/commits/c58152d94ba878b2d7d76bcac59146312199b9eb'} |
GHSA | GHSA-rpw6-9xfx-jvcx | Directory Traversal in Archive_Tar | Tar.php in Archive_Tar through 1.4.11 allows write operations with Directory Traversal due to inadequate checking of symbolic links, a related issue to CVE-2020-28948.
:exclamation: Note: There was an [initial fix](https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916) for this vulnerability made in version `1.4.12`. That fix introduced a bug which was [fixed in 1.4.13](https://github.com/pear/Archive_Tar/pull/36). Therefore we have set the first-patched-version to `1.4.13` which the earliest working version that avoids this vulnerability. | {'CVE-2020-36193'} | 2021-09-27T18:45:02Z | 2021-04-22T16:20:36Z | HIGH | 7.5 | {'CWE-22'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VJQQYDAOWHD6RDITDRPHFW7WY6BS3V5N/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42GPGVVFTLJYAKRI75IVB5R45NYQGEUR/', 'https://packagist.org/packages/pear/archive_tar', 'https://github.com/advisories/GHSA-rpw6-9xfx-jvcx', 'https://www.drupal.org/sa-core-2021-001', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FOZNK4FIIV7FSFCJNNFWMJZTTV7NFJV2/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36193', 'https://github.com/pear/Archive_Tar/releases/tag/1.4.13', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YKD5WEFA4WT6AVTMRAYBNXZNLWZHM7FH/', 'https://www.debian.org/security/2021/dsa-4894', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00018.html', 'https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916', 'https://lists.debian.org/debian-lts-announce/2021/04/msg00007.html', 'https://github.com/pear/Archive_Tar/issues/35', 'https://security.gentoo.org/glsa/202101-23', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/pear/archive_tar/CVE-2020-36193.yaml'} | null | {'https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916'} | {'https://github.com/pear/Archive_Tar/commit/cde460582ff389404b5b3ccb59374e9b389de916'} |
GHSA | GHSA-5jjv-x4fq-qjwp | Possible timing attack in derivation_endpoint | ### Impact
When using the `derivation_endpoint` plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL.
### Patches
The problem has been fixed by comparing sent and calculated signature in constant time, using `Rack::Utils.secure_compare`. Users using the `derivation_endpoint` plugin are urged to upgrade to Shrine 3.3.0 or greater.
### Workarounds
Users of older Shrine versions can apply the following monkey-patch after loading the `derivation_endpoint` plugin:
```rb
class Shrine
class UrlSigner
def verify_signature(string, signature)
if signature.nil?
fail InvalidSignature, "missing \"signature\" param"
elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
fail InvalidSignature, "provided signature does not match the calculated signature"
end
end
end
end
```
### References
You can read more about timing attacks [here](https://en.wikipedia.org/wiki/Timing_attack). | {'CVE-2020-15237'} | 2022-04-19T19:02:36Z | 2020-10-05T15:48:34Z | MODERATE | 5.9 | {'CWE-208', 'CWE-203'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15237', 'https://github.com/shrinerb/shrine/security/advisories/GHSA-5jjv-x4fq-qjwp', 'https://github.com/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0', 'https://github.com/advisories/GHSA-5jjv-x4fq-qjwp'} | null | {'https://github.com/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0'} | {'https://github.com/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0'} |
GHSA | GHSA-5xqr-grq4-qwgx | Moderate severity vulnerability that affects com.github.junrar:junrar | Archive.java in Junrar before 1.0.1, as used in Apache Tika and other products, is affected by a denial of service vulnerability due to an infinite loop when handling corrupt RAR files. | {'CVE-2018-12418'} | 2021-09-01T22:36:11Z | 2018-10-17T00:04:05Z | MODERATE | 5.5 | {'CWE-835'} | {'https://github.com/advisories/GHSA-5xqr-grq4-qwgx', 'https://github.com/junrar/junrar/pull/8', 'https://github.com/junrar/junrar/commit/ad8d0ba8e155630da8a1215cee3f253e0af45817', 'https://nvd.nist.gov/vuln/detail/CVE-2018-12418'} | null | {'https://github.com/junrar/junrar/commit/ad8d0ba8e155630da8a1215cee3f253e0af45817'} | {'https://github.com/junrar/junrar/commit/ad8d0ba8e155630da8a1215cee3f253e0af45817'} |
GHSA | GHSA-38rv-5jqc-m2cv | High severity vulnerability that affects recurly | The Recurly Client Python Library before 2.0.5, 2.1.16, 2.2.22, 2.3.1, 2.4.5, 2.5.1, 2.6.2 is vulnerable to a Server-Side Request Forgery vulnerability in the "Resource.get" method that could result in compromise of API keys or other critical resources. | {'CVE-2017-0906'} | 2021-01-08T20:03:04Z | 2019-01-04T17:48:09Z | HIGH | 0 | {'CWE-918'} | {'https://github.com/advisories/GHSA-38rv-5jqc-m2cv', 'https://hackerone.com/reports/288635', 'https://dev.recurly.com/page/python-updates', 'https://github.com/recurly/recurly-client-python/commit/049c74699ce93cf126feff06d632ea63fba36742', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0906'} | null | {'https://github.com/recurly/recurly-client-python/commit/049c74699ce93cf126feff06d632ea63fba36742'} | {'https://github.com/recurly/recurly-client-python/commit/049c74699ce93cf126feff06d632ea63fba36742'} |
GHSA | GHSA-72rj-36qc-47g7 | Information Disclosure | pgsync before 0.6.7 is affected by Information Disclosure of sensitive information. Syncing the schema with the --schema-first and --schema-only options is mishandled. For example, the sslmode connection parameter may be lost, which means that SSL would not be used. | {'CVE-2021-31671'} | 2021-06-09T23:09:49Z | 2021-04-27T15:54:52Z | HIGH | 7.5 | {'CWE-319'} | {'https://github.com/advisories/GHSA-72rj-36qc-47g7', 'https://rubygems.org/gems/pgsync', 'https://github.com/ankane/pgsync/commit/05cd18f5fc09407e4b544f2c12f819cabc50c40e', 'https://github.com/ankane/pgsync/blob/master/CHANGELOG.md#067-2021-04-26', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31671', 'https://github.com/ankane/pgsync/issues/121'} | null | {'https://github.com/ankane/pgsync/commit/05cd18f5fc09407e4b544f2c12f819cabc50c40e'} | {'https://github.com/ankane/pgsync/commit/05cd18f5fc09407e4b544f2c12f819cabc50c40e'} |
GHSA | GHSA-qhm4-jxv7-j9pq | Allocation of Resources Without Limits or Throttling and Uncontrolled Memory Allocation in Kubernetes | The Kubelet component in versions 1.15.0-1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via the kubelet API, including the unauthenticated HTTP read-only API typically served on port 10255, and the authenticated HTTPS API typically served on port 10250. | {'CVE-2020-8551'} | 2022-04-12T22:00:18Z | 2022-02-15T01:57:18Z | LOW | 4.3 | {'CWE-789'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://github.com/kubernetes/kubernetes/pull/87913', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8551', 'https://github.com/advisories/GHSA-qhm4-jxv7-j9pq', 'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc', 'https://github.com/kubernetes/kubernetes/issues/89377', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/2UOlsba2g0s'} | null | {'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc'} | {'https://github.com/kubernetes/kubernetes/commit/9802bfcec0580169cffce2a3d468689a407fa7dc'} |
GHSA | GHSA-j545-frh3-r9gq | SQL Injection in dolibarr | dolibarr is vulnerable to Improper Neutralization of Special Elements used in an SQL Command | {'CVE-2022-0224'} | 2022-01-21T23:56:39Z | 2022-01-21T23:56:39Z | HIGH | 8.3 | {'CWE-89'} | {'https://github.com/advisories/GHSA-j545-frh3-r9gq', 'https://huntr.dev/bounties/f1d1ce3e-ca92-4c7b-b1b8-934e28eaa486', 'https://github.com/dolibarr/dolibarr/commit/b9b45fb50618aa8053961f50bc8604b188d0ea79', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0224'} | null | {'https://github.com/dolibarr/dolibarr/commit/b9b45fb50618aa8053961f50bc8604b188d0ea79'} | {'https://github.com/dolibarr/dolibarr/commit/b9b45fb50618aa8053961f50bc8604b188d0ea79'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.