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-xfrc-7mj2-5xh9 | Undefined Behavior in zencashjs | Versions of `zencashjs` prior to 1.2.0 may cause loss of funds when used with cryptocurrency wallets. The package relies on a string comparison of the first two characters of a Horizen address to determine the destination address type of a transaction (P2PKH or P2SH). Due to the base58 address prefixes chosen in Horizen there exists the possibility of a clash of address prefixes for testnet P2PKH and mainnet P2SH addresses, testnet P2PKH addresses start with “zt” while a subset of mainnet P2SH addresses can also start with “zt”. The package interprets transactions sent to a “zt” P2SH address on mainnet as P2PKH transactions erroneously. Any funds sent to a mainnet P2SH multisignature address starting with “zt” will be sent to the wrong address and be lost.
## Recommendation
Upgrade to version 1.2.0 or later. | null | 2020-09-03T17:14:51Z | 2020-09-03T17:14:51Z | CRITICAL | 0 | null | {'https://github.com/advisories/GHSA-xfrc-7mj2-5xh9', 'https://www.npmjs.com/advisories/1035', 'https://github.com/ZencashOfficial/zencashjs/commit/db01bd94b9f8a956d7835e934500eaa643f8bd13#diff-42d8d2088a96641b563b25ad908b0c0fR146'} | null | {'https://github.com/ZencashOfficial/zencashjs/commit/db01bd94b9f8a956d7835e934500eaa643f8bd13#diff-42d8d2088a96641b563b25ad908b0c0fR146'} | {'https://github.com/ZencashOfficial/zencashjs/commit/db01bd94b9f8a956d7835e934500eaa643f8bd13#diff-42d8d2088a96641b563b25ad908b0c0fR146'} |
GHSA | GHSA-q86f-fmqf-qrf6 | Moderate severity vulnerability that affects mail | The mail gem before 2.5.5 for Ruby (aka A Really Ruby Mail Library) is vulnerable to SMTP command injection via CRLF sequences in a RCPT TO or MAIL FROM command, as demonstrated by CRLF sequences immediately before and after a DATA substring. | {'CVE-2015-9097'} | 2021-09-16T19:40:52Z | 2017-10-24T18:33:36Z | MODERATE | 6.1 | {'CWE-93'} | {'https://rubysec.com/advisories/mail-OSVDB-131677', 'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83', 'http://www.mbsd.jp/Whitepaper/smtpi.pdf', 'https://github.com/mikel/mail/pull/1097', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9097', 'http://openwall.com/lists/oss-security/2015/12/11/3', 'https://github.com/rubysec/ruby-advisory-db/issues/215', 'https://hackerone.com/reports/137631', 'https://github.com/advisories/GHSA-q86f-fmqf-qrf6'} | null | {'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83'} | {'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83'} |
GHSA | GHSA-3q55-66g3-p8xq | Cross-site Scripting in microweber | File upload filter bypass leading to stored XSS in GitHub repository microweber/microweber prior to 1.2.12. | {'CVE-2022-0926'} | 2022-03-22T19:36:42Z | 2022-03-13T00:00:54Z | MODERATE | 4.8 | {'CWE-79'} | {'https://huntr.dev/bounties/dc5d1555-0108-4627-b542-93352f35fa17', 'https://github.com/microweber/microweber/commit/89200cfcc2cfefe5554721e7fa3cf52f6a2a9120', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0926', 'https://github.com/advisories/GHSA-3q55-66g3-p8xq'} | null | {'https://github.com/microweber/microweber/commit/89200cfcc2cfefe5554721e7fa3cf52f6a2a9120'} | {'https://github.com/microweber/microweber/commit/89200cfcc2cfefe5554721e7fa3cf52f6a2a9120'} |
GHSA | GHSA-fxwf-4rqh-v8g3 | Insecure defaults due to CORS misconfiguration in socket.io | The package socket.io before 2.4.0 are vulnerable to Insecure Defaults due to CORS Misconfiguration. All domains are whitelisted by default. | {'CVE-2020-28481'} | 2021-01-29T19:57:43Z | 2021-01-20T21:22:37Z | MODERATE | 0 | {'CWE-453', 'CWE-346'} | {'https://github.com/advisories/GHSA-fxwf-4rqh-v8g3', 'https://snyk.io/vuln/SNYK-JS-SOCKETIO-1024859', 'https://github.com/socketio/socket.io/issues/3671', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28481', 'https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1056358', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1056357'} | null | {'https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7'} | {'https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7'} |
GHSA | GHSA-jff2-qjw8-5476 | Command Injection Vulnerability in systeminformation | ### Impact
command injection vulnerability
### Patches
Problem was fixed with a parameter check. Please upgrade to version >= 5.6.4
### Workarounds
If you cannot upgrade, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected. | {'CVE-2021-21388'} | 2021-04-30T17:24:30Z | 2021-04-06T17:30:14Z | HIGH | 8.9 | {'CWE-77', 'CWE-78'} | {'https://github.com/sebhildebrandt/systeminformation/commit/0be6fcd575c05687d1076d5cd6d75af2ebae5a46', 'https://github.com/sebhildebrandt/systeminformation/commit/7922366d707de7f20995fc8e30ac3153636bf35f', 'https://www.npmjs.com/package/systeminformation', 'https://github.com/sebhildebrandt/systeminformation/commit/01ef56cd5824ed6da1c11b37013a027fdef67524', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21388', 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-jff2-qjw8-5476', 'https://github.com/advisories/GHSA-jff2-qjw8-5476'} | null | {'https://github.com/sebhildebrandt/systeminformation/commit/0be6fcd575c05687d1076d5cd6d75af2ebae5a46', 'https://github.com/sebhildebrandt/systeminformation/commit/01ef56cd5824ed6da1c11b37013a027fdef67524', 'https://github.com/sebhildebrandt/systeminformation/commit/7922366d707de7f20995fc8e30ac3153636bf35f'} | {'https://github.com/sebhildebrandt/systeminformation/commit/7922366d707de7f20995fc8e30ac3153636bf35f', 'https://github.com/sebhildebrandt/systeminformation/commit/01ef56cd5824ed6da1c11b37013a027fdef67524', 'https://github.com/sebhildebrandt/systeminformation/commit/0be6fcd575c05687d1076d5cd6d75af2ebae5a46'} |
GHSA | GHSA-cvpc-8phh-8f45 | Out of bounds access in tensorflow-lite | ### Impact
In TensorFlow Lite, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor:https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/kernel_util.cc#L36
However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative `-1` value as index for these tensors:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/c/common.h#L82
This results in special casing during validation at model loading time: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L566-L580
Unfortunately, this means that the `-1` index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays.
This results in both read and write gadgets, albeit very limited in scope.
### Patches
We have patched the issue in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). We will release patch releases for all versions between 1.15 and 2.3.
We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
### Workarounds
A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that only operators which accept optional inputs use the `-1` special value and only for the tensors that they expect to be optional. Since this allow-list type approach is erro-prone, we advise upgrading to the patched code.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2020-15211'} | 2021-08-26T15:19:43Z | 2020-09-25T18:28:49Z | MODERATE | 4.8 | {'CWE-787', 'CWE-125'} | {'https://github.com/tensorflow/tensorflow/commit/cd31fd0ce0449a9e0f83dcad08d6ed7f1d6bef3f', 'https://github.com/advisories/GHSA-cvpc-8phh-8f45', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/tensorflow/tensorflow/commit/fff2c8326280c07733828f990548979bdc893859', 'https://github.com/tensorflow/tensorflow/commit/e11f55585f614645b360563072ffeb5c3eeff162', 'https://github.com/tensorflow/tensorflow/commit/46d5b0852528ddfd614ded79bccc75589f801bd9', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45', 'https://github.com/tensorflow/tensorflow/commit/00302787b788c5ff04cb6f62aed5a74d936e86c0', 'https://github.com/tensorflow/tensorflow/commit/1970c2158b1ffa416d159d03c3370b9a462aee35', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15211', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/1970c2158b1ffa416d159d03c3370b9a462aee35', 'https://github.com/tensorflow/tensorflow/commit/cd31fd0ce0449a9e0f83dcad08d6ed7f1d6bef3f', 'https://github.com/tensorflow/tensorflow/commit/e11f55585f614645b360563072ffeb5c3eeff162', 'https://github.com/tensorflow/tensorflow/commit/46d5b0852528ddfd614ded79bccc75589f801bd9', 'https://github.com/tensorflow/tensorflow/commit/00302787b788c5ff04cb6f62aed5a74d936e86c0', 'https://github.com/tensorflow/tensorflow/commit/fff2c8326280c07733828f990548979bdc893859'} | {'https://github.com/tensorflow/tensorflow/commit/00302787b788c5ff04cb6f62aed5a74d936e86c0', 'https://github.com/tensorflow/tensorflow/commit/1970c2158b1ffa416d159d03c3370b9a462aee35', 'https://github.com/tensorflow/tensorflow/commit/e11f55585f614645b360563072ffeb5c3eeff162', 'https://github.com/tensorflow/tensorflow/commit/fff2c8326280c07733828f990548979bdc893859', 'https://github.com/tensorflow/tensorflow/commit/cd31fd0ce0449a9e0f83dcad08d6ed7f1d6bef3f', 'https://github.com/tensorflow/tensorflow/commit/46d5b0852528ddfd614ded79bccc75589f801bd9'} |
GHSA | GHSA-mx43-r985-5h4m | Open redirect vulnerability in Sourcegraph | ### Impact
An open redirect vulnerability that allows users to be targeted for phishing attacks has been found in Sourcegraph instances configured with OAuth, OpenID, or SAML authentication enabled. Users targeted by these phishing attacks could have their authentication tokens silently harvested by an attacker.
### Resolution
Sourcegraph v3.14.4 and v3.15.1 have been released which resolve the vulnerability. ([associated change](https://github.com/sourcegraph/sourcegraph/pull/10167))
### Workarounds
Disabling OAuth, OpenID and/or SAML sign-in options until upgraded to the patched versions will secure Sourcegraph / workaround the issue.
### Timeline
- Apr 23, 8 AM PST: GitHub Security Lab reported the issue to Sourcegraph.
- Apr 23, 11 PM PST: A Sourcegraph engineer proposed a resolution for the vulnerability. https://github.com/sourcegraph/sourcegraph/pull/10167
- Apr 24, 3 AM PST: The proposed resolution was reviewed, approved, and merged.
- Apr 28, 2 PM PST: Patch releases for 3.14.4 and 3.15.1 were published.
- Apr 29, 10 PM PST: Mitre publicly disclosed [CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283).
- Apr 30, 11 AM PST: Sourcegraph issued a GitHub security advisory and notified all affected users.
### References
- [Mitre: CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283)
- [GitHub Security Lab: GHSL-2020-085](https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph)
- [detectify's blog post on open redirect vulnerabilities
](https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/)
### For more information
If you have any questions or comments about this advisory, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com) and include `CVE-2020-12283` in the title. | {'CVE-2020-12283'} | 2021-12-20T18:12:47Z | 2021-12-20T18:12:47Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/advisories/GHSA-mx43-r985-5h4m', 'https://github.com/sourcegraph/sourcegraph/pull/10167', 'https://github.com/sourcegraph/sourcegraph/blob/master/CHANGELOG.md', 'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12283', 'https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph', 'https://github.com/sourcegraph/sourcegraph/security/advisories/GHSA-mx43-r985-5h4m', 'https://github.com/sourcegraph/sourcegraph/compare/v3.15.0...v3.15.1'} | null | {'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64'} | {'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64'} |
GHSA | GHSA-fwh7-v4gf-xv7w | yetiforcecrm is vulnerable to Cross-site Scripting | yetiforcecrm is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). | {'CVE-2021-4116'} | 2022-01-03T15:55:41Z | 2021-12-16T21:00:45Z | MODERATE | 6.6 | {'CWE-79'} | {'https://huntr.dev/bounties/7561bae7-9053-4dc8-aa59-b71acfb1712c', 'https://github.com/yetiforcecompany/yetiforcecrm/commit/9cdb012ca64ff1f719f8120d5fd162cd5ef1013f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4116', 'https://github.com/advisories/GHSA-fwh7-v4gf-xv7w'} | null | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/9cdb012ca64ff1f719f8120d5fd162cd5ef1013f'} | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/9cdb012ca64ff1f719f8120d5fd162cd5ef1013f'} |
GHSA | GHSA-g6xv-8q23-w2q3 | SQL Injection in Gogs | Multiple SQL injection vulnerabilities in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.6.1105 Beta allow remote attackers to execute arbitrary SQL commands via the q parameter to (1) api/v1/repos/search, which is not properly handled in models/repo.go, or (2) api/v1/users/search, which is not properly handled in models/user.go. | {'CVE-2014-8682'} | 2021-06-29T18:32:48Z | 2021-06-29T18:32:48Z | HIGH | 7.3 | {'CWE-89'} | {'http://www.securityfocus.com/archive/1/533995/100/0/threaded', 'http://seclists.org/fulldisclosure/2014/Nov/31', 'http://seclists.org/fulldisclosure/2014/Nov/33', 'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d', 'https://github.com/gogits/gogs/releases/tag/v0.5.8', 'http://gogs.io/docs/intro/change_log.html', 'http://packetstormsecurity.com/files/129116/Gogs-Label-Search-Blind-SQL-Injection.html', 'http://www.exploit-db.com/exploits/35238', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8682', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98694', 'https://github.com/advisories/GHSA-g6xv-8q23-w2q3', 'https://www.exploit-db.com/exploits/35238', 'http://www.securityfocus.com/bid/71187', 'http://packetstormsecurity.com/files/129117/Gogs-Repository-Search-SQL-Injection.html'} | null | {'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d'} | {'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d'} |
GHSA | GHSA-h3fg-h5v3-vf8m | CSRF forgery protection bypass in solidus_frontend | ### Impact
CSRF vulnerability that allows a malicious site to add an item to the user's cart without their knowledge.
All `solidus_frontend` versions are affected. If you're using your own storefront, please, follow along to make sure you're not affected.
To reproduce the issue:
- Pick the id for a variant with available stock. From the rails console:
```ruby
Spree::Variant.in_stock.pluck(:id)
```
Say we pick variant id `2`.
- Launch your application, for instance, on `http://localhost:3000`:
```bash
bin/rails server
```
- Open your browser dev tools.
- Click on whatever link in your store.
- Copy the value of the `Cookie` request header sent for the previous request from your browser dev tools.
- Execute the following, using your previously selected variant id and the value of the `Cookie` header (notice how it doesn't contain any authentication token):
```bash
curl -X POST -d "variant_id=2&quantity=1" -H "Cookie: guest_token=eyJfcmFpbHMiOnsibWVzc2FnZSI6IklrWlRVMWRQWnpKMVZVdFNXRzlPVW1aaWJHTjZZa0VpIiwiZXhwIjpudWxsLCJwdXIiOiJjb29raWUuZ3Vlc3RfdG9rZW4ifX0%3D--5006ba5d346f621c760a29b6a797bf351d17d1b8; _sandbox_session=vhutu5%2FL9NmWrUpGc3DxrFA%2FFsQD1dHn1cNsD7nvE84zcjWf17Af4%2F%2F2Vab3md71b6KTb9NP6WktdXktpwH4eU01jEGIBXG5%2BMzW5nL0nb4W269qk1io4LYljvoOg8%2BZVll7oJCVkJLKKh0sSoS0Kg8j%2FCHHs%2BsShohP%2BGnA%2Bfr9Ub8H6HofpSmloSpsfHHygmX0ho03fEgzHJ4DD5wJctaNKwg7NhVikHh5kgIPPHl84OGCgv3p2oe9jR19HTxOKq7BtyvDd7XZsecWhkcfS8BPnvDDUWZG6qpAEFI5kWo81KkpSJ%2Bp6Q1HOo8%3D--n3G2vgaDG7VS%2B%2FhF--ZTjxBAkfGG3hpr4GRQ2S1Q%3D%3D; __profilin=p%3Dt" http://localhost:3000/orders/populate
```
- Reload your browser and look at how your cart got updated.
### Patches
Please, upgrade `solidus` to versions `3.1.5`, `3.0.5` or `2.11.14`.
After upgrading, make sure you read the "Upgrade notes" section below.
### Upgrade notes
The patch adds CSRF token verification to the "Add to cart" action. Adding forgery protection to a form that missed it can have some side effects.
#### `InvalidAuthenticityToken` errors
If you're using the `:exception` strategy, it's likely that after upgrading, you'll see more `ActionController::InvalidAuthenticityToken` errors popping out in your logs. Due to browser-side cache, a form can be re-rendered and sent without any attached request cookie (for instance, when re-opening a mobile browser). That will cause an authentication error, as the sent token won't match with the one in the session (none in this case). That's a known problem in the Rails community (see https://github.com/rails/rails/issues/21948), and, at this point, there's no perfect solution.
Any attempt to mitigate the issue should be seen at the application level. For an excellent survey of all the available options, take a look at https://github.com/betagouv/demarches-simplifiees.fr/blob/5b4f7f9ae9eaf0ac94008b62f7047e4714626cf9/doc/adr-csrf-forgery.md. The latter is a third-party link. As the information is relevant here, we're going to copy it below, but it should be clear that all the credit goes to @kemenaran:
> # Protecting against request forgery using CRSF tokens
>
> ## Context
>
> Rails has CSRF protection enabled by default, to protect against POST-based CSRF attacks.
>
> To protect from this, Rails stores two copies of a random token (the so-named CSRF token) on each request:
> - one copy embedded in each HTML page,
> - another copy in the user session.
>
> When performing a POST request, Rails checks that the two copies match – and otherwise denies the request. This protects against an attacker that would generate a form secretly pointing to our website: the attacker can't read the token in the session, and so can't post a form with a valid token.
>
> The problem is that, much more often, this has false positives. There are several cases for that, including:
>
> 1. The web browser (often mobile) loads a page containing a form, then is closed by the user. Later, when the browser is re-opened, it restores the page from the cache. But the session cookie has expired, and so is not restored – so the copy of the CSRF token stored in the session is missing. When the user submits the form, they get an "InvalidAuthenticityToken" exception.
>
> 2. The user attempts to fill a form, and gets an error message (usually in response to a POST request). They close the browser. When the browser is re-opened, it attempts to restore the page. On Chrome this is blocked by the browser, because the browser denies retrying a (probably non-idempotent) POST request. Safari however happily retries the POST request – but without sending any cookies (in an attempt to avoid having unexpected side-effects). So the copy of the CSRF token in the session is missing (because no cookie was sent), and the user get an "InvalidAuthenticityToken" exception.
>
> ## Options considered
>
> ### Extend the session cookie duration
>
> We can configure the session cookie to be valid for a longer time (like 2 weeks).
>
> Pros:
> - It solves 1., because when the browser restores the page, the session cookie is still valid.
>
> Cons:
> - Users would be signed-in for a much longer time by default, which has unacceptable security implications.
> - It doesn't solve 2. (because Safari doesn't send any cookie when restoring a page from a POST request)
>
> ### Change the cache parameters
>
> We can send a HTTP cache header stating 'Cache-Control: no-store, no-cache'. This instructs the browser to never keep any copy of the page, and to always make a request to the server to restore it.
>
> This solution was attempted during a year in production, and solved 1. – but also introduced another type of InvalidAuthenticityToken errors. In that scenario, the user attempts to fill a form, and gets an error message (usually in response to a POST request). They then navigate on another domain (like France Connect), then hit the "Back" button. Crossing back the domain boundary may cause the browser to either block the request or retry an invalid POST request.
>
> Pros:
> - It solves 1., because on relaunch the browser requests a fresh page again (instead of serving it from its cache), thus retrieving a fresh session and a fresh matching CSRF token.
>
> Cons:
> - It doesn't solve 2.
> - It causes another type of InvalidAuthenticityToken errors.
>
> ### Using a null-session strategy
>
> We can change the default protect_from_forgery strategy to :null_session. This makes the current request use an empty session for the request duration.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted.
>
> Cons:
> - The user is asked to sign-in only after filling and submitting the form, losing their time and data
> - The user will not be redirected to their original page after signing-in
> - It has potential security implications: as the (potentically malicious) request runs anyway, variables cached by a controller before the Null session is created may allow the form submission to succeed anyway (https://www.veracode.com/blog/managing-appsec/when-rails-protectfromforgery-fails)
>
> ### Using a reset-session strategy
>
> We can change the default protect_from_forgery strategy to :reset_session. This clears the user session permanently, logging them out until they log in again.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted.
>
> Cons:
> - A forgery error in a browser tab will disconnect the user in all its open tabs
> - It has potential security implications: as the (potentically malicious) request runs anyway, variables cached by a controller before the Null session is created may allow the form submission to succeed anyway (https://www.veracode.com/blog/managing-appsec/when-rails-protectfromforgery-fails)
> - It allows an attacker to disconnect an user on demand, which is not only inconvenient, but also has security implication (the attacker could then log the user on it's own attacker account, pretending to be the user account)
>
> ### Redirect to login form
>
> When a forgery error occurs, we can instead redirect to the login form.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted (but the user data is lost).
> - It kind of solves 2., by redirecting to a "Please sign-in" page when a previously POSTed form is reloaded.
>
> Cons:
> - Not all forms require authentication – so for public forms there is no point redirecting to the login form.
> - The user will not be redirected to their original page after signing-in (because setting the redirect path is a state-changing action, and it is dangerous to let an unauthorized request changing the state – an attacker could control the path where an user is automatically redirected to.)
> - The implementation is finicky, and may introduce security errors. For instance, a naive implementation that catches the exception and redirect_to the sign-in page will prevent Devise from running a cleanup code – which means the user will still be logged, and the CSRF protection is bypassed. However a well-tested implementation that lets Devise code run should avoid these pittfalls.
>
> ### Using a long-lived cookie for CSRF tokens
>
> Instead of storing the CSRF token in the session cookie (which is deleted when the browser is closed), we can instead store it in a longer-lived cookie. For this we need to patch Rails.
>
> Pros:
> - It solves 1., because when the user submits a stale form, even if the session cookie because stale, the long-lived CSRF cookie is still valid.
>
> Cons:
> - It doesn't solve 2., because when Safari retries a POST request, it sends none of the cookies (not even long-lived ones).
> - Patching Rails may introduce security issues (now or in the future)
#### Broken behavior due to session expiration + template cache
Although pretty unlikely, you should make sure that your current setup for cache/session expiration is compatible. The upgrade can break the addition of products to the cart if both:
- The "Add to cart" form is being cached (usually along with the variant information).
- A user session is reset at every or every few requests.
The token validation depends on the issuing and consuming sessions being the same. If a product page is cached with the token in it, it can become stale on a subsequent rendering if the session changes.
To check that you're safe, after having upgraded locally, go through the following steps:
- Enable cache on dev mode:
```bash
bin/rails dev:cache
```
- Visit the page for a variant with stock.
- Reload that page several times.
- Click on the "Add to cart" button.
- Remember to rerun `bin/rails dev:cache` to turn off cache again.
No error or session reset should happen.
Otherwise, you can try with:
- Revisiting how your session gets expired.
- Changing the caching strategy to exclude the token.
#### Using weaker CSRF protection strategies
It's also important to understand that a complete fix will only be in place when using the `:exception` forgery protection strategy. The `solidus_frontend` engine can't do pretty much anything otherwise. Using weaker CSRF strategies should be an informed and limited decision made by the application team. After the upgrade:
- An app using `:null_session` should also be safe, but there will be side effects. That strategy runs with a null object session. As such, no order and no user is found on it. A new `cart` state order is created in the database, associated with no user. Next time the user visits the site, they won't find any difference in its cart state.
- An app using `:reset_session` is not entirely safe. That strategy resets the session. That means that registered users will be logged out. Next time a user visits, they'll see the cart with the items added during the CSRF attack, although it won't be associated with their account in the case of registered users.
#### Reversing the update
If you still want to deploy the upgraded version before changing your application code (if the latter is needed), you can add the following workaround to your `config/application.rb` (however, take into account that you'll keep being vulnerable):
```ruby
config.after_initialize do
Spree::OrdersController.skip_before_action :verify_authenticity_token, only: [:populate]
end
```
### Workarounds
If an upgrade is not an option, you can work around the issue by adding the following to `config/application.rb`:
```ruby
config.after_initialize do
Spree::OrdersController.protect_from_forgery with: ApplicationController.forgery_protection_strategy.name.demodulize.underscore.to_sym, only: [:populate]
end
```
However, go through the same safety check detailed on "Upgrade notes" above.
### References
- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)
- [How CSRF tokens are generated and validated on Rails](https://medium.com/rubyinside/a-deep-dive-into-csrf-protection-in-rails-19fa0a42c0ef)
- [Solidus security](https://solidus.io/security/)
### For more information
If you have any questions or comments about this advisory:
* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
| {'CVE-2021-43846'} | 2022-01-06T18:33:44Z | 2022-01-06T18:33:44Z | MODERATE | 5.3 | {'CWE-352'} | {'https://github.com/solidusio/solidus/security/advisories/GHSA-h3fg-h5v3-vf8m', 'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://github.com/advisories/GHSA-h3fg-h5v3-vf8m', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43846'} | null | {'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81'} | {'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81'} |
GHSA | GHSA-g644-pr5v-vppf | Insertion of Sensitive Information into Log File in Apache NiFi | In Apache NiFi 1.10.0 to 1.11.4, the NiFi stateless execution engine produced log output which included sensitive property values. When a flow was triggered, the flow definition configuration JSON was printed, potentially containing sensitive values in plaintext. | {'CVE-2020-9486'} | 2022-01-06T20:41:02Z | 2022-01-06T20:41:02Z | HIGH | 7.5 | {'CWE-532'} | {'https://nifi.apache.org/security#CVE-2020-9486', 'https://github.com/advisories/GHSA-g644-pr5v-vppf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9486', 'https://github.com/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0'} | null | {'https://github.com/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0'} | {'https://github.com/apache/nifi/commit/148537d64a017b73160b0d49943183c18f883ab0'} |
GHSA | GHSA-5726-g6r9-5f22 | Potential for Script Injection in syntax-error | Versions of `syntax-error` prior to 1.1.1 are affected by a cross-site scripting vulnerability which may allow a malicious file to execute code when browserified.
## Recommendation
Update to version 1.1.1 or later. | {'CVE-2014-7192'} | 2022-04-19T19:03:25Z | 2017-10-24T18:33:36Z | HIGH | 0 | {'CWE-94'} | {'https://www.npmjs.com/advisories/37', 'https://github.com/advisories/GHSA-5726-g6r9-5f22', 'http://www-01.ibm.com/support/docview.wss?uid=swg21690815', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/96728', 'https://nodesecurity.io/advisories/syntax-error-potential-script-injection', 'https://github.com/substack/node-syntax-error/commit/9aa4e66eb90ec595d2dba55e6f9c2dd9a668b309', 'https://github.com/substack/node-browserify/blob/master/changelog.markdown#421', 'https://nvd.nist.gov/vuln/detail/CVE-2014-7192'} | null | {'https://github.com/substack/node-syntax-error/commit/9aa4e66eb90ec595d2dba55e6f9c2dd9a668b309'} | {'https://github.com/substack/node-syntax-error/commit/9aa4e66eb90ec595d2dba55e6f9c2dd9a668b309'} |
GHSA | GHSA-v6r6-84gr-92rm | Heap buffer overflow in `AvgPool3DGrad` | ### Impact
The implementation of `tf.raw_ops.AvgPool3DGrad` is vulnerable to a heap buffer overflow:
```python
import tensorflow as tf
orig_input_shape = tf.constant([10, 6, 3, 7, 7], shape=[5], dtype=tf.int32)
grad = tf.constant([0.01, 0, 0], shape=[3, 1, 1, 1, 1], dtype=tf.float32)
ksize = [1, 1, 1, 1, 1]
strides = [1, 1, 1, 1, 1]
padding = "SAME"
tf.raw_ops.AvgPool3DGrad(
orig_input_shape=orig_input_shape, grad=grad, ksize=ksize, strides=strides,
padding=padding)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/d80ffba9702dc19d1fac74fc4b766b3fa1ee976b/tensorflow/core/kernels/pooling_ops_3d.cc#L376-L450) assumes that the `orig_input_shape` and `grad` tensors have similar first and last dimensions but does not check that this assumption is validated.
### Patches
We have patched the issue in GitHub commit [6fc9141f42f6a72180ecd24021c3e6b36165fe0d](https://github.com/tensorflow/tensorflow/commit/6fc9141f42f6a72180ecd24021c3e6b36165fe0d).
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-29577'} | 2021-05-21T17:08:45Z | 2021-05-21T14:26:18Z | LOW | 2.5 | {'CWE-119', 'CWE-787'} | {'https://github.com/advisories/GHSA-v6r6-84gr-92rm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29577', 'https://github.com/tensorflow/tensorflow/commit/6fc9141f42f6a72180ecd24021c3e6b36165fe0d', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-v6r6-84gr-92rm'} | null | {'https://github.com/tensorflow/tensorflow/commit/6fc9141f42f6a72180ecd24021c3e6b36165fe0d'} | {'https://github.com/tensorflow/tensorflow/commit/6fc9141f42f6a72180ecd24021c3e6b36165fe0d'} |
GHSA | GHSA-69q2-p9xp-739v | XML Injection in petl | petl before 1.68, in some configurations, allows resolution of entities in an XML document. | {'CVE-2020-29128'} | 2022-03-22T22:08:42Z | 2021-04-20T16:32:08Z | CRITICAL | 9.8 | {'CWE-91'} | {'https://petl.readthedocs.io/en/stable/changes.html', 'https://github.com/petl-developers/petl/pull/527', 'https://nvd.nist.gov/vuln/detail/CVE-2020-29128', 'https://github.com/petl-developers/petl/compare/v1.6.7...v1.6.8', 'https://github.com/petl-developers/petl/pull/527/commits/1b0a09f08c3cdfe2e69647bd02f97c1367a5b5f8', 'https://github.com/petl-developers/petl/issues/526', 'https://github.com/petl-developers/petl/security/advisories/GHSA-f5gc-p5m3-v347', 'https://github.com/nvn1729/advisories/blob/master/cve-2020-29128.md', 'https://github.com/advisories/GHSA-69q2-p9xp-739v'} | null | {'https://github.com/petl-developers/petl/pull/527/commits/1b0a09f08c3cdfe2e69647bd02f97c1367a5b5f8'} | {'https://github.com/petl-developers/petl/pull/527/commits/1b0a09f08c3cdfe2e69647bd02f97c1367a5b5f8'} |
GHSA | GHSA-6xj3-fhrf-rjgc | Cross-site Scripting in microweber | XSS in /demo/module/?module=HERE in GitHub repository microweber/microweber prior to 1.2.15. Typical impact of XSS attacks. | {'CVE-2022-1504'} | 2022-04-28T21:11:46Z | 2022-04-28T00:00:34Z | MODERATE | 6.3 | {'CWE-79'} | {'https://github.com/microweber/microweber/commit/1f6a4de416a85e626dc643bb5ceb916e4802223e', 'https://github.com/advisories/GHSA-6xj3-fhrf-rjgc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1504', 'https://huntr.dev/bounties/b8e5c324-3dfe-46b4-8095-1697c6b0a6d6'} | null | {'https://github.com/microweber/microweber/commit/1f6a4de416a85e626dc643bb5ceb916e4802223e'} | {'https://github.com/microweber/microweber/commit/1f6a4de416a85e626dc643bb5ceb916e4802223e'} |
GHSA | GHSA-cvx5-m8vg-vxgc | Arbitrary filesystem write access from velocity. | ### Impact
The velocity scripts is not properly sandboxed against using the Java File API to perform read or write operations on the filesystem. Now writing an attacking script in velocity requires the Script rights in XWiki so not all users can use it, and it also requires finding an XWiki API which returns a File.
### Patches
The problem has been patched on versions 12.6.7, 12.10.3 and 13.0RC1.
### 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-5168
### 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-24897'} | 2022-05-03T17:50:36Z | 2022-04-28T21:16:40Z | HIGH | 7.5 | {'CWE-22'} | {'https://github.com/xwiki/xwiki-commons/security/advisories/GHSA-cvx5-m8vg-vxgc', 'https://github.com/xwiki/xwiki-commons/commit/215951cfb0f808d0bf5b1097c9e7d1e503449ab8', 'https://jira.xwiki.org/browse/XWIKI-5168', 'https://github.com/advisories/GHSA-cvx5-m8vg-vxgc'} | null | {'https://github.com/xwiki/xwiki-commons/commit/215951cfb0f808d0bf5b1097c9e7d1e503449ab8'} | {'https://github.com/xwiki/xwiki-commons/commit/215951cfb0f808d0bf5b1097c9e7d1e503449ab8'} |
GHSA | GHSA-9f46-5r25-5wfm | Time-of-check Time-of-use (TOCTOU) Race Condition in league/flysystem | ### Impact
The whitespace normalisation using in 1.x and 2.x removes any unicode whitespace. Under certain specific conditions this could potentially allow a malicious user to execute code remotely.
The conditions:
- A user is allowed to supply the path or filename of an uploaded file.
- The supplied path or filename is not checked against unicode chars.
- The supplied pathname checked against an extension deny-list, not an allow-list.
- The supplied path or filename contains a unicode whitespace char in the extension.
- The uploaded file is stored in a directory that allows PHP code to be executed.
Given these conditions are met a user can upload and execute arbitrary code on the system under attack.
### Patches
The unicode whitespace removal has been replaced with a rejection (exception).
The library has been patched in:
- 1.x: https://github.com/thephpleague/flysystem/commit/f3ad69181b8afed2c9edf7be5a2918144ff4ea32
- 2.x: https://github.com/thephpleague/flysystem/commit/a3c694de9f7e844b76f9d1b61296ebf6e8d89d74
### Workarounds
For 1.x users, upgrade to 1.1.4. For 2.x users, upgrade to 2.1.1.
| {'CVE-2021-32708'} | 2022-04-19T19:03:01Z | 2021-06-29T03:13:28Z | CRITICAL | 9.8 | {'CWE-367'} | {'https://github.com/thephpleague/flysystem/commit/a3c694de9f7e844b76f9d1b61296ebf6e8d89d74', 'https://github.com/advisories/GHSA-9f46-5r25-5wfm', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NWPTENBYKI2IG47GI4DHAACLNRLTWUR5/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32708', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RNZSWK4GOMJOOHKLZEOE5AQSLC4DNCRZ/', 'https://packagist.org/packages/league/flysystem', 'https://github.com/thephpleague/flysystem/security/advisories/GHSA-9f46-5r25-5wfm', 'https://github.com/thephpleague/flysystem/commit/f3ad69181b8afed2c9edf7be5a2918144ff4ea32'} | null | {'https://github.com/thephpleague/flysystem/commit/f3ad69181b8afed2c9edf7be5a2918144ff4ea32', 'https://github.com/thephpleague/flysystem/commit/a3c694de9f7e844b76f9d1b61296ebf6e8d89d74'} | {'https://github.com/thephpleague/flysystem/commit/a3c694de9f7e844b76f9d1b61296ebf6e8d89d74', 'https://github.com/thephpleague/flysystem/commit/f3ad69181b8afed2c9edf7be5a2918144ff4ea32'} |
GHSA | GHSA-wwvv-x5mq-h3jj | Use of Cryptographically Weak Pseudo-Random Number Generator in yiisoft/yii2-dev | yii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator | {'CVE-2021-3692'} | 2022-04-26T18:04:49Z | 2021-09-01T18:35:26Z | MODERATE | 5.3 | {'CWE-338', 'CWE-330'} | {'https://huntr.dev/bounties/55517f19-5c28-4db2-8b00-f78f841e8aba', 'https://github.com/yiisoft/yii2/commit/13f27e4d920a05d53236139e8b07007acd046a46', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3692', 'https://github.com/advisories/GHSA-wwvv-x5mq-h3jj'} | null | {'https://github.com/yiisoft/yii2/commit/13f27e4d920a05d53236139e8b07007acd046a46'} | {'https://github.com/yiisoft/yii2/commit/13f27e4d920a05d53236139e8b07007acd046a46'} |
GHSA | GHSA-gh32-pc56-4c96 | Information Exposure in jaegar | Sensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials. | {'CVE-2020-10750'} | 2021-05-18T18:35:02Z | 2021-05-18T18:35:02Z | LOW | 7.1 | {'CWE-200', 'CWE-532'} | {'https://github.com/jaegertracing/jaeger/releases/tag/v1.18.1', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10750', 'https://github.com/advisories/GHSA-gh32-pc56-4c96', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10750', 'https://bugzilla.redhat.com/show_bug.cgi?id=1838401', 'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace'} | null | {'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace'} | {'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace'} |
GHSA | GHSA-fmx4-26r3-wxpf | Integer overflow in cmark-gfm table parsing extension leads to heap memory corruption | ### Impact
CommonMarker uses `cmark-gfm` for rendering [Github Flavored Markdown](https://github.github.com/gfm/). An [integer overflow in `cmark-gfm`'s table row parsing](https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4x) may lead to heap memory corruption when parsing tables who's marker rows contain more than UINT16_MAX columns. The impact of this heap corruption ranges from Information Leak to Arbitrary Code Execution.
If affected versions of CommonMarker are used for rendering remote user controlled markdown, this vulnerability may lead to Remote Code Execution (RCE).
### Patches
This vulnerability has been patched in the following CommonMarker release:
- v0.23.4
### Workarounds
The vulnerability exists in the table markdown extensions of `cmark-gfm`. Disabling any use of the table extension will prevent this vulnerability from being triggered.
### References
- https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4x
### Acknowledgements
We would like to thank Felix Wilhelm of Google's Project Zero for reporting this vulnerability
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [CommonMarker](http://github.com/gjtorikian/commonmarker) | null | 2022-03-03T20:29:09Z | 2022-03-03T20:28:47Z | HIGH | 8.8 | {'CWE-190'} | {'https://github.com/gjtorikian/commonmarker/security/advisories/GHSA-fmx4-26r3-wxpf', 'https://github.com/advisories/GHSA-fmx4-26r3-wxpf', 'https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3', 'https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4x'} | null | {'https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3'} | {'https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3'} |
GHSA | GHSA-h6ch-v84p-w6p9 | Regular Expression Denial of Service (ReDoS) | A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. | null | 2021-02-24T19:27:03Z | 2019-06-13T18:58:54Z | HIGH | 0 | {'CWE-400'} | {'https://www.whitesourcesoftware.com/vulnerability-database/WS-2018-0590', 'https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0', 'https://github.com/advisories/GHSA-h6ch-v84p-w6p9', 'https://snyk.io/vuln/npm:diff:20180305', 'https://bugzilla.redhat.com/show_bug.cgi?id=1552148', 'https://www.npmjs.com/advisories/1631'} | null | {'https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0'} | {'https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0'} |
GHSA | GHSA-hmg3-c7xj-6qwm | Heap buffer overflow in `SparseTensorToCSRSparseMatrix` | ### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in converting sparse tensors to CSR Sparse matrices:
```python
import tensorflow as tf
import numpy as np
from tensorflow.python.ops.linalg.sparse import sparse_csr_matrix_ops
indices_array = np.array([[0, 0]])
value_array = np.array([0.0], dtype=np.float32)
dense_shape = [0, 0]
st = tf.SparseTensor(indices_array, value_array, dense_shape)
values_tensor = sparse_csr_matrix_ops.sparse_tensor_to_csr_sparse_matrix(
st.indices, st.values, st.dense_shape)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/800346f2c03a27e182dd4fba48295f65e7790739/tensorflow/core/kernels/sparse/kernels.cc#L66) does a double redirection to access an element of an array allocated on the heap:
```cc
csr_row_ptr(indices(i, 0) + 1) += 1;
```
If the value at `indices(i, 0)` is such that `indices(i, 0) + 1` is outside the bounds of `csr_row_ptr`, this results in writing outside of bounds of heap allocated data.
### Patches
We have patched the issue in GitHub commit [1e922ccdf6bf46a3a52641f99fd47d54c1decd13](https://github.com/tensorflow/tensorflow/commit/1e922ccdf6bf46a3a52641f99fd47d54c1decd13).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29545'} | 2021-05-21T14:23:25Z | 2021-05-21T14:23:25Z | LOW | 2.5 | {'CWE-131'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hmg3-c7xj-6qwm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29545', 'https://github.com/advisories/GHSA-hmg3-c7xj-6qwm', 'https://github.com/tensorflow/tensorflow/commit/1e922ccdf6bf46a3a52641f99fd47d54c1decd13'} | null | {'https://github.com/tensorflow/tensorflow/commit/1e922ccdf6bf46a3a52641f99fd47d54c1decd13'} | {'https://github.com/tensorflow/tensorflow/commit/1e922ccdf6bf46a3a52641f99fd47d54c1decd13'} |
GHSA | GHSA-w3gh-g32m-cvhr | High severity vulnerability that affects org.apache.cxf.fediz:fediz-jetty8, org.apache.cxf.fediz:fediz-jetty9, org.apache.cxf.fediz:fediz-spring, org.apache.cxf.fediz:fediz-spring2, and org.apache.cxf.fediz:fediz-spring3 | Versions of Apache CXF Fediz prior to 1.4.4 do not fully disable Document Type Declarations (DTDs) when either parsing the Identity Provider response in the application plugins, or in the Identity Provider itself when parsing certain XML-based parameters. | {'CVE-2018-8038'} | 2021-06-17T18:59:46Z | 2018-10-18T16:56:47Z | HIGH | 0 | {'CWE-20'} | {'http://cxf.apache.org/security-advisories.data/CVE-2018-8038.txt.asc', 'https://nvd.nist.gov/vuln/detail/CVE-2018-8038', 'https://lists.apache.org/thread.html/rc774278135816e7afc943dc9fc78eb0764f2c84a2b96470a0187315c@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rff42cfa5e7d75b7c1af0e37589140a8f1999e578a75738740b244bd4@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rd49aabd984ed540c8ff7916d4d79405f3fa311d2fdbcf9ed307839a6@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf@%3Ccommits.cxf.apache.org%3E', 'https://github.com/apache/cxf-fediz/commit/b6ed9865d0614332fa419fe4b6d0fe81bc2e660d', 'https://lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/f0a6a05ec3b3a00458da43712b0ff3a2f573175d9bfb39fb0de21424@%3Cdev.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4@%3Ccommits.cxf.apache.org%3E', 'http://www.securitytracker.com/id/1041220', 'https://github.com/advisories/GHSA-w3gh-g32m-cvhr'} | null | {'https://github.com/apache/cxf-fediz/commit/b6ed9865d0614332fa419fe4b6d0fe81bc2e660d'} | {'https://github.com/apache/cxf-fediz/commit/b6ed9865d0614332fa419fe4b6d0fe81bc2e660d'} |
GHSA | GHSA-fwr7-v2mv-hh25 | Prototype Pollution in async | A vulnerability exists in Async through 3.2.1 for 3.x and through 2.6.3 for 2.x (fixed in 3.2.2 and 2.6.4), which could let a malicious user obtain privileges via the `mapValues()` method. | {'CVE-2021-43138'} | 2022-04-20T19:12:25Z | 2022-04-07T00:00:17Z | HIGH | 7.8 | {'CWE-1321'} | {'https://github.com/caolan/async/pull/1828', 'https://github.com/caolan/async/commit/8f7f90342a6571ba1c197d747ebed30c368096d2', 'https://github.com/caolan/async/commit/e1ecdbf79264f9ab488c7799f4c76996d5dca66d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43138', 'https://jsfiddle.net/oz5twjd9/', 'https://github.com/caolan/async/blob/master/lib/mapValuesLimit.js', 'https://github.com/advisories/GHSA-fwr7-v2mv-hh25', 'https://github.com/caolan/async/blob/master/lib/internal/iterator.js', 'https://github.com/caolan/async/blob/v2.6.4/CHANGELOG.md#v264'} | null | {'https://github.com/caolan/async/commit/8f7f90342a6571ba1c197d747ebed30c368096d2', 'https://github.com/caolan/async/commit/e1ecdbf79264f9ab488c7799f4c76996d5dca66d'} | {'https://github.com/caolan/async/commit/e1ecdbf79264f9ab488c7799f4c76996d5dca66d', 'https://github.com/caolan/async/commit/8f7f90342a6571ba1c197d747ebed30c368096d2'} |
GHSA | GHSA-hjfx-8p6c-g7gx | Insufficient Verification of Data Authenticity in Pillow | An issue was discovered in Pillow before 8.2.0. For BLP data, BlpImagePlugin did not properly check that reads (after jumping to file offsets) returned data. This could lead to a DoS where the decoder could be run a large number of times on empty data. | {'CVE-2021-28678'} | 2021-07-16T14:34:17Z | 2021-06-08T18:49:20Z | MODERATE | 5.5 | {'CWE-345'} | {'https://github.com/advisories/GHSA-hjfx-8p6c-g7gx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28678', 'https://github.com/python-pillow/Pillow/pull/5377', 'https://github.com/python-pillow/Pillow/pull/5377/commits/496245aa4365d0827390bd0b6fbd11287453b3a1', 'https://security.gentoo.org/glsa/202107-33', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MQHA5HAIBOYI3R6HDWCLAGFTIQP767FL/', 'https://pillow.readthedocs.io/en/stable/releasenotes/8.2.0.html#cve-2021-28678-fix-blp-dos'} | null | {'https://github.com/python-pillow/Pillow/pull/5377/commits/496245aa4365d0827390bd0b6fbd11287453b3a1'} | {'https://github.com/python-pillow/Pillow/pull/5377/commits/496245aa4365d0827390bd0b6fbd11287453b3a1'} |
GHSA | GHSA-f7vx-j8mp-3h2x | Insufficient Verification of Data Authenticity in Eclipse Theia | In Eclipse Theia versions 0.3.9 through 0.15.0, one of the default pre-packaged Theia extensions is "Mini-Browser", published as "@theia/mini-browser" on npmjs.com. This extension, for its own needs, exposes a HTTP endpoint that allows to read the content of files on the hosts filesystem, given their path, without restrictions on the requesters origin. This design is vulnerable to being exploited remotely through a DNS rebinding attack or a drive-by download of a carefully crafted exploit. | {'CVE-2019-17636'} | 2021-04-13T15:18:01Z | 2021-04-13T15:18:01Z | HIGH | 8.1 | {'CWE-345'} | {'https://github.com/eclipse-theia/theia/pull/7205', 'https://github.com/advisories/GHSA-f7vx-j8mp-3h2x', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=551747', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17636', 'https://github.com/eclipse-theia/theia/commit/b212d07f915df1509180944ee3132714bc2636bf'} | null | {'https://github.com/eclipse-theia/theia/commit/b212d07f915df1509180944ee3132714bc2636bf'} | {'https://github.com/eclipse-theia/theia/commit/b212d07f915df1509180944ee3132714bc2636bf'} |
GHSA | GHSA-47wv-vhj2-g66m | Use of insecure temporary file in Horovod | ### Impact
The insecure `tempfile.mktemp()` is used when Horovod is run in an LSF job with `jsrun`. In that situation, a jsrun rank file is created with `mktemp`, which could be hijacked by another process to read or manipulate the content.
This issue does not impact the use of MPI, Gloo, Spark or Ray.
### Patches
The problem has been fixed in [b96ecae4](https://github.com/horovod/horovod/commit/b96ecae4dc69fc0a83c7c2d3f1dde600c20a1b41).
### Workarounds
The rank file is not created when `binding_args` are provided in the `Settings` instance.
### References
Please see https://github.com/horovod/horovod/pull/3358 for details.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/horovod/horovod](https://github.com/horovod/horovod/issues/new/choose) | {'CVE-2022-0315'} | 2022-04-05T00:10:46Z | 2022-03-29T19:18:32Z | HIGH | 8.2 | {'CWE-668', 'CWE-377'} | {'https://github.com/pypa/advisory-database/tree/main/vulns/horovod/PYSEC-2022-175.yaml', 'https://github.com/horovod/horovod/security/advisories/GHSA-47wv-vhj2-g66m', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0315', 'https://github.com/advisories/GHSA-47wv-vhj2-g66m', 'https://github.com/horovod/horovod/pull/3358', 'https://github.com/horovod/horovod/commit/b96ecae4dc69fc0a83c7c2d3f1dde600c20a1b41', 'https://huntr.dev/bounties/7e50397b-dd63-4bb5-b56d-704094a7da45'} | null | {'https://github.com/horovod/horovod/commit/b96ecae4dc69fc0a83c7c2d3f1dde600c20a1b41'} | {'https://github.com/horovod/horovod/commit/b96ecae4dc69fc0a83c7c2d3f1dde600c20a1b41'} |
GHSA | GHSA-jgwr-3qm3-26f3 | Potential remote code execution in Apache Tomcat | The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue. | {'CVE-2021-25329'} | 2022-02-08T21:33:58Z | 2021-03-19T20:11:13Z | CRITICAL | 7 | {'CWE-502'} | {'https://security.netapp.com/advisory/ntap-20210409-0002/', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cannounce.tomcat.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00018.html', 'https://lists.apache.org/thread.html/rb51ccd58b2152fc75125b2406fc93e04ca9d34e737263faa6ff0f41f@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r732b2ca289dc02df2de820e8775559abd6c207f159e39f559547a085@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r11ce01e8a4c7269b88f88212f21830edf73558997ac7744f37769b77@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/rf6d5d57b114678d8898005faef31e9fd6d7c981fcc4ccfc3bc272fc9@%3Cdev.tomcat.apache.org%3E', 'https://github.com/advisories/GHSA-jgwr-3qm3-26f3', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25329', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cdev.tomcat.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cannounce.apache.org%3E', 'https://github.com/apache/tomcat/commit/6d66e99ef85da93e4d2c2a536ca51aa3418bfaf4', 'http://www.openwall.com/lists/oss-security/2021/03/01/2', 'https://lists.apache.org/thread.html/r8a2ac0e476dbfc1e6440b09dcc782d444ad635d6da26f0284725a5dc@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf@%3Cusers.tomcat.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.debian.org/security/2021/dsa-4891', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/apache/tomcat/commit/6d66e99ef85da93e4d2c2a536ca51aa3418bfaf4'} | {'https://github.com/apache/tomcat/commit/6d66e99ef85da93e4d2c2a536ca51aa3418bfaf4'} |
GHSA | GHSA-8cxv-76p7-jxwr | Null-dereference in Tensorflow | ### Impact
The [implementation of `GetInitOp`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/cc/saved_model/loader_util.cc#L31-L61) is vulnerable to a crash caused by dereferencing a null pointer:
```cc
const auto& init_op_sig_it =
meta_graph_def.signature_def().find(kSavedModelInitOpSignatureKey);
if (init_op_sig_it != sig_def_map.end()) {
*init_op_name = init_op_sig_it->second.outputs()
.find(kSavedModelInitOpSignatureKey)
->second.name();
return Status::OK();
}
```
Here, we have a nested map and we assume that if the first `.find` succeeds then so would be the search in the internal map. However, the maps are built based on the `SavedModel` protobuf format and a malicious user can alter that on disk before loading to cause the second `.find` to return `nullptr`.
### Patches
We have patched the issue in GitHub commit [4f38b1ac8e42727e18a2f0bde06d3bee8e77b250](https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250).
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-23577'} | 2022-02-11T20:45:59Z | 2022-02-10T00:32:29Z | MODERATE | 6.5 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23577', 'https://github.com/advisories/GHSA-8cxv-76p7-jxwr', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/cc/saved_model/loader_util.cc#L31-L61', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8cxv-76p7-jxwr', 'https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250'} | null | {'https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250'} | {'https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250'} |
GHSA | GHSA-3pg8-c473-w6rr | Stored Cross-site Scripting in showdoc | ShowDoc is a tool for an IT team to share documents online. showdoc contains a stored cross-site scripting vulnerability in the File Library page when uploading a file in .ofd format in versions prior to 2.10.4. At this time, there is no known workaround. Users should update to version 2.10.4. | {'CVE-2022-0967'} | 2022-03-25T00:07:37Z | 2022-03-16T00:00:46Z | MODERATE | 6.9 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-0967', 'https://github.com/advisories/GHSA-3pg8-c473-w6rr', 'https://huntr.dev/bounties/9dea3c98-7609-480d-902d-149067bd1e2a', 'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | null | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} | {'https://github.com/star7th/showdoc/commit/3caa32334db0c277b84e993eaca2036f5d1dbef8'} |
GHSA | GHSA-rrqm-p222-8ph2 | Prototype Pollution in Dynamoose | ### Impact
In Dynamoose versions 2.0.0-2.6.0 there was a prototype pollution vulnerability in the internal utility method [`lib/utils/object/set.ts`](https://github.com/dynamoose/dynamoose/blob/master/lib/utils/object/set.ts). This method is used throughout the codebase for various operations throughout Dynamoose.
We have not seen any evidence of this vulnerability being exploited.
We do not believe this issue impacts v1.x.x since this method was added as part of the v2 rewrite. This vulnerability also impacts v2.x.x beta/alpha versions.
### Patches
v2.7.0 includes a patch for this vulnerability.
### Workarounds
We are unaware of any workarounds to patch this vulnerability other than upgrading to v2.7.0 or greater.
### References
- Patch commit hash: 324c62b4709204955931a187362f8999805b1d8e
### For more information
If you have any questions or comments about this advisory:
* [Contact me](https://charlie.fish/contact)
* [Read our Security Policy](https://github.com/dynamoose/dynamoose/blob/master/SECURITY.md)
### Credit
- GitHub CodeQL Code Scanning | {'CVE-2021-21304'} | 2021-08-23T22:30:49Z | 2021-02-08T17:44:01Z | MODERATE | 7.2 | {'CWE-1321', 'CWE-915'} | {'https://www.npmjs.com/package/dynamoose', 'https://github.com/dynamoose/dynamoose/releases/tag/v2.7.0', 'https://github.com/dynamoose/dynamoose/security/advisories/GHSA-rrqm-p222-8ph2', 'https://github.com/advisories/GHSA-rrqm-p222-8ph2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21304', 'https://github.com/dynamoose/dynamoose/commit/324c62b4709204955931a187362f8999805b1d8e'} | null | {'https://github.com/dynamoose/dynamoose/commit/324c62b4709204955931a187362f8999805b1d8e'} | {'https://github.com/dynamoose/dynamoose/commit/324c62b4709204955931a187362f8999805b1d8e'} |
GHSA | GHSA-6w39-qhmq-g8cp | CSRF vulnerability in Jenkins Publish Over FTP Plugin | A cross-site request forgery (CSRF) vulnerability in Jenkins Publish Over FTP Plugin 1.16 and earlier allows attackers to connect to an FTP server using attacker-specified credentials. | {'CVE-2022-29050'} | 2022-05-04T20:56:36Z | 2022-04-13T00:00:16Z | HIGH | 8.8 | {'CWE-352'} | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7', 'https://github.com/advisories/GHSA-6w39-qhmq-g8cp', 'https://www.jenkins.io/security/advisory/2022-04-12/#SECURITY-2321', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29050'} | null | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7'} | {'https://github.com/jenkinsci/publish-over-ftp-plugin/commit/b265201428557ab91304e06199ad38221efc23e7'} |
GHSA | GHSA-vx6v-xg64-pmr8 | Cross-site Scripting in django-helpdesk | django-helpdesk is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). | {'CVE-2021-3945'} | 2021-11-17T21:10:27Z | 2021-11-15T23:12:41Z | HIGH | 8.8 | {'CWE-79'} | {'https://github.com/django-helpdesk/django-helpdesk/commit/2c7065e0c4296e0c692fb4a7ee19c7357583af30', 'https://github.com/advisories/GHSA-vx6v-xg64-pmr8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3945', 'https://huntr.dev/bounties/745f483c-70ed-441f-ab2e-7ac1305439a4'} | null | {'https://github.com/django-helpdesk/django-helpdesk/commit/2c7065e0c4296e0c692fb4a7ee19c7357583af30'} | {'https://github.com/django-helpdesk/django-helpdesk/commit/2c7065e0c4296e0c692fb4a7ee19c7357583af30'} |
GHSA | GHSA-5j3g-jfq3-7jwx | Arbitrary JavaScript Execution in bassmaster | A vulnerability exists in bassmaster <= 1.5.1 that allows for an attacker to provide arbitrary JavaScript that is then executed server side via eval.
## Recommendation
Update to bassmaster version 1.5.2 or greater. | {'CVE-2014-7205'} | 2021-09-01T22:16:02Z | 2017-10-24T18:33:36Z | CRITICAL | 0 | {'CWE-94'} | {'http://www.securityfocus.com/bid/70180', 'https://nvd.nist.gov/vuln/detail/CVE-2014-7205', 'https://github.com/hapijs/bassmaster/commit/b751602d8cb7194ee62a61e085069679525138c4', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/96730', 'http://www.openwall.com/lists/oss-security/2014/09/30/10', 'https://www.npmjs.com/advisories/1', 'https://github.com/advisories/GHSA-5j3g-jfq3-7jwx', 'https://nodesecurity.io/advisories/bassmaster_js_injection', 'https://www.exploit-db.com/exploits/40689/'} | null | {'https://github.com/hapijs/bassmaster/commit/b751602d8cb7194ee62a61e085069679525138c4'} | {'https://github.com/hapijs/bassmaster/commit/b751602d8cb7194ee62a61e085069679525138c4'} |
GHSA | GHSA-gjm5-83cw-p3p2 | Prototype Pollution in extend2 | The package extend2 before 1.0.1 are vulnerable to Prototype Pollution via the extend function due to unsafe recursive merge. | {'CVE-2021-23568'} | 2022-01-12T22:59:13Z | 2022-01-12T22:59:13Z | HIGH | 7.3 | {'CWE-1321'} | {'https://github.com/eggjs/extend2/blob/master/index.js%23L50-L60', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23568', 'https://snyk.io/vuln/SNYK-JS-EXTEND2-2320315', 'https://github.com/advisories/GHSA-gjm5-83cw-p3p2', 'https://github.com/eggjs/extend2/pull/2', 'https://github.com/eggjs/extend2/commit/aa332a59116c8398976434b57ea477c6823054f8'} | null | {'https://github.com/eggjs/extend2/commit/aa332a59116c8398976434b57ea477c6823054f8'} | {'https://github.com/eggjs/extend2/commit/aa332a59116c8398976434b57ea477c6823054f8'} |
GHSA | GHSA-mg3m-f475-28hv | Path Traversal in @backstage/plugin-scaffolder-backend | ### Impact
A malicious actor with write access to a registered scaffolder template is able to manipulate the template in a way that writes files to arbitrary paths on the scaffolder-backend host instance.
This vulnerability can in some situation also be exploited through user input when executing a template, meaning you do not need write access to the templates. This method will not allow the attacker to control the contents of the injected file however, unless the template is also crafted in a specific way that gives control of the file contents.
### Patches
This vulnerability is fixed in version `0.15.14` of the `@backstage/plugin-scaffolder-backend`.
### Workarounds
This attack is mitigated by restricting access and requiring reviews when registering or modifying scaffolder templates.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [Backstage repository](https://github.com/backstage/backstage)
* Visit our chat, linked to in [Backstage README](https://github.com/backstage/backstage)
| {'CVE-2021-43783'} | 2021-12-01T18:28:51Z | 2021-12-01T18:28:51Z | HIGH | 8.5 | {'CWE-22'} | {'https://github.com/backstage/backstage/security/advisories/GHSA-mg3m-f475-28hv', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43783', 'https://github.com/advisories/GHSA-mg3m-f475-28hv', 'https://github.com/backstage/backstage/commit/f9352ab606367cd9efc6ff048915c70ed3013b7f'} | null | {'https://github.com/backstage/backstage/commit/f9352ab606367cd9efc6ff048915c70ed3013b7f'} | {'https://github.com/backstage/backstage/commit/f9352ab606367cd9efc6ff048915c70ed3013b7f'} |
GHSA | GHSA-r6g8-jmj9-g945 | Improper Restriction of Rendered UI Layers or Frames in yourls | yourls is vulnerable to Improper Restriction of Rendered UI Layers or Frames | {'CVE-2021-3734'} | 2021-09-02T18:52:22Z | 2021-08-30T16:22:16Z | MODERATE | 6.5 | {'CWE-352', 'CWE-1021'} | {'https://github.com/advisories/GHSA-r6g8-jmj9-g945', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3734', 'https://github.com/yourls/yourls/commit/0a70acdcfb5fcbc63dbc5750018d608288eba3fe', 'https://huntr.dev/bounties/dd2e2dbe-efe5-49ec-be11-7a7e7c41debd'} | null | {'https://github.com/yourls/yourls/commit/0a70acdcfb5fcbc63dbc5750018d608288eba3fe'} | {'https://github.com/yourls/yourls/commit/0a70acdcfb5fcbc63dbc5750018d608288eba3fe'} |
GHSA | GHSA-f9hv-mg5h-xcw9 | High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind | FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization. | {'CVE-2018-19360'} | 2021-06-10T23:47:42Z | 2019-01-04T19:06:57Z | CRITICAL | 9.8 | {'CWE-502'} | {'http://www.securityfocus.com/bid/107985', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19360', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b', 'https://www.debian.org/security/2019/dsa-4452', 'https://lists.apache.org/thread.html/c70da3cb6e3f03e0ad8013e38b6959419d866c4a7c80fdd34b73f25c@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8', '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://github.com/FasterXML/jackson-databind/issues/2186', '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://lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/37e1ed724a1b0e5d191d98c822c426670bdfde83804567131847d2a3@%3Cdevnull.infra.apache.org%3E', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://github.com/advisories/GHSA-f9hv-mg5h-xcw9', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://issues.apache.org/jira/browse/TINKERPOP-2121', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823'} | null | {'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'} | {'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'} |
GHSA | GHSA-qqv6-5w6p-3pgr | Moderate severity vulnerability that affects org.hswebframework.web:hsweb-commons | An issue was discovered in hsweb 3.0.4. It is a reflected XSS vulnerability due to the absence of type parameter checking in FlowableModelManagerController.java. | {'CVE-2018-20594'} | 2021-09-16T20:04:03Z | 2019-01-04T17:43:30Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/hs-web/hsweb-framework/issues/107', 'https://github.com/hs-web/hsweb-framework/commit/b72a2275ed21240296c6539bae1049c56abb542f', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20594', 'https://github.com/advisories/GHSA-qqv6-5w6p-3pgr'} | null | {'https://github.com/hs-web/hsweb-framework/commit/b72a2275ed21240296c6539bae1049c56abb542f'} | {'https://github.com/hs-web/hsweb-framework/commit/b72a2275ed21240296c6539bae1049c56abb542f'} |
GHSA | GHSA-4f99-p9c2-3j8x | Undefined behavior via `nullptr` reference binding in sparse matrix multiplication | ### Impact
The [code for sparse matrix multiplication](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/sparse_matmul_op.cc#L954-L1086) is vulnerable to undefined behavior via binding a reference to `nullptr`:
```python
import tensorflow as tf
tf.raw_ops.SparseMatMul(
a=[[1.0,1.0,1.0]],
b=[[],[],[]],
transpose_a=False,
transpose_b=False,
a_is_sparse=False,
b_is_sparse=True)
```
This occurs whenever the dimensions of `a` or `b` are 0 or less. In the case on one of these is 0, an empty output tensor should be allocated (to conserve the invariant that output tensors are always allocated when the operation is successful) but nothing should be written to it (that is, we should return early from the kernel implementation). Otherwise, attempts to write to this empty tensor would result in heap OOB access.
### Patches
We have patched the issue in GitHub commit [e6cf28c72ba2eb949ca950d834dd6d66bb01cfae](https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
| {'CVE-2021-41219'} | 2021-11-10T18:51:51Z | 2021-11-10T18:51:51Z | HIGH | 7.8 | {'CWE-824', 'CWE-125'} | {'https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4f99-p9c2-3j8x', 'https://github.com/advisories/GHSA-4f99-p9c2-3j8x', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41219'} | null | {'https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae'} | {'https://github.com/tensorflow/tensorflow/commit/e6cf28c72ba2eb949ca950d834dd6d66bb01cfae'} |
GHSA | GHSA-5pcx-vqjp-p34w | Cross-site Scripting in shuup | In Shuup, versions 1.6.0 through 2.10.8 are vulnerable to reflected Cross-Site Scripting (XSS) that allows execution of arbitrary javascript code on a victim browser. This vulnerability exists due to the error page contents not escaped. | {'CVE-2021-25963'} | 2021-10-08T21:30:20Z | 2021-10-04T20:11:03Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25963', 'https://github.com/advisories/GHSA-5pcx-vqjp-p34w', 'https://github.com/shuup/shuup/commit/75714c37e32796eb7cbb0d977af5bcaa26573588', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25963', 'https://github.com/shuup/shuup'} | null | {'https://github.com/shuup/shuup/commit/75714c37e32796eb7cbb0d977af5bcaa26573588'} | {'https://github.com/shuup/shuup/commit/75714c37e32796eb7cbb0d977af5bcaa26573588'} |
GHSA | GHSA-3rpf-5rqv-689q | PHP Code Injection by malicious function name in smarty | Template authors could inject php code by choosing a malicous {function} name. Sites that cannot fully trust template authors should update as soon as possible. Please upgrade to 3.1.39 or higher.
| {'CVE-2021-26120'} | 2022-05-03T03:01:58Z | 2021-02-26T19:53:24Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://github.com/smarty-php/smarty/blob/master/CHANGELOG.md', 'https://github.com/advisories/GHSA-3rpf-5rqv-689q', 'https://github.com/smarty-php/smarty/commit/165f1bd4d2eec328cfeaca517a725b46001de838', 'https://security.gentoo.org/glsa/202105-06', 'https://srcincite.io/blog/2021/02/18/smarty-template-engine-multiple-sandbox-escape-vulnerabilities.html', 'https://lists.debian.org/debian-lts-announce/2021/04/msg00014.html', 'https://lists.debian.org/debian-lts-announce/2021/04/msg00004.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26120', 'https://github.com/smarty-php/smarty/blob/master/CHANGELOG.md#3139---2021-02-17', 'https://github.com/smarty-php/smarty/security/advisories/GHSA-3rpf-5rqv-689q'} | null | {'https://github.com/smarty-php/smarty/commit/165f1bd4d2eec328cfeaca517a725b46001de838'} | {'https://github.com/smarty-php/smarty/commit/165f1bd4d2eec328cfeaca517a725b46001de838'} |
GHSA | GHSA-j823-4qch-3rgm | Deserialization of untrusted data in Jackson Databind | FasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.xalan.lib.sql.JNDIConnectionPool (aka apache/drill). | {'CVE-2020-14060'} | 2021-10-21T21:08:17Z | 2020-06-18T14:44:46Z | HIGH | 8.1 | {'CWE-502'} | {'https://github.com/FasterXML/jackson-databind/commit/d1c67a0396e84c08d0558fbb843b5bd1f26e1921', 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062', 'https://github.com/advisories/GHSA-j823-4qch-3rgm', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00001.html', 'https://security.netapp.com/advisory/ntap-20200702-0003/', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14060', 'https://snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-572314', 'https://github.com/FasterXML/jackson-databind/issues/2688', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/FasterXML/jackson-databind/commit/d1c67a0396e84c08d0558fbb843b5bd1f26e1921'} | {'https://github.com/FasterXML/jackson-databind/commit/d1c67a0396e84c08d0558fbb843b5bd1f26e1921'} |
GHSA | GHSA-cj92-c4fj-w9c5 | Moderate severity vulnerability that affects mail | Directory traversal vulnerability in lib/mail/network/delivery_methods/file_delivery.rb in the Mail gem before 2.4.4 for Ruby allows remote attackers to read arbitrary files via a .. (dot dot) in the to parameter. | {'CVE-2012-2139'} | 2021-09-09T19:22:48Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-22'} | {'http://secunia.com/advisories/48970', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080645.html', 'https://nvd.nist.gov/vuln/detail/CVE-2012-2139', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080747.html', 'https://github.com/advisories/GHSA-cj92-c4fj-w9c5', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080648.html', 'http://www.openwall.com/lists/oss-security/2012/04/25/8', 'https://bugzilla.redhat.com/show_bug.cgi?id=816352', 'https://github.com/mikel/mail/commit/29aca25218e4c82991400eb9b0c933626aefc98f', 'http://www.openwall.com/lists/oss-security/2012/04/26/1', 'https://bugzilla.novell.com/show_bug.cgi?id=759092'} | null | {'https://github.com/mikel/mail/commit/29aca25218e4c82991400eb9b0c933626aefc98f'} | {'https://github.com/mikel/mail/commit/29aca25218e4c82991400eb9b0c933626aefc98f'} |
GHSA | GHSA-hmr4-m2h5-33qx | SQL injection in Django | Django 1.11 before 1.11.28, 2.2 before 2.2.10, and 3.0 before 3.0.3 allows SQL Injection if untrusted data is used as a StringAgg delimiter (e.g., in Django applications that offer downloads of data as a series of rows with a user-specified column delimiter). By passing a suitably crafted delimiter to a contrib.postgres.aggregates.StringAgg instance, it was possible to break escaping and inject malicious SQL. | {'CVE-2020-7471'} | 2022-03-21T20:34:26Z | 2020-02-11T21:03:20Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136', 'https://security.netapp.com/advisory/ntap-20200221-0006/', 'https://www.djangoproject.com/weblog/2020/feb/03/security-releases/', 'https://www.openwall.com/lists/oss-security/2020/02/03/1', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4A2AP4T7RKPBCLTI2NNQG3T6MINDUUMZ/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7471', 'https://groups.google.com/forum/#!topic/django-announce/X45S86X5bZI', 'https://security.gentoo.org/glsa/202004-17', 'http://www.openwall.com/lists/oss-security/2020/02/03/1', 'https://usn.ubuntu.com/4264-1/', 'https://seclists.org/bugtraq/2020/Feb/30', 'https://www.debian.org/security/2020/dsa-4629', 'https://github.com/advisories/GHSA-hmr4-m2h5-33qx'} | null | {'https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136'} | {'https://github.com/django/django/commit/eb31d845323618d688ad429479c6dda973056136'} |
GHSA | GHSA-vp37-2f9p-3vr3 | Cross-site Scripting in OWASP AntiSamy | AntiSamy is a library for performing fast, configurable cleansing of HTML coming from untrusted sources. OWASP AntiSamy before 1.6.7 allows XSS via HTML tag smuggling on STYLE content with crafted input. The output serializer does not properly encode the supposed Cascading Style Sheets (CSS) content. NOTE: this issue exists because of an incomplete fix for CVE-2022-28367. | {'CVE-2022-29577'} | 2022-05-04T03:59:46Z | 2022-04-23T00:03:04Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-29577', 'https://github.com/advisories/GHSA-vp37-2f9p-3vr3', 'https://github.com/nahsra/antisamy/releases/tag/v1.6.7', 'https://github.com/nahsra/antisamy/commit/32e273507da0e964b58c50fd8a4c94c9d9363af0'} | null | {'https://github.com/nahsra/antisamy/commit/32e273507da0e964b58c50fd8a4c94c9d9363af0'} | {'https://github.com/nahsra/antisamy/commit/32e273507da0e964b58c50fd8a4c94c9d9363af0'} |
GHSA | GHSA-q5wr-fvpq-p67g | Integer Overflow in png-img | An integer overflow in the PngImg::InitStorage_() function of png-img before 3.1.0 leads to an under-allocation of heap memory and subsequently an exploitable heap-based buffer overflow when loading a crafted PNG file. | {'CVE-2020-28248'} | 2021-12-10T17:23:30Z | 2021-12-10T17:23:30Z | HIGH | 8.8 | {'CWE-787', 'CWE-190'} | {'https://github.com/gemini-testing/png-img', 'https://github.com/advisories/GHSA-q5wr-fvpq-p67g', 'https://securitylab.github.com/advisories/GHSL-2020-142-gemini-png-img', 'https://github.com/gemini-testing/png-img/commit/14ac462a32ca4b3b78f56502ac976d5b0222ce3d', 'https://github.com/gemini-testing/png-img/compare/v3.0.0...v3.1.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28248'} | null | {'https://github.com/gemini-testing/png-img/commit/14ac462a32ca4b3b78f56502ac976d5b0222ce3d'} | {'https://github.com/gemini-testing/png-img/commit/14ac462a32ca4b3b78f56502ac976d5b0222ce3d'} |
GHSA | GHSA-6cc5-2vg4-cc7m | Injection in Twisted | In Twisted before 19.2.1, twisted.web did not validate or sanitize URIs or HTTP methods, allowing an attacker to inject invalid characters such as CRLF. | {'CVE-2019-12387'} | 2021-04-23T20:35:36Z | 2019-06-10T18:05:06Z | MODERATE | 6.1 | {'CWE-74'} | {'http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00030.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2G5RPDQ4BNB336HL6WW5ZJ344MAWNN7N/', 'https://github.com/advisories/GHSA-6cc5-2vg4-cc7m', 'https://usn.ubuntu.com/4308-1/', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00042.html', 'https://github.com/twisted/twisted/commit/6c61fc4503ae39ab8ecee52d10f10ee2c371d7e2', 'https://twistedmatrix.com/pipermail/twisted-python/2019-June/032352.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12387', 'https://labs.twistedmatrix.com/2019/06/twisted-1921-released.html', 'https://usn.ubuntu.com/4308-2/'} | null | {'https://github.com/twisted/twisted/commit/6c61fc4503ae39ab8ecee52d10f10ee2c371d7e2'} | {'https://github.com/twisted/twisted/commit/6c61fc4503ae39ab8ecee52d10f10ee2c371d7e2'} |
GHSA | GHSA-ppq7-88c7-q879 | Cross-Site Request Forgery in PiranhaCMS | In PiranhaCMS, versions 4.0.0-alpha1 to 9.2.0 are vulnerable to cross-site request forgery (CSRF) when performing various actions supported by the management system, such as deleting a user, deleting a role, editing a post, deleting a media folder etc., when an ID is known. | {'CVE-2021-25976'} | 2021-11-17T23:42:40Z | 2021-11-17T23:42:40Z | HIGH | 8.1 | {'CWE-352'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25976', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25976', 'https://github.com/advisories/GHSA-ppq7-88c7-q879', 'https://github.com/PiranhaCMS/piranha.core/commit/e42abacdd0dd880ce9cf6607efcc24646ac82eda'} | null | {'https://github.com/PiranhaCMS/piranha.core/commit/e42abacdd0dd880ce9cf6607efcc24646ac82eda'} | {'https://github.com/PiranhaCMS/piranha.core/commit/e42abacdd0dd880ce9cf6607efcc24646ac82eda'} |
GHSA | GHSA-c676-mcw3-qg55 | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF) | firefly-iii is vulnerable to Cross-Site Request Forgery (CSRF) | {'CVE-2021-3730'} | 2021-08-27T12:48:30Z | 2021-08-25T14:50:08Z | MODERATE | 6.5 | {'CWE-352'} | {'https://huntr.dev/bounties/ea181323-51f8-46a2-a60f-6a401907feb7', 'https://github.com/firefly-iii/firefly-iii/commit/f80178b1b2b7864d17500a131d570c353c9a26f6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3730', 'https://github.com/advisories/GHSA-c676-mcw3-qg55'} | null | {'https://github.com/firefly-iii/firefly-iii/commit/f80178b1b2b7864d17500a131d570c353c9a26f6'} | {'https://github.com/firefly-iii/firefly-iii/commit/f80178b1b2b7864d17500a131d570c353c9a26f6'} |
GHSA | GHSA-vhhw-xjvf-wprr | Command Injection in @graphql-tools/git-loader | This affects the package @graphql-tools/git-loader before 6.2.6. The use of exec and execSync in packages/loaders/git/src/load-git.ts allows arbitrary command injection. | {'CVE-2021-23326'} | 2021-03-31T20:10:44Z | 2021-01-29T18:13:14Z | MODERATE | 5.5 | {'CWE-77'} | {'https://advisory.checkmarx.net/advisory/CX-2020-4300', 'https://snyk.io/vuln/SNYK-JS-GRAPHQLTOOLSGITLOADER-1062543', 'https://github.com/ardatan/graphql-tools/releases/tag/%40graphql-tools%2Fgit-loader%406.2.6', 'https://github.com/ardatan/graphql-tools/pull/2470', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23326', 'https://github.com/advisories/GHSA-vhhw-xjvf-wprr', 'https://github.com/ardatan/graphql-tools/commit/6a966beee8ca8b2f4adfe93318b96e4a5c501eac'} | null | {'https://github.com/ardatan/graphql-tools/commit/6a966beee8ca8b2f4adfe93318b96e4a5c501eac'} | {'https://github.com/ardatan/graphql-tools/commit/6a966beee8ca8b2f4adfe93318b96e4a5c501eac'} |
GHSA | GHSA-6gp3-h3jj-prx4 | Prototype pollution in class-transformer | class-transformer through 0.2.3 is vulnerable to Prototype Pollution. The 'classToPlainFromExist' function could be tricked into adding or modifying properties of 'Object.prototype' using a '__proto__' payload. | {'CVE-2020-7637'} | 2022-04-28T17:58:14Z | 2020-04-07T15:47:40Z | MODERATE | 5.3 | {'CWE-915'} | {'https://snyk.io/vuln/SNYK-JS-CLASSTRANSFORMER-564431', 'https://github.com/advisories/GHSA-6gp3-h3jj-prx4', 'https://github.com/typestack/class-transformer/blob/a650d9f490573443f62508bc063b857bcd5e2525/src/ClassTransformer.ts#L29-L31,', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7637', 'https://github.com/typestack/class-transformer/commit/8f04eb9db02de708f1a20f6f2d2bb309b2fed01e'} | null | {'https://github.com/typestack/class-transformer/commit/8f04eb9db02de708f1a20f6f2d2bb309b2fed01e'} | {'https://github.com/typestack/class-transformer/commit/8f04eb9db02de708f1a20f6f2d2bb309b2fed01e'} |
GHSA | GHSA-vc2p-r46x-m3vx | Argument injection in lettre | ### Impact
Affected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.
Depending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).
*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.
### Fix
The flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.
### References
* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)
* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247) | {'CVE-2020-28247'} | 2022-04-19T19:02:40Z | 2021-08-25T20:56:48Z | MODERATE | 5.3 | {'CWE-77'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0069.html', 'https://github.com/advisories/GHSA-vc2p-r46x-m3vx', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28247', 'https://github.com/RustSec/advisory-db/pull/478/files', 'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b', 'https://github.com/lettre/lettre/security/advisories/GHSA-vc2p-r46x-m3vx'} | null | {'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b'} | {'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b'} |
GHSA | GHSA-3pp3-77j6-8ph6 | Missing Authentication for Critical Function in Apache NiFi | In Apache NiFi 1.0.0 to 1.11.4, the NiFi download token (one-time password) mechanism used a fixed cache size and did not authenticate a request to create a download token, only when attempting to use the token to access the content. An unauthenticated user could repeatedly request download tokens, preventing legitimate users from requesting download tokens. | {'CVE-2020-9487'} | 2022-01-06T20:41:04Z | 2022-01-06T20:41:04Z | HIGH | 7.5 | {'CWE-306'} | {'https://nifi.apache.org/security#CVE-2020-9487', 'https://github.com/advisories/GHSA-3pp3-77j6-8ph6', 'https://github.com/apache/nifi/commit/01e42dfb3291c3a3549023edadafd2d8023f3042', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9487'} | null | {'https://github.com/apache/nifi/commit/01e42dfb3291c3a3549023edadafd2d8023f3042'} | {'https://github.com/apache/nifi/commit/01e42dfb3291c3a3549023edadafd2d8023f3042'} |
GHSA | GHSA-vcqg-3p29-xw73 | Integer overflow in Pillow | libImaging/TiffDecode.c in Pillow before 6.2.2 has a TIFF decoding integer overflow, related to realloc. | {'CVE-2020-5310'} | 2021-11-03T18:04:41Z | 2021-11-03T18:04:41Z | MODERATE | 8.8 | {'CWE-190'} | {'https://github.com/python-pillow/Pillow/commit/4e2def2539ec13e53a82e06c4b3daf00454100c4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5310', 'https://github.com/pypa/advisory-db/blob/7872b0a91b4d980f749e6d75a81f8cc1af32829f/vulns/pillow/PYSEC-2020-81.yaml', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MMU3WT2X64GS5WHDPKKC2WZA7UIIQ3A/', 'https://github.com/advisories/GHSA-vcqg-3p29-xw73', 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.2.html'} | null | {'https://github.com/python-pillow/Pillow/commit/4e2def2539ec13e53a82e06c4b3daf00454100c4'} | {'https://github.com/python-pillow/Pillow/commit/4e2def2539ec13e53a82e06c4b3daf00454100c4'} |
GHSA | GHSA-p5gm-fgfx-hr7h | Gadget chain attack in Nippy | A deserialization flaw is present in Taoensso Nippy before 2.14.2. In some circumstances, it is possible for an attacker to create a malicious payload that, when deserialized, will allow arbitrary code to be executed. This occurs because there is automatic use of the Java Serializable interface. | {'CVE-2020-24164'} | 2022-02-10T20:55:10Z | 2022-02-10T20:55:10Z | HIGH | 7.8 | {'CWE-502'} | {'https://github.com/ptaoussanis/nippy/commit/61fb009fdde2994140f2da2e495ba8af3a873eb2', 'https://github.com/ptaoussanis/nippy/issues/130', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24164', 'https://github.com/advisories/GHSA-p5gm-fgfx-hr7h'} | null | {'https://github.com/ptaoussanis/nippy/commit/61fb009fdde2994140f2da2e495ba8af3a873eb2'} | {'https://github.com/ptaoussanis/nippy/commit/61fb009fdde2994140f2da2e495ba8af3a873eb2'} |
GHSA | GHSA-69v6-xc2j-r2jf | Shallow copy bug in geth | ### Impact
This is a Consensus vulnerability, which can be used to cause a chain-split where vulnerable nodes reject the canonical chain.
Geth’s pre-compiled `dataCopy` (at `0x00...04`) contract did a shallow copy on invocation. An attacker could deploy a contract that
- writes `X` to an EVM memory region `R`,
- calls `0x00..04` with `R` as an argument,
- overwrites `R` to `Y`,
- and finally invokes the `RETURNDATACOPY` opcode.
When this contract is invoked, a consensus-compliant node would push `X` on the EVM stack, whereas Geth would push `Y`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org) | {'CVE-2020-26241'} | 2022-04-19T19:02:40Z | 2021-06-29T21:13:01Z | MODERATE | 6.5 | {'CWE-682'} | {'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-69v6-xc2j-r2jf', 'https://blog.ethereum.org/2020/11/12/geth_security_release/', 'https://github.com/advisories/GHSA-69v6-xc2j-r2jf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26241', 'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785'} | null | {'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785'} | {'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785'} |
GHSA | GHSA-vg44-fw64-cpjx | Incorrect Account Used for Signing | ### Impact
Anybody using this library to sign with a BIP44 account other than the first account may be affected. If a user is signing with the first account (i.e. the account at index `0`), or with the legacy MEW/MyCrypto HD path, they are not affected.
The vulnerability impacts cases where the user signs a personal message or transaction without first adding the account. This includes cases where the user has already added the account in a previous session (i.e. they added the account, reset the application, then signed something). The serialization/deserialization process does restore a previously added account, but it doesn't restore the index instructing the keyring to use that account for signing. As a result, after serializing then deserializing the keyring state, the account at index `0` is always used for signing even if it isn't the current account.
### Patches
This has been patched ([#14](https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/14)) in version >=0.2.1 of [`eth-ledger-bridge-keyring`](https://www.npmjs.com/package/eth-ledger-bridge-keyring), and in version >=0.2.2 of [`@metamask/eth-ledger-bridge-keyring`](https://www.npmjs.com/package/@metamask/eth-ledger-bridge-keyring). Users are encouraged to migrate to the new package name.
### Workarounds
To work around this problem without updating, you should remove then re-add the account before use. As long as the account was added during the lifetime of that process, signing with that account should work correctly.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [MetaMask/eth-ledger-bridge-keyring on GitHub](https://github.com/MetaMask/eth-ledger-bridge-keyring)
* Email the MetaMask team at [hello@metamask.io](mailto:hello@metamask.io) | null | 2021-08-23T14:40:06Z | 2020-03-24T15:08:59Z | HIGH | 7.5 | {'CWE-287'} | {'https://github.com/MetaMask/eth-ledger-bridge-keyring/pull/14', 'https://snyk.io/vuln/SNYK-JS-ETHLEDGERBRIDGEKEYRING-561121', 'https://www.npmjs.com/advisories/1497', 'https://www.npmjs.com/advisories/1498', 'https://github.com/advisories/GHSA-vg44-fw64-cpjx', 'https://github.com/MetaMask/eth-ledger-bridge-keyring/commit/f32e529d13a53e55f558d903534d631846dc26ce', 'https://github.com/MetaMask/eth-ledger-bridge-keyring/security/advisories/GHSA-vg44-fw64-cpjx'} | null | {'https://github.com/MetaMask/eth-ledger-bridge-keyring/commit/f32e529d13a53e55f558d903534d631846dc26ce'} | {'https://github.com/MetaMask/eth-ledger-bridge-keyring/commit/f32e529d13a53e55f558d903534d631846dc26ce'} |
GHSA | GHSA-88xq-w8cq-xfg7 | Invalid drop of partially-initialized instances in the pooling instance allocator for modules with defined `externref` globals | ### Impact
There exists a bug in the pooling instance allocator in Wasmtime's runtime where a failure to instantiate an instance for a module that defines an `externref` global will result in an invalid drop of a `VMExternRef` via an uninitialized pointer.
As instance slots may be reused between consecutive instantiations, the value of the uninitialized pointer may be from a previous instantiation and therefore under the control of an attacker via a module's initial values for its globals. If the attacker can somehow determine an address under their control inside the mapped memory representing the instance pool, it is possible to trick the runtime to call `drop_in_place` on a trait object under the attacker's control and therefore cause remote code execution.
Exploiting the bug to cause remote code execution would be very difficult as attackers cannot determine the addresses of globals from code executing within the WebAssembly VM and the memory space for the instance pool cannot be statically determined. Operating system mitigations, such as [address space layout randomization](https://en.wikipedia.org/wiki/Address_space_layout_randomization), would additionally increase the difficulty for attackers to determine useful executable code to target with an exploit. It is also very unlikely that attackers will be able to directly influence the conditions that trigger the bug as described below.
When the conditions to trigger the bug are met, however, it is much easier to exploit this bug to cause a denial of service by crashing the host with an invalid memory read.
The following engine configuration (via [Config](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Config.html)) is required to be impacted by this bug:
* support for the reference types proposal must be enabled (this is the default for `Config`).
* a pooling allocation strategy must be configured via [Config::allocation_strategy](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Config.html#method.allocation_strategy), which is **not the default allocation strategy**.
A module must be instantiated with **all the following characteristics**:
* The module defines at least one table or memory.
* The module defines at least one `externref` global.
During instantiation, **one of the following** must occur to cause the instantiation to fail:
* a call to `mprotect` or `VirtualAlloc` fails (e.g. out-of-memory conditions).
* a resource limiter was configured in the associated `Store` (via [Store::limiter](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Store.html#method.limiter) or [Store::limiter_async](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Store.html#method.limiter_async)) and the limiter returns `false` from the initial call to `memory_growing` or `table_growing`. **Stores do not have a resource limiter set by default**.
This results in a partially-initialized instance being dropped and that attempts to drop the uninitialized `VMExternRef` representing the defined `externref` global.
We have reason to believe that the effective impact of this bug is relatively small because the usage of `externref` is still uncommon and without a resource limiter configured on the `Store`, which is not the default configuration, it is only possible to trigger the bug from an error returned by `mprotect` or `VirtualAlloc`.
Note that on Linux with the `uffd` feature enabled, it is only possible to trigger the bug from a resource limiter as the call to `mprotect` is skipped; if no resource limiter is used, then this configuration is not vulnerable.
### Patches
The bug has been fixed in 0.34.1 and 0.33.1; users are encouraged to upgrade as soon as possible.
### Workarounds
If it is not possible to upgrade to 0.34.1 or 0.33.1 of the `wasmtime` crate, it is recommend that support for the reference types proposal be disabled by passing `false` to [Config::wasm_reference_types](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_reference_types).
Doing so will prevent modules that use `externref` from being loaded entirely.
### 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-2022-23636'} | 2022-04-19T19:03:23Z | 2022-02-16T22:35:03Z | MODERATE | 5.1 | {'CWE-824'} | {'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-88xq-w8cq-xfg7', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23636', 'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a', 'https://github.com/advisories/GHSA-88xq-w8cq-xfg7'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a'} | {'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a'} |
GHSA | GHSA-prfq-f66g-43mp | Information disclosure through error object in auth0.js | ## Overview
Between versions 8.0.0 and 9.13.1(inclusive), in the case of an (authentication) error, the error object returned by the library contains the original request of the user, which may include the plaintext password the user entered.
If the error object is exposed or logged without modification, the application risks password exposure.
## Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using Auth0.js version between 8.0.0 and 9.13.1(inclusive).
- You store or display error objects without filtering.
## How to fix that?
Developers should upgrade auth0.js to version 9.13.2 or later where user inputted passwords are masked in errors. If upgrading is not possible, a temporary fix may include not storing the error object or displaying it publicly without modification.
## Will this update impact my users?
This fix patches the Auth0.js and may require changes in application code due to password no longer available in error object, but it will not impact your users, their current state, or any existing sessions. | {'CVE-2020-5263'} | 2021-01-08T20:23:17Z | 2020-04-10T18:19:10Z | HIGH | 5.5 | {'CWE-522'} | {'https://github.com/advisories/GHSA-prfq-f66g-43mp', 'https://github.com/auth0/auth0.js/security/advisories/GHSA-prfq-f66g-43mp', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5263', 'https://github.com/auth0/auth0.js/commit/355ca749b229fb93142f0b3978399b248d710828'} | null | {'https://github.com/auth0/auth0.js/commit/355ca749b229fb93142f0b3978399b248d710828'} | {'https://github.com/auth0/auth0.js/commit/355ca749b229fb93142f0b3978399b248d710828'} |
GHSA | GHSA-m298-fh5c-jc66 | Object injection in PHPMailer/PHPMailer | ### Impact
This is a reintroduction of an earlier issue (CVE-2018-19296) by an unrelated bug fix in PHPMailer 6.1.8. An external file may be unexpectedly executable if it is used as a path to an attachment file via PHP's support for `.phar` files`. Exploitation requires that an attacker is able to provide an unfiltered path to a file to attach, or to trick calling code into generating one. See [this article](https://knasmueller.net/5-answers-about-php-phar-exploitation) for more info.
### Patches
This issue was patched in the PHPMailer 6.4.1 release. This release also implements stricter filtering for attachment paths; paths that look like *any* kind of URL are rejected.
### Workarounds
Validate paths to loaded files using the same pattern as used in [`isPermittedPath()`](https://github.com/PHPMailer/PHPMailer/blob/master/src/PHPMailer.php#L1815) before using them in *any* PHP file function, such as `file_exists`. This method can't be used directly because it is protected, but you can implement the same thing in calling code. Note that this should be applied to *all* user-supplied paths passed into such functions; it's not a problem specific to PHPMailer.
### Credit
This issue was found by Fariskhi Vidyan, reported and managed via Tidelift. | {'CVE-2020-36326'} | 2021-05-13T15:11:01Z | 2021-05-04T17:42:13Z | CRITICAL | 9.8 | {'CWE-502', 'CWE-641'} | {'https://github.com/advisories/GHSA-m298-fh5c-jc66', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36326', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3B5WDPGUFNPG4NAZ6G4BZX43BKLAVA5B/', 'https://github.com/PHPMailer/PHPMailer/security/advisories/GHSA-m298-fh5c-jc66', 'https://github.com/PHPMailer/PHPMailer/commit/e2e07a355ee8ff36aba21d0242c5950c56e4c6f9', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KPU66INRFY5BQ3ESVPRUXJR4DXQAFJVT/'} | null | {'https://github.com/PHPMailer/PHPMailer/commit/e2e07a355ee8ff36aba21d0242c5950c56e4c6f9'} | {'https://github.com/PHPMailer/PHPMailer/commit/e2e07a355ee8ff36aba21d0242c5950c56e4c6f9'} |
GHSA | GHSA-h6gg-fvf5-qgwf | Data races in generator | The `Generator` type is an iterable which uses a generator function that yields
values. In affected versions of the crate, the provided function yielding values
had no `Send` bounds despite the `Generator` itself implementing `Send`.
The generator function lacking a `Send` bound means that types that are
dangerous to send across threads such as `Rc` could be sent as part of a
generator, potentially leading to data races.
This flaw was fixed in commit [`f7d120a3b`](https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0)
by enforcing that the generator function be bound by `Send`.
| null | 2021-08-25T20:55:41Z | 2021-08-25T20:55:41Z | MODERATE | 0 | {'CWE-362'} | {'https://github.com/advisories/GHSA-h6gg-fvf5-qgwf', 'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0', 'https://rustsec.org/advisories/RUSTSEC-2020-0151.html', 'https://github.com/Xudong-Huang/generator-rs/issues/27'} | null | {'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0'} | {'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0'} |
GHSA | GHSA-ppj4-34rq-v8j9 | regular expression denial of service in gjson | GJSON is a Go package that provides a fast and simple way to get values from a json document. GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack. | {'CVE-2021-42836'} | 2022-05-05T13:49:18Z | 2021-10-25T19:43:15Z | HIGH | 7.5 | {'CWE-400', 'CWE-697', 'CWE-1333'} | {'https://github.com/advisories/GHSA-ppj4-34rq-v8j9', 'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944', 'https://github.com/tidwall/gjson/issues/236', 'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96', 'https://github.com/tidwall/gjson/issues/237', 'https://github.com/tidwall/gjson/compare/v1.9.2...v1.9.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42836'} | null | {'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944', 'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96'} | {'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96', 'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944'} |
GHSA | GHSA-hxp5-8pgq-mgv9 | Missing Authentication for Critical Function in Apache Calcite | "HttpUtils#getURLConnection method disables explicitly hostname verification for HTTPS connections making clients vulnerable to man-in-the-middle attacks. Calcite uses this method internally to connect with Druid and Splunk so information leakage may happen when using the respective Calcite adapters. The method itself is in a utility class so people may use it to create vulnerable HTTPS connections for other applications. From Apache Calcite 1.26 onwards, the hostname verification will be performed using the default JVM truststore." | {'CVE-2020-13955'} | 2021-08-02T15:26:07Z | 2021-04-22T16:14:14Z | MODERATE | 5.9 | {'CWE-295'} | {'https://github.com/advisories/GHSA-hxp5-8pgq-mgv9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13955', 'https://lists.apache.org/thread.html/r0b0fbe2038388175951ce1028182d980f9e9a7328be13d52dab70bb3%40%3Cdev.calcite.apache.org%3E', 'https://issues.apache.org/jira/browse/CALCITE-4298', 'https://github.com/apache/calcite/commit/43eeafcbac29d02c72bd520c003cdfc571de2d15'} | null | {'https://github.com/apache/calcite/commit/43eeafcbac29d02c72bd520c003cdfc571de2d15'} | {'https://github.com/apache/calcite/commit/43eeafcbac29d02c72bd520c003cdfc571de2d15'} |
GHSA | GHSA-x4jg-mjrx-434g | Improper Verification of Cryptographic Signature in node-forge | ### Impact
RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a `DigestInfo` ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used.
### Patches
The issue has been addressed in `node-forge` `1.3.0`.
### References
For more information, please see
["Bleichenbacher's RSA signature forgery based on implementation error"](https://mailarchive.ietf.org/arch/msg/openpgp/5rnE9ZRN1AokBVj3VqblGlP63QE/)
by Hal Finney.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [forge](https://github.com/digitalbazaar/forge)
* Email us at [example email address](mailto:security@digitalbazaar.com) | {'CVE-2022-24772'} | 2022-03-30T20:07:57Z | 2022-03-18T23:10:28Z | HIGH | 7.5 | {'CWE-347'} | {'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1', 'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24772', 'https://github.com/digitalbazaar/forge/security/advisories/GHSA-x4jg-mjrx-434g', 'https://github.com/advisories/GHSA-x4jg-mjrx-434g'} | null | {'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1', 'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2'} | {'https://github.com/digitalbazaar/forge/commit/bb822c02df0b61211836472e29b9790cc541cdb2', 'https://github.com/digitalbazaar/forge/commit/3f0b49a0573ef1bb7af7f5673c0cfebf00424df1'} |
GHSA | GHSA-rrc9-gqf8-8rwg | Prototype Pollution via file load in aws-sdk and @aws-sdk/shared-ini-file-loader | This affects the package @aws-sdk/shared-ini-file-loader before 1.0.0-rc.9; the package aws-sdk before 2.814.0. If an attacker submits a malicious INI file to an application that parses it with loadSharedConfigFiles , they will pollute the prototype on the application. This can be exploited further depending on the context. | {'CVE-2020-28472'} | 2021-11-16T21:26:43Z | 2021-11-16T21:26:43Z | HIGH | 7.3 | {'CWE-400'} | {'https://github.com/aws/aws-sdk-js-v3/commit/a209082dff913939672bb069964b33aa4c5409a9', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1059425', 'https://snyk.io/vuln/SNYK-JS-AWSSDKSHAREDINIFILELOADER-1049304', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28472', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-1059426', 'https://github.com/advisories/GHSA-rrc9-gqf8-8rwg', 'https://github.com/aws/aws-sdk-js/pull/3585/commits/7d72aff2a941173733fcb6741b104cd83d3bc611', 'https://snyk.io/vuln/SNYK-JS-AWSSDK-1059424'} | null | {'https://github.com/aws/aws-sdk-js/pull/3585/commits/7d72aff2a941173733fcb6741b104cd83d3bc611', 'https://github.com/aws/aws-sdk-js-v3/commit/a209082dff913939672bb069964b33aa4c5409a9'} | {'https://github.com/aws/aws-sdk-js/pull/3585/commits/7d72aff2a941173733fcb6741b104cd83d3bc611', 'https://github.com/aws/aws-sdk-js-v3/commit/a209082dff913939672bb069964b33aa4c5409a9'} |
GHSA | GHSA-884w-698f-927f | Arbitrary File Write via Archive Extraction in unzipper | Versions of `unzipper` before 0.8.13 are vulnerable to arbitrary file write when used to extract a specifically crafted archive that contains path traversal filenames (`../../file.txt` for example).
## Recommendation
Update to version 0.3.18 or later. | {'CVE-2018-1002203'} | 2021-01-08T19:11:25Z | 2018-07-27T17:06:50Z | HIGH | 0 | {'CWE-22'} | {'https://github.com/ZJONSSON/node-unzipper/commit/2220ddd5b58f6252069a4f99f9475441ad0b50cd', 'https://hackerone.com/reports/362119', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1002203', 'https://snyk.io/vuln/npm:unzipper:20180415', 'https://www.npmjs.com/advisories/680', 'https://github.com/snyk/zip-slip-vulnerability', 'https://github.com/ZJONSSON/node-unzipper/pull/59', 'https://github.com/advisories/GHSA-884w-698f-927f', 'https://snyk.io/research/zip-slip-vulnerability'} | null | {'https://github.com/ZJONSSON/node-unzipper/commit/2220ddd5b58f6252069a4f99f9475441ad0b50cd'} | {'https://github.com/ZJONSSON/node-unzipper/commit/2220ddd5b58f6252069a4f99f9475441ad0b50cd'} |
GHSA | GHSA-28r6-jm5h-mrgg | Access control bypass in Beego | An issue was discovered in the route lookup process in beego through 2.0.1, allows attackers to bypass access control. | {'CVE-2021-30080'} | 2022-04-12T21:53:25Z | 2022-04-06T00:01:30Z | HIGH | 0 | null | {'https://nvd.nist.gov/vuln/detail/CVE-2021-30080', 'https://github.com/advisories/GHSA-28r6-jm5h-mrgg', 'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519'} | null | {'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519'} | {'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519'} |
GHSA | GHSA-9jcx-pr2f-qvq5 | Denial of Service (DoS) | An issue was discovered in setTA in scan_rr.go in the Miek Gieben DNS library before 1.0.10 for Go. A dns.ParseZone() parsing error causes a segmentation violation, leading to denial of service. | {'CVE-2018-17419'} | 2021-05-18T18:34:25Z | 2021-05-18T18:34:25Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d', 'https://nvd.nist.gov/vuln/detail/CVE-2018-17419', 'https://github.com/advisories/GHSA-9jcx-pr2f-qvq5', 'https://github.com/miekg/dns/issues/742'} | null | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d'} | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d'} |
GHSA | GHSA-j7c3-96rf-jrrp | Critical vulnerability in log4j may affect generated PEAR projects | ### Impact
UIMA PEAR projects that have been generated with the `de.averbis.textanalysis:pear-archetype ` version `2.0.0` have a maven dependency with scope `test` to` log4j 2.8.2` and might be affected by CVE-2021-44228.
### Patches
- The issue has been resolved in `de.averbis.textanalysis:pear-archetype ` version `2.0.1`. Please make sure to use `de.averbis.textanalysis:pear-archetype ` version >= `2.0.1` for generating new PEAR projects.
- Existing maven PEAR projects can be patched by manually upgrading to `log4j` >= `2.16.0` in `pom.xml`.
### References
https://www.lunasec.io/docs/blog/log4j-zero-day/
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/averbis/pear-archetype/issues
| null | 2021-12-16T21:01:51Z | 2021-12-16T21:01:51Z | CRITICAL | 0 | null | {'https://github.com/averbis/pear-archetype/commit/6815f5981c836ab8c345a6ff54f29e9f4b67f7eb', 'https://github.com/advisories/GHSA-j7c3-96rf-jrrp', 'https://github.com/averbis/pear-archetype/security/advisories/GHSA-j7c3-96rf-jrrp'} | null | {'https://github.com/averbis/pear-archetype/commit/6815f5981c836ab8c345a6ff54f29e9f4b67f7eb'} | {'https://github.com/averbis/pear-archetype/commit/6815f5981c836ab8c345a6ff54f29e9f4b67f7eb'} |
GHSA | GHSA-2wc6-2rcj-8v76 | scalarmult() vulnerable to degenerate public keys | The `scalarmult()` function included in previous versions of this crate
accepted all-zero public keys, for which the resulting Diffie-Hellman shared
secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them
if they are used.
| {'CVE-2017-1000168'} | 2021-08-25T21:00:41Z | 2021-08-25T21:00:41Z | MODERATE | 6.5 | {'CWE-1240'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-1000168', 'https://rustsec.org/advisories/RUSTSEC-2017-0001.html', 'https://github.com/advisories/GHSA-2wc6-2rcj-8v76', 'https://github.com/dnaq/sodiumoxide/issues/154', 'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'} | null | {'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'} | {'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'} |
GHSA | GHSA-hgch-jjmr-gp7w | Sandbox Breakout / Arbitrary Code Execution in safer-eval | Versions of `safer-eval` before 1.3.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
## Recommendation
Upgrade to version 1.3.2. | {'CVE-2019-10760'} | 2021-07-27T22:20:29Z | 2019-10-17T18:27:30Z | CRITICAL | 9.9 | {'CWE-94'} | {'https://github.com/commenthol/safer-eval/commit/1c29f6a6e304fb650c05056e217e457a0d2cc3c5', 'https://github.com/advisories/GHSA-hgch-jjmr-gp7w', 'https://snyk.io/vuln/SNYK-JS-SAFEREVAL-473029', 'https://www.npmjs.com/advisories/787', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10760'} | null | {'https://github.com/commenthol/safer-eval/commit/1c29f6a6e304fb650c05056e217e457a0d2cc3c5'} | {'https://github.com/commenthol/safer-eval/commit/1c29f6a6e304fb650c05056e217e457a0d2cc3c5'} |
GHSA | GHSA-84mw-34w6-2q43 | Null pointer dereference via invalid Ragged Tensors | ### Impact
Calling `tf.raw_ops.RaggedTensorToVariant` with arguments specifying an invalid ragged tensor results in a null pointer dereference:
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)
filter_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32)
tf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 56, 56, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 23, 1])
```
```python
import tensorflow as tf
input_tensor = tf.constant([], shape=[2, 2, 2, 2, 0], dtype=tf.float32)
filter_tensor = tf.constant([], shape=[0, 0, 2, 6, 2], dtype=tf.float32)
tf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 39, 34, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1])
```
The implementation of [`RaggedTensorToVariant` operations](https://github.com/tensorflow/tensorflow/blob/904b3926ed1c6c70380d5313d282d248a776baa1/tensorflow/core/kernels/ragged_tensor_to_variant_op.cc#L39-L40) does not validate that the ragged tensor argument is non-empty:
```cc
int ragged_rank = batched_ragged.ragged_rank();
auto batched_splits_top_vec = batched_ragged.splits(0).vec<SPLIT_TYPE>();
```
Since `batched_ragged` contains no elements, `batched_ragged.splits` is a null vector, thus `batched_ragged.splits(0)` will result in dereferencing `nullptr`.
### Patches
We have patched the issue in GitHub commit [b055b9c474cd376259dde8779908f9eeaf097d93](https://github.com/tensorflow/tensorflow/commit/b055b9c474cd376259dde8779908f9eeaf097d93).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team. | {'CVE-2021-29516'} | 2021-05-21T14:20:58Z | 2021-05-21T14:20:58Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/tensorflow/tensorflow/commit/b055b9c474cd376259dde8779908f9eeaf097d93', 'https://github.com/advisories/GHSA-84mw-34w6-2q43', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-84mw-34w6-2q43', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29516'} | null | {'https://github.com/tensorflow/tensorflow/commit/b055b9c474cd376259dde8779908f9eeaf097d93'} | {'https://github.com/tensorflow/tensorflow/commit/b055b9c474cd376259dde8779908f9eeaf097d93'} |
GHSA | GHSA-v26w-gcxh-v4r7 | Prototype polluation in just-safe-set | Prototype pollution vulnerability in ‘just-safe-set’ versions 1.0.0 through 2.2.1 allows an attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2021-25952'} | 2021-12-10T18:50:40Z | 2021-12-10T18:50:40Z | CRITICAL | 9.8 | {'CWE-1321', 'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25952', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25952', 'https://github.com/advisories/GHSA-v26w-gcxh-v4r7', 'https://github.com/angus-c/just/commit/dd57a476f4bb9d78c6f60741898dc04c71d2eb53', 'https://github.com/angus-c/just/pull/267'} | null | {'https://github.com/angus-c/just/commit/dd57a476f4bb9d78c6f60741898dc04c71d2eb53'} | {'https://github.com/angus-c/just/commit/dd57a476f4bb9d78c6f60741898dc04c71d2eb53'} |
GHSA | GHSA-x44x-r84w-8v67 | Lack of URL normalization may lead to authorization bypass when URL access rules are used | ### Impact
When access rules are used inside a protected host, some URL encodings may bypass filtering system.
### Patches
Version 0.5.2 includes a patch that fixes the vulnerability
### Workarounds
No way for users to fix or remediate the vulnerability without upgrading
### References
https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repository](https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/issues) or [LemonLDAP::NG GitLab](https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues)
* Email us at [lemonldap-ng-users@ow2.org](mailto:lemonldap-ng-users@ow2.org) | {'CVE-2020-24660'} | 2021-10-04T21:15:53Z | 2020-09-09T18:45:55Z | MODERATE | 6.5 | {'CWE-287'} | {'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/security/advisories/GHSA-x44x-r84w-8v67', 'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/releases/tag/0.5.2', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24660', 'https://github.com/advisories/GHSA-x44x-r84w-8v67', 'https://snyk.io/vuln/SNYK-JS-NODELEMONLDAPNGHANDLER-655999', 'https://gitlab.ow2.org/lemonldap-ng/lemonldap-ng/-/issues/2290', 'https://www.debian.org/security/2020/dsa-4762', 'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/commit/136aa83ed431462fa42ce17b7f9b24e056de06be', 'https://www.npmjs.com/package/lemonldap-ng-handler'} | null | {'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/commit/136aa83ed431462fa42ce17b7f9b24e056de06be'} | {'https://github.com/LemonLDAPNG/node-lemonldap-ng-handler/commit/136aa83ed431462fa42ce17b7f9b24e056de06be'} |
GHSA | GHSA-j6p2-cx3w-6jcp | Cross-Site Scripting in backbone | Affected versions of `backbone` are vulnerable to cross-site scripting when users are allowed to supply input to the `Model#Escape` function, and the output is then written to the DOM.
The vulnerability occurs as a result of the regular expression used to encode metacharacters failing to take HTML Entities such as `<` into account.
## Recommendation
Update to version 0.5.0 or later. | {'CVE-2016-10537'} | 2021-01-08T18:36:31Z | 2019-02-18T23:39:55Z | HIGH | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/108', 'https://github.com/advisories/GHSA-j6p2-cx3w-6jcp', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10537', 'https://github.com/jashkenas/backbone/commit/0cdc525961d3fa98e810ffae6bcc8e3838e36d93', 'https://github.com/jashkenas/backbone/compare/0.3.3...0.5.0#diff-0d56d0d310de7ff18b3cef9c2f8f75dcL1008', 'https://nodesecurity.io/advisories/108', 'https://backbonejs.org/#changelog'} | null | {'https://github.com/jashkenas/backbone/commit/0cdc525961d3fa98e810ffae6bcc8e3838e36d93'} | {'https://github.com/jashkenas/backbone/commit/0cdc525961d3fa98e810ffae6bcc8e3838e36d93'} |
GHSA | GHSA-8cv5-p934-3hwp | Denial of service in fast-csv | ### Impact
Possible ReDoS (Regular Expression Denial of Service) when using `ignoreEmpty` option when parsing.
### Patches
This has been patched in `v4.3.6`
### Workarounds
You will only be affected by this if you use the `ignoreEmpty` parsing option. If you do use this option it is recommended that you upgrade to the latest version `v4.3.6`
### References
This vulnerability was found using a [CodeQL](https://securitylab.github.com/tools/codeql) query which identified `EMPTY_ROW_REGEXP` regular expression as vulnerable.
[Link to query run](https://lgtm.com/query/8609731774537641779/).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [fast-csv](https://github.com/C2FO/fast-csv) | {'CVE-2020-26256'} | 2021-10-08T20:36:37Z | 2020-12-08T21:42:53Z | LOW | 5.7 | {'CWE-400'} | {'https://www.npmjs.com/advisories/1587', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26256', 'https://lgtm.com/query/8609731774537641779/', 'https://www.npmjs.com/package/fast-csv', 'https://www.npmjs.com/advisories/1588', 'https://github.com/C2FO/fast-csv/commit/4bbd39f26a8cd7382151ab4f5fb102234b2f829e', 'https://github.com/C2FO/fast-csv/security/advisories/GHSA-8cv5-p934-3hwp', 'https://github.com/C2FO/fast-csv/issues/540', 'https://www.npmjs.com/package/@fast-csv/parse', 'https://github.com/advisories/GHSA-8cv5-p934-3hwp'} | null | {'https://github.com/C2FO/fast-csv/commit/4bbd39f26a8cd7382151ab4f5fb102234b2f829e'} | {'https://github.com/C2FO/fast-csv/commit/4bbd39f26a8cd7382151ab4f5fb102234b2f829e'} |
GHSA | GHSA-4v2w-h9jm-mqjg | Prototype Pollution in systeminformation | ### Impact
command injection vulnerability by prototype pollution
### Patches
Problem was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. Please upgrade to version >= 4.30.2
### Workarounds
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()
### 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-26245'} | 2021-01-07T22:40:04Z | 2020-11-27T16:07:15Z | MODERATE | 8.1 | {'CWE-471', 'CWE-78'} | {'https://github.com/sebhildebrandt/systeminformation/commit/8113ff0e87b2f422a5756c48f1057575e73af016', 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-4v2w-h9jm-mqjg', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26245', 'https://github.com/advisories/GHSA-4v2w-h9jm-mqjg'} | null | {'https://github.com/sebhildebrandt/systeminformation/commit/8113ff0e87b2f422a5756c48f1057575e73af016'} | {'https://github.com/sebhildebrandt/systeminformation/commit/8113ff0e87b2f422a5756c48f1057575e73af016'} |
GHSA | GHSA-68w8-qjq3-2gfm | Path Traversal in Django | Django before 2.2.24, 3.x before 3.1.12, and 3.2.x before 3.2.4 has a potential directory traversal via django.contrib.admindocs. Staff members could use the TemplateDetailView view to check the existence of arbitrary files. Additionally, if (and only if) the default admindocs templates have been customized by application developers to also show file contents, then not only the existence but also the file contents would have been exposed. In other words, there is directory traversal outside of the template root directories. | {'CVE-2021-33203'} | 2022-02-14T22:19:23Z | 2021-06-10T17:21:00Z | MODERATE | 4.9 | {'CWE-22'} | {'https://www.djangoproject.com/weblog/2021/jun/02/security-releases/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33203', 'https://security.netapp.com/advisory/ntap-20210727-0004/', 'https://github.com/django/django/commit/053cc9534d174dc89daba36724ed2dcb36755b90', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B4SQG2EAF4WCI2SLRL6XRDJ3RPK3ZRDV/', 'https://github.com/advisories/GHSA-68w8-qjq3-2gfm', 'https://groups.google.com/forum/#!forum/django-announce', 'https://docs.djangoproject.com/en/3.2/releases/security/'} | null | {'https://github.com/django/django/commit/053cc9534d174dc89daba36724ed2dcb36755b90'} | {'https://github.com/django/django/commit/053cc9534d174dc89daba36724ed2dcb36755b90'} |
GHSA | GHSA-f8vc-wfc8-hxqh | Improper Privilege Management in Apache Hadoop | In Apache Hadoop 3.2.0 to 3.2.1, 3.0.0-alpha1 to 3.1.3, and 2.0.0-alpha to 2.10.0, WebHDFS client might send SPNEGO authorization header to remote URL without proper verification. | {'CVE-2020-9492'} | 2022-02-09T22:17:38Z | 2022-02-09T22:17:38Z | HIGH | 8.8 | {'CWE-863', 'CWE-269'} | {'https://lists.apache.org/thread.html/r513758942356ccd0d14538ba18a09903fc72716d74be1cb727ea91ff%40%3Cgeneral.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/r49c9ab444ab1107c6a8be8a0d66602dec32a16d96c2631fec8d309fb@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r4a57de5215494c35c8304cf114be75d42df7abc6c0c54bf163c3e370@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/rc0057ebf32b646ab47f7f5744a8948332e015c39044cbb9d87ea76cd@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r79201a209df9a4e7f761e537434131b4e39eabec4369a7d668904df4@%3Cissues.solr.apache.org%3E', 'https://github.com/apache/hadoop/commit/ca65409836d2949e9a9408d40bec0177b414cd5d', 'https://github.com/advisories/GHSA-f8vc-wfc8-hxqh', 'https://lists.apache.org/thread.html/r6341f2a468ced8872a71997aa1786ce036242413484f0fa68dc9ca02@%3Cissues.solr.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20210304-0001/', 'https://lists.apache.org/thread.html/r9328eb49305e4cacc80e182bfd8a2efd8e640d940e24f5bfd7d5cb26@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r0a534f1cde7555f7208e9f9b791c1ab396d215eaaef283b3a9153429@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rb12afaa421d483863c4175e42e5dbd0673917a3cff73f3fca4f8275f@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r941e9be04efe0f455d20aeac88516c0848decd7e7b1d93d5687060f4@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/rca4516b00b55b347905df45e5d0432186248223f30497db87aba8710@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/r6c2fa7949738e9d39606f1d7cd890c93a2633e3357c9aeaf886ea9a6@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/re4129c6b9e0410848bbd3761187ce9c19bc1cd491037b253007df99e@%3Cissues.solr.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-9492', 'https://lists.apache.org/thread.html/r79323adac584edab99fd5e4b52a013844b784a5d4b600da0662b33d6@%3Ccommits.druid.apache.org%3E'} | null | {'https://github.com/apache/hadoop/commit/ca65409836d2949e9a9408d40bec0177b414cd5d'} | {'https://github.com/apache/hadoop/commit/ca65409836d2949e9a9408d40bec0177b414cd5d'} |
GHSA | GHSA-qjj8-32p7-h289 | Division by 0 in `ResourceGather` | ### Impact
An attacker can trigger a crash via a floating point exception in `tf.raw_ops.ResourceGather`:
```python
import tensorflow as tf
tensor = tf.constant(value=[[]],shape=(0,1),dtype=tf.uint32)
v = tf.Variable(tensor)
tf.raw_ops.ResourceGather(
resource=v.handle,
indices=[0],
dtype=tf.uint32,
batch_dims=1,
validate_indices=False)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L725-L731) computes the value of a value, `batch_size`, and then divides by it without checking that this value is not 0.
### Patches
We have patched the issue in GitHub commit [ac117ee8a8ea57b73d34665cdf00ef3303bc0b11](https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11).
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-37653'} | 2021-08-25T14:43:04Z | 2021-08-25T14:43:04Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qjj8-32p7-h289', 'https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11', 'https://github.com/advisories/GHSA-qjj8-32p7-h289', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37653'} | null | {'https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11'} | {'https://github.com/tensorflow/tensorflow/commit/ac117ee8a8ea57b73d34665cdf00ef3303bc0b11'} |
GHSA | GHSA-fv3m-xhqw-9m79 | ballcat-codegen template engine remote code execution injection | ### Impact
Ballcat Codegen provides the function of online editing code to generate templates.
In version < 1.0.0.beta.2, since Velocity and freemarker templates are introduced but input verification is not done, attackers can implement remote code execution through malicious code injection of the template engine.
### Patches
The fault is rectified and needs to be upgraded to the latest version. | {'CVE-2022-24881'} | 2022-04-27T21:05:16Z | 2022-04-27T21:05:15Z | HIGH | 8.8 | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24881', 'https://github.com/advisories/GHSA-fv3m-xhqw-9m79', 'https://github.com/ballcat-projects/ballcat-codegen/security/advisories/GHSA-fv3m-xhqw-9m79', 'https://github.com/ballcat-projects/ballcat-codegen/issues/5', 'https://github.com/ballcat-projects/ballcat-codegen/commit/84a7cb38daf0295b93aba21d562ec627e4eb463b'} | null | {'https://github.com/ballcat-projects/ballcat-codegen/commit/84a7cb38daf0295b93aba21d562ec627e4eb463b'} | {'https://github.com/ballcat-projects/ballcat-codegen/commit/84a7cb38daf0295b93aba21d562ec627e4eb463b'} |
GHSA | GHSA-332q-7ff2-57h2 | Prototype Pollution in undefsafe | undefsafe before 2.0.3 is vulnerable to Prototype Pollution. The 'a' function could be tricked into adding or modifying properties of Object.prototype using a `__proto__` payload. | {'CVE-2019-10795'} | 2022-04-19T19:03:24Z | 2022-02-09T22:34:01Z | MODERATE | 6.3 | {'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10795', 'https://github.com/advisories/GHSA-332q-7ff2-57h2', 'https://snyk.io/vuln/SNYK-JS-UNDEFSAFE-548940', 'https://github.com/remy/undefsafe/commit/f272681b3a50e2c4cbb6a8533795e1453382c822'} | null | {'https://github.com/remy/undefsafe/commit/f272681b3a50e2c4cbb6a8533795e1453382c822'} | {'https://github.com/remy/undefsafe/commit/f272681b3a50e2c4cbb6a8533795e1453382c822'} |
GHSA | GHSA-m7fm-4jfh-jrg6 | Use after free in boosted trees creation | ### Impact
The implementation for `tf.raw_ops.BoostedTreesCreateEnsemble` can result in a use after free error if an attacker supplies specially crafted arguments:
```python
import tensorflow as tf
v= tf.Variable([0.0])
tf.raw_ops.BoostedTreesCreateEnsemble(
tree_ensemble_handle=v.handle,
stamp_token=[0],
tree_ensemble_serialized=['0'])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/boosted_trees/resource_ops.cc#L55) uses a reference counted resource and decrements the refcount if the initialization fails, as it should. However, when the code was written, the resource was represented as a naked pointer but later refactoring has changed it to be a smart pointer. Thus, when the pointer leaves the scope, a subsequent `free`-ing of the resource occurs, but this fails to take into account that the refcount has already reached 0, thus the resource has been already freed. During this double-free process, members of the resource object are accessed for cleanup but they are invalid as the entire resource has been freed.
### Patches
We have patched the issue in GitHub commit [5ecec9c6fbdbc6be03295685190a45e7eee726ab](https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab).
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-37652'} | 2021-08-25T14:43:07Z | 2021-08-25T14:43:07Z | HIGH | 7.8 | {'CWE-416'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-37652', 'https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab', 'https://github.com/advisories/GHSA-m7fm-4jfh-jrg6', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m7fm-4jfh-jrg6'} | null | {'https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab'} | {'https://github.com/tensorflow/tensorflow/commit/5ecec9c6fbdbc6be03295685190a45e7eee726ab'} |
GHSA | GHSA-52mq-6jcv-j79x | User content sandbox can be confused into opening arbitrary documents | ### Impact
The user content sandbox can be abused to trick users into opening unexpected documents after several user interactions. The content can be opened with a `blob` origin from the Matrix client, so it is possible for a malicious document to access user messages and secrets.
### Patches
This has been fixed by https://github.com/matrix-org/matrix-react-sdk/pull/5657, which is included in 3.15.0.
### Workarounds
There are no known workarounds. | {'CVE-2021-21320'} | 2022-04-19T19:02:48Z | 2021-03-03T02:23:56Z | LOW | 2.6 | {'CWE-345'} | {'https://github.com/matrix-org/matrix-react-sdk/pull/5657', 'https://github.com/matrix-org/matrix-react-sdk/security/advisories/GHSA-52mq-6jcv-j79x', 'https://github.com/advisories/GHSA-52mq-6jcv-j79x', 'https://www.npmjs.com/package/matrix-react-sdk', 'https://github.com/matrix-org/matrix-react-sdk/commit/b386f0c73b95ecbb6ea7f8f79c6ff5171a8dedd1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21320'} | null | {'https://github.com/matrix-org/matrix-react-sdk/commit/b386f0c73b95ecbb6ea7f8f79c6ff5171a8dedd1'} | {'https://github.com/matrix-org/matrix-react-sdk/commit/b386f0c73b95ecbb6ea7f8f79c6ff5171a8dedd1'} |
GHSA | GHSA-8687-vv9j-hgph | Improper Input Validation in Automattic Mongoose | Automattic Mongoose through 5.7.4 allows attackers to bypass access control (in some applications) because any query object with a _bsontype attribute is ignored. For example, adding "_bsontype":"a" can sometimes interfere with a query filter. NOTE: this CVE is about Mongoose's failure to work around this _bsontype special case that exists in older versions of the bson parser (aka the mongodb/js-bson project). | {'CVE-2019-17426'} | 2021-07-27T22:16:02Z | 2019-10-22T20:19:54Z | CRITICAL | 9.1 | {'CWE-20'} | {'https://github.com/Automattic/mongoose/issues/8222', 'https://github.com/Automattic/mongoose/commit/f3eca5b94d822225c04e96cbeed9f095afb3c31c', 'https://github.com/advisories/GHSA-8687-vv9j-hgph', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17426'} | null | {'https://github.com/Automattic/mongoose/commit/f3eca5b94d822225c04e96cbeed9f095afb3c31c'} | {'https://github.com/Automattic/mongoose/commit/f3eca5b94d822225c04e96cbeed9f095afb3c31c'} |
GHSA | GHSA-v525-c3g5-cg9p | Unsafe Deserialization that can Result in Code Execution | JMS Client for RabbitMQ 1.x before 1.15.2 and 2.x before 2.2.0 is vulnerable to unsafe deserialization that can result in code execution via crafted StreamMessage data. | {'CVE-2020-36282'} | 2021-12-10T17:15:49Z | 2021-12-10T17:15:49Z | HIGH | 0 | {'CWE-502'} | {'https://github.com/rabbitmq/rabbitmq-jms-client/issues/135', 'https://medium.com/@ramon93i7/a99645d0448b', 'https://github.com/rabbitmq/rabbitmq-jms-client/releases/tag/v2.2.0', 'https://github.com/rabbitmq/rabbitmq-jms-client/pull/136/commits/f647e5dbfe055a2ca8cbb16dd70f9d50d888b638', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36282', 'https://github.com/advisories/GHSA-v525-c3g5-cg9p', 'https://github.com/rabbitmq/rabbitmq-jms-client/releases/tag/v1.15.2'} | null | {'https://github.com/rabbitmq/rabbitmq-jms-client/pull/136/commits/f647e5dbfe055a2ca8cbb16dd70f9d50d888b638'} | {'https://github.com/rabbitmq/rabbitmq-jms-client/pull/136/commits/f647e5dbfe055a2ca8cbb16dd70f9d50d888b638'} |
GHSA | GHSA-vhr6-pvjm-9qwf | User passwords are stored in clear text in the Django session | ### Impact
django-two-factor-auth versions 1.11 and before store the user's password in clear text in the user session (base64-encoded). The password is stored in the session when the user submits their username and password, and is removed once they complete authentication by entering a two-factor authentication code. This means that the password is stored in clear text in the session for an arbitrary amount of time, and potentially forever if the user begins the login process by entering their username and password, and then leaves before entering their two-factor authentication code.
The severity of this issue depends on which type of session storage you have configured: in the worst case, if you're using Django's default database session storage, then users' password are stored in clear text in your database. In the best case, if you're using Django's signed cookie session, then users' passwords are only stored in clear text within their browser's cookie store. In the common case of using Django's cache session store, the users' password are stored in clear text in whatever cache storage you have configured (typically Memcached or Redis).
### Patches
Upgrade to version 1.12 to resolve this issue.
After upgrading, users should be sure to delete any clear text passwords that have been stored. For example, if you're using the database session backend, you'll likely want to delete any session record from the database and purge that data from any database backups or replicas.
In addition, affected organizations who have suffered a database breach while using an affected version should inform their users that their clear text passwords have been compromised. All organizations should encourage users whose passwords were insecurely stored to change these passwords on any sites where they were used.
### Workarounds
Switching Django's session storage to use signed cookies instead of the database or cache lessens the impact of this issue, but should not be done without a thorough understanding of the security tradeoffs of using signed cookies rather than a server-side session storage. There is no way to fully mitigate the issue without upgrading.
### References
For an explanation of why storing cleartext password is a substantial vulnerability: [Hashing Passwords: One-Way Road to Security](https://auth0.com/blog/hashing-passwords-one-way-road-to-security/).
For documentation on configuring the Django session storage engine: [Django session documentation](https://docs.djangoproject.com/en/3.0/topics/http/sessions/).
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the repo](https://github.com/Bouke/django-two-factor-auth) | {'CVE-2020-15105'} | 2022-04-19T19:02:29Z | 2020-07-10T20:55:00Z | HIGH | 5.4 | {'CWE-312'} | {'https://github.com/Bouke/django-two-factor-auth/security/advisories/GHSA-vhr6-pvjm-9qwf', 'https://github.com/advisories/GHSA-vhr6-pvjm-9qwf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15105', 'https://github.com/Bouke/django-two-factor-auth/blob/master/CHANGELOG.md#112---2020-07-08', 'https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359'} | null | {'https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359'} | {'https://github.com/Bouke/django-two-factor-auth/commit/454fd9842fa6e8bb772dbf0943976bc8e3335359'} |
GHSA | GHSA-xpm8-98mx-h4c5 | Critical severity vulnerability that affects MLAlchemy | An exploitable vulnerability exists in the YAML parsing functionality in the parse_yaml_query method in parser.py in MLAlchemy before 0.2.2. When processing YAML-Based queries for data, a YAML parser can execute arbitrary Python commands resulting in command execution because load is used where safe_load should have been used. An attacker can insert Python into loaded YAML to trigger this vulnerability. | {'CVE-2017-16615'} | 2022-03-22T20:44:42Z | 2018-07-13T16:01:07Z | CRITICAL | 9.8 | null | {'https://github.com/thanethomson/MLAlchemy/commit/bc795757febdcce430d89f9d08f75c32d6989d3c', 'https://github.com/thanethomson/MLAlchemy/issues/1', 'https://joel-malwarebenchmark.github.io/blog/2017/11/08/cve-2017-16615-critical-restful-web-applications-vulnerability/', 'https://github.com/advisories/GHSA-xpm8-98mx-h4c5', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16615'} | null | {'https://github.com/thanethomson/MLAlchemy/commit/bc795757febdcce430d89f9d08f75c32d6989d3c'} | {'https://github.com/thanethomson/MLAlchemy/commit/bc795757febdcce430d89f9d08f75c32d6989d3c'} |
GHSA | GHSA-g8q7-xv52-hf9f | Feedgen Vulnerable to XML Denial of Service Attacks | ### Impact
The *feedgen* library allows supplying XML as content for some of the available fields. This XML will be parsed and integrated into the existing XML tree. During this process, feedgen is vulnerable to [XML Denial of Service Attacks](https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses) (e.g. XML Bomb).
This becomes a concern in particular if feedgen is used to include content from untrused sources and if XML (including XHTML) is directly included instead of providing plain tex content only.
### Patches
This problem has been fixed in feedgen 0.9.0 which disallows XML entity expansion and external resources.
### Workarounds
Updating is strongly recommended and should not be problematic. Nevertheless, as a workaround, avoid providing XML directly to feedgen or ensure that no entity expansion is part of the XML.
### References
- [Security Briefs - XML Denial of Service Attacks and Defenses](https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses)
- [Billion laughs attack](https://en.wikipedia.org/wiki/Billion_laughs_attack#cite_note-2)
### For more information
If you have any questions or comments about this advisory:
- Open an issue in [lkiesow/python-feedgen](https://github.com/lkiesow/python-feedgen/issues)
- Send an email to security@lkiesow.de | {'CVE-2020-5227'} | 2021-01-08T21:09:03Z | 2020-01-28T22:37:50Z | HIGH | 4.4 | {'CWE-776'} | {'https://github.com/lkiesow/python-feedgen/security/advisories/GHSA-g8q7-xv52-hf9f', 'https://github.com/advisories/GHSA-g8q7-xv52-hf9f', 'https://docs.microsoft.com/en-us/archive/msdn-magazine/2009/november/xml-denial-of-service-attacks-and-defenses', 'https://github.com/lkiesow/python-feedgen/commit/f57a01b20fa4aaaeccfa417f28e66b4084b9d0cf', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/T6I5ENUYGFNMIH6ZQ62FZ6VU2WD3SIOI/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5227'} | null | {'https://github.com/lkiesow/python-feedgen/commit/f57a01b20fa4aaaeccfa417f28e66b4084b9d0cf'} | {'https://github.com/lkiesow/python-feedgen/commit/f57a01b20fa4aaaeccfa417f28e66b4084b9d0cf'} |
GHSA | GHSA-7q4h-pj78-j7vg | Authorization service vulnerable to DDos attacks in Apache CFX | CXF supports (via JwtRequestCodeFilter) passing OAuth 2 parameters via a JWT token as opposed to query parameters (see: The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)). Instead of sending a JWT token as a "request" parameter, the spec also supports specifying a URI from which to retrieve a JWT token from via the "request_uri" parameter. CXF was not validating the "request_uri" parameter (apart from ensuring it uses "https) and was making a REST request to the parameter in the request to retrieve a token. This means that CXF was vulnerable to DDos attacks on the authorization server, as specified in section 10.4.1 of the spec. This issue affects Apache CXF versions prior to 3.4.3; Apache CXF versions prior to 3.3.10. | {'CVE-2021-22696'} | 2022-04-22T16:50:03Z | 2021-05-13T22:31:05Z | HIGH | 7.5 | {'CWE-400', 'CWE-918'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-22696', 'https://github.com/advisories/GHSA-7q4h-pj78-j7vg', 'https://github.com/apache/cxf/commit/40503a53914758759894f704bbf139ae89ace286', 'https://lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/r8651c06212c56294a1c0ea61a5ad7790c06502209c03f05c0c7c9914@%3Cusers.cxf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/apache/cxf/commit/aa789c5c4686597a7bdef2443909ab491fc2bc04', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r6445001cc5f9a2bb1e6316993753306e054bdd1d702656b7cbe59045@%3Cannounce.apache.org%3E', 'https://lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4@%3Ccommits.cxf.apache.org%3E', 'https://lists.apache.org/thread.html/r8651c06212c56294a1c0ea61a5ad7790c06502209c03f05c0c7c9914@%3Cdev.cxf.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2021/04/02/2', 'https://cxf.apache.org/security-advisories.data/CVE-2021-22696.txt.asc'} | null | {'https://github.com/apache/cxf/commit/aa789c5c4686597a7bdef2443909ab491fc2bc04', 'https://github.com/apache/cxf/commit/40503a53914758759894f704bbf139ae89ace286'} | {'https://github.com/apache/cxf/commit/aa789c5c4686597a7bdef2443909ab491fc2bc04', 'https://github.com/apache/cxf/commit/40503a53914758759894f704bbf139ae89ace286'} |
GHSA | GHSA-cjx7-399x-p2rj | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in micronaut-core | With a basic configuration like
```yaml
router:
static-resources:
assets:
enabled: true
mapping: /.assets/public/**
paths: file:/home/lstrmiska/test/
```
it is possible to access any file from a filesystem, using "/../../" in URL, as Micronaut does not restrict file access to configured paths.
**Repro Steps**
- create a file test.txt in /home/lstrmiska
- start micronaut
- execute command
`curl -v --path-as-is "http://localhost:8080/.assets/public/../test.txt"`
### Impact
Micronaut can potentially leak sensitive information.
See https://cwe.mitre.org/data/definitions/22.html
### Patches
```
diff --git a/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java b/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java
index 2f5a91403..19d3b7f05 100644
--- a/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java
+++ b/core/src/main/java/io/micronaut/core/io/file/DefaultFileSystemResourceLoader.java
@@ -69,6 +69,9 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader
@Override
public Optional<InputStream> getResourceAsStream(String path) {
Path filePath = getFilePath(normalize(path));
+ if (pathOutsideBase(filePath)) {
+ return Optional.empty();
+ }
try {
return Optional.of(Files.newInputStream(filePath));
} catch (IOException e) {
@@ -79,7 +82,7 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader
@Override
public Optional<URL> getResource(String path) {
Path filePath = getFilePath(normalize(path));
- if (Files.exists(filePath) && Files.isReadable(filePath) && !Files.isDirectory(filePath)) {
+ if (!pathOutsideBase(filePath) && Files.exists(filePath) && Files.isReadable(filePath) && !Files.isDirectory(filePath)) {
try {
URL url = filePath.toUri().toURL();
return Optional.of(url);
@@ -117,4 +120,15 @@ public class DefaultFileSystemResourceLoader implements FileSystemResourceLoader
private Path getFilePath(String path) {
return baseDirPath.map(dir -> dir.resolve(path)).orElseGet(() -> Paths.get(path));
}
+
+ private boolean pathOutsideBase(Path path) {
+ if (baseDirPath.isPresent()) {
+ Path baseDir = baseDirPath.get();
+ if (path.isAbsolute() == baseDir.isAbsolute()) {
+ Path relativePath = baseDir.relativize(path);
+ return relativePath.startsWith("..");
+ }
+ }
+ return false;
+ }
}
--
```
### Workarounds
- do not use ** in mapping, use only * which exposes only flat structure of a directory not allowing traversal
- run micronaut in chroot (linux only)
### References
See https://cwe.mitre.org/data/definitions/22.html
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Github](https://github.com/micronaut-projects/micronaut-core/issues)
* Email us at [info@micronaut.io](mailto:info@micronaut.io)
| {'CVE-2021-32769'} | 2022-04-19T19:03:03Z | 2021-07-26T21:15:08Z | HIGH | 7.5 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32769', 'https://github.com/micronaut-projects/micronaut-core/security/advisories/GHSA-cjx7-399x-p2rj', 'https://github.com/advisories/GHSA-cjx7-399x-p2rj', 'https://github.com/micronaut-projects/micronaut-core/commit/a0cfeb13bf1ef5d692d16d4a3b91b34b7456bb11'} | null | {'https://github.com/micronaut-projects/micronaut-core/commit/a0cfeb13bf1ef5d692d16d4a3b91b34b7456bb11'} | {'https://github.com/micronaut-projects/micronaut-core/commit/a0cfeb13bf1ef5d692d16d4a3b91b34b7456bb11'} |
GHSA | GHSA-23fp-fmrv-f5px | Uncontrolled Resource Consumption in strapi | A denial of service exists in strapi v3.0.0-beta.18.3 and earlier that can be abused in the admin console using admin rights can lead to arbitrary restart of the application. | {'CVE-2020-8123'} | 2021-12-10T17:22:01Z | 2021-12-10T17:22:01Z | MODERATE | 4.9 | {'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8123', 'https://hackerone.com/reports/768574', 'https://github.com/advisories/GHSA-23fp-fmrv-f5px', 'https://github.com/strapi/strapi/commit/c0c191c08f05fe10d7a6b1bf9475c1a651a89362'} | null | {'https://github.com/strapi/strapi/commit/c0c191c08f05fe10d7a6b1bf9475c1a651a89362'} | {'https://github.com/strapi/strapi/commit/c0c191c08f05fe10d7a6b1bf9475c1a651a89362'} |
GHSA | GHSA-w68r-5p45-5rqp | Improper Input Validation in Laravel | An issue was discovered in Laravel before 6.18.35 and 7.x before 7.24.0. The $guarded property is mishandled in some situations involving requests with JSON column nesting expressions. | {'CVE-2020-24941'} | 2021-07-29T22:25:35Z | 2021-05-06T18:54:20Z | HIGH | 7.5 | {'CWE-863'} | {'https://github.com/advisories/GHSA-w68r-5p45-5rqp', 'https://blog.laravel.com/security-release-laravel-61835-7240', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24941', 'https://github.com/laravel/framework/commit/897d107775737a958dbd0b2f3ea37877c7526371'} | null | {'https://github.com/laravel/framework/commit/897d107775737a958dbd0b2f3ea37877c7526371'} | {'https://github.com/laravel/framework/commit/897d107775737a958dbd0b2f3ea37877c7526371'} |
GHSA | GHSA-cmcx-xhr8-3w9p | Denial of Service in uap-core when processing crafted User-Agent strings | ### Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
### Patches
Please update uap-core to &amp;gt;= v0.7.3
Downstream packages such as uap-python, uap-ruby etc which depend upon uap-core follow different version schemes.
### Details
Each vulnerable regular expression reported here contains 3 overlapping capture groups. Backtracking has approximately cubic time complexity with respect to the length of the user-agent string.
#### Regex 1:
```
\bSmartWatch *\( *([^;]+) *; *([^;]+) *;
```
is vulnerable in portion ` *([^;]+) *` and can be attacked with
```python
&amp;quot;SmartWatch(&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
e.g.
```
SmartWatch( z
```
#### Regex 2:
```
; *([^;/]+) Build[/ ]Huawei(MT1-U06|[A-Z]+\d+[^\);]+)[^\);]*\)
```
is vulnerable in portion `\d+[^\);]+[^\);]*` and can be attacked with
```python
&amp;quot;;A Build HuaweiA&amp;quot; + (&amp;quot;4&amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
#### Regex 3:
```
(HbbTV)/[0-9]+\.[0-9]+\.[0-9]+ \([^;]*; *(LG)E *; *([^;]*) *;[^;]*;[^;]*;\)
```
is vulnerable in portion ` *([^;]*) *` and can be attacked with
```python
&amp;quot;HbbTV/0.0.0 (;LGE;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
#### Regex 4:
```
(HbbTV)/[0-9]+\.[0-9]+\.[0-9]+ \([^;]*; *(?:CUS:([^;]*)|([^;]+)) *; *([^;]*) *;.*;
```
is vulnerable in portions ` *(?:CUS:([^;]*)|([^;]+)) *` and ` *([^;]*) *` and can be attacked with
```python
&amp;quot;HbbTV/0.0.0 (;CUS:;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
&amp;quot;HbbTV/0.0.0 (;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
&amp;quot;HbbTV/0.0.0 (;z;&amp;quot; + (&amp;quot; &amp;quot; * 3500) + &amp;quot;z&amp;quot;
```
Reported by Ben Caller @bcaller | {'CVE-2020-5243'} | 2022-04-19T19:02:24Z | 2020-02-20T23:26:10Z | HIGH | 5.7 | {'CWE-20'} | {'https://github.com/advisories/GHSA-cmcx-xhr8-3w9p', 'https://github.com/ua-parser/uap-core/commit/0afd61ed85396a3b5316f18bfd1edfaadf8e88e1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5243', 'https://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p'} | null | {'https://github.com/ua-parser/uap-core/commit/0afd61ed85396a3b5316f18bfd1edfaadf8e88e1'} | {'https://github.com/ua-parser/uap-core/commit/0afd61ed85396a3b5316f18bfd1edfaadf8e88e1'} |
GHSA | GHSA-hjmq-236j-8m87 | Denial of service in tensorflow-lite | ### Impact
In TensorFlow Lite models using segment sum can trigger a denial of service by causing an out of memory allocation in the implementation of segment sum. Since code uses the last element of the tensor holding them to determine the dimensionality of output tensor, attackers can use a very large value to trigger a large allocation:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/segment_sum.cc#L39-L44
### Patches
We have patched the issue in 204945b and will release patch releases for all affected versions.
We recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1.
### Workarounds
A potential workaround would be to add a custom `Verifier` to limit the maximum value in the segment ids tensor. This only handles the case when the segment ids are stored statically in the model, but a similar validation could be done if the segment ids are generated at runtime, between inference steps.
However, if the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm). | {'CVE-2020-15213'} | 2021-08-26T15:19:57Z | 2020-09-25T18:28:53Z | MODERATE | 4 | {'CWE-119', 'CWE-770'} | {'https://github.com/advisories/GHSA-hjmq-236j-8m87', 'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hjmq-236j-8m87', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15213', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} | {'https://github.com/tensorflow/tensorflow/commit/204945b19e44b57906c9344c0d00120eeeae178a'} |
GHSA | GHSA-c4qr-gmr9-v23w | Prefix escape | ### Impact
By crafting a specific URL, it is possible to escape the prefix of the proxied backend service.
If the base url of the proxied server is `/pub/`, a user expect that accessing `/priv` on the target service would not be possible. Unfortunately, it is.
[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N)
### Patches
All releases after v4.3.1 include the fix.
### Workarounds
There are no workaround available.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [fastify-reply-from](https://github.com/fastify/fastify-reply-from)
* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com) | {'CVE-2021-21322'} | 2021-03-03T17:49:53Z | 2021-03-03T02:18:08Z | LOW | 10 | {'CWE-20'} | {'https://github.com/fastify/fastify-http-proxy/security/advisories/GHSA-c4qr-gmr9-v23w', 'https://github.com/fastify/fastify-http-proxy/commit/02d9b43c770aa16bc44470edecfaeb7c17985016', 'https://github.com/advisories/GHSA-c4qr-gmr9-v23w', 'https://www.npmjs.com/package/fastify-http-proxy', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21322'} | null | {'https://github.com/fastify/fastify-http-proxy/commit/02d9b43c770aa16bc44470edecfaeb7c17985016'} | {'https://github.com/fastify/fastify-http-proxy/commit/02d9b43c770aa16bc44470edecfaeb7c17985016'} |
GHSA | GHSA-8r7c-3cm2-3h8f | Memory leak in Tensorflow | ### Impact
If a graph node is invalid, TensorFlow can leak memory in the [implementation of `ImmutableExecutorState::Initialize`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/common_runtime/immutable_executor_state.cc#L84-L262):
```cc
Status s = params_.create_kernel(n->properties(), &item->kernel);
if (!s.ok()) {
item->kernel = nullptr;
s = AttachDef(s, *n);
return s;
}
```
Here, we set `item->kernel` to `nullptr` but it is a simple `OpKernel*` pointer so the memory that was previously allocated to it would leak.
### Patches
We have patched the issue in GitHub commit [c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd](https://github.com/tensorflow/tensorflow/commit/c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd).
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-23578'} | 2022-02-11T20:39:19Z | 2022-02-10T00:33:13Z | MODERATE | 4.3 | {'CWE-401'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8r7c-3cm2-3h8f', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/common_runtime/immutable_executor_state.cc#L84-L262', 'https://github.com/tensorflow/tensorflow/commit/c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23578', 'https://github.com/advisories/GHSA-8r7c-3cm2-3h8f'} | null | {'https://github.com/tensorflow/tensorflow/commit/c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd'} | {'https://github.com/tensorflow/tensorflow/commit/c79ccba517dbb1a0ccb9b01ee3bd2a63748b60dd'} |
GHSA | GHSA-9vjp-v76f-g363 | SnappyFrameDecoder doesn't restrict chunk length any may buffer skippable chunks in an unnecessary way | ### Impact
The Snappy frame decoder function doesn't restrict the chunk length which may lead to excessive memory usage. Beside this it also may buffer reserved skippable chunks until the whole chunk was received which may lead to excessive memory usage as well.
This vulnerability can be triggered by supplying malicious input that decompresses to a very big size (via a network stream or a file) or by sending a huge skippable chunk.
### Impact
All users of SnappyFrameDecoder are affected and so the application may be in risk for a DoS attach due excessive memory usage.
### References
https://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L79
https://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L171
https://github.com/netty/netty/blob/netty-4.1.67.Final/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L185 | {'CVE-2021-37137'} | 2022-04-22T15:41:10Z | 2021-09-09T17:11:31Z | HIGH | 7.5 | {'CWE-400'} | {'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/advisories/GHSA-9vjp-v76f-g363', 'https://lists.apache.org/thread.html/rfb2bf8597e53364ccab212fbcbb2a4e9f0a9e1429b1dc08023c6868e@%3Cdev.tinkerpop.apache.org%3E', 'https://lists.apache.org/thread.html/r75490c61c2cb7b6ae2c81238fd52ae13636c60435abcd732d41531a0@%3Ccommits.druid.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37137', 'https://lists.apache.org/thread.html/rd262f59b1586a108e320e5c966feeafbb1b8cdc96965debc7cc10b16@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r5e05eba32476c580412f9fbdfc9b8782d5b40558018ac4ac07192a04@%3Ccommits.druid.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/netty/netty/security/advisories/GHSA-9vjp-v76f-g363', 'https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L79', 'https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L171', 'https://security.netapp.com/advisory/ntap-20220210-0012/', 'https://lists.apache.org/thread.html/r06a145c9bd41a7344da242cef07977b24abe3349161ede948e30913d@%3Ccommits.druid.apache.org%3E', 'https://github.com/netty/netty/blob/4.1/codec/src/main/java/io/netty/handler/codec/compression/SnappyFrameDecoder.java#L185', 'https://lists.apache.org/thread.html/r5406eaf3b07577d233b9f07cfc8f26e28369e6bab5edfcab41f28abb@%3Ccommits.druid.apache.org%3E', 'https://github.com/netty/netty/commit/6da4956b31023ae967451e1d94ff51a746a9194f'} | null | {'https://github.com/netty/netty/commit/6da4956b31023ae967451e1d94ff51a746a9194f'} | {'https://github.com/netty/netty/commit/6da4956b31023ae967451e1d94ff51a746a9194f'} |
GHSA | GHSA-q3cc-7p7g-392c | Use after free in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free. | {'CVE-2020-35873'} | 2021-08-25T20:47:43Z | 2021-08-25T20:47:43Z | CRITICAL | 9.8 | {'CWE-416'} | {'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35873', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/advisories/GHSA-q3cc-7p7g-392c', 'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'} | null | {'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'} | {'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.