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-7h43-gx24-p529 | Prototype pollution in json8 | This affects the package json8 before 1.0.3. The function adds in the target object the property specified in the path, however it does not properly check the key being set, leading to a prototype pollution. | {'CVE-2020-7770'} | 2021-05-10T19:17:05Z | 2021-05-10T19:17:05Z | CRITICAL | 9.8 | {'CWE-1321'} | {'https://snyk.io/vuln/SNYK-JS-JSON8-1017116', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7770', 'https://github.com/sonnyp/JSON8/commit/2e890261b66cbc54ae01d0c79c71b0fd18379e7e', 'https://github.com/advisories/GHSA-7h43-gx24-p529', 'https://www.npmjs.com/package/json8'} | null | {'https://github.com/sonnyp/JSON8/commit/2e890261b66cbc54ae01d0c79c71b0fd18379e7e'} | {'https://github.com/sonnyp/JSON8/commit/2e890261b66cbc54ae01d0c79c71b0fd18379e7e'} |
GHSA | GHSA-7f33-f4f5-xwgw | In-band key negotiation issue in AWS S3 Crypto SDK for golang | ### Summary
The golang AWS S3 Crypto SDK is impacted by an issue that can result in loss of confidentiality and message forgery. The attack requires write access to the bucket in question, and that the attacker has access to an endpoint that reveals decryption failures (without revealing the plaintext) and that when encrypting the GCM option was chosen as content cipher.
### Risk/Severity
The vulnerability pose insider risks/privilege escalation risks, circumventing KMS controls for stored data.
### Impact
This advisory describes the plaintext revealing vulnerabilities in the golang AWS S3 Crypto SDK, with a similar issue in the non "strict" versions of C++ and Java S3 Crypto SDKs being present as well.
V1 prior to 1.34.0 of the S3 crypto SDK does not authenticate the algorithm parameters for the data encryption key.
An attacker with write access to the bucket can use this in order to change the encryption algorithm of an object in the bucket, which can lead to problems depending on the supported algorithms. For example, a switch from AES-GCM to AES-CTR in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation.
By default, the only available algorithms in the SDK are AES-GCM and AES-CBC. Switching the algorithm from AES-GCM to AES-CBC can be used as way to reconstruct the plaintext through an oracle endpoint revealing decryption failures, by brute forcing 16 byte chunks of the plaintext. Note that the plaintext needs to have some known structure for this to work, as a uniform random 16 byte string would be the same as a 128 bit encryption key, which is considered cryptographically safe.
The attack works by taking a 16 byte AES-GCM encrypted block guessing 16 bytes of plaintext, constructing forgery that pretends to be PKCS5 padded AES-CBC, using the ciphertext and the plaintext guess and that will decrypt to a valid message if the guess was correct.
To understand this attack, we have to take a closer look at both AES-GCM and AES-CBC:
AES-GCM encrypts using a variant of CTR mode, i.e. `C_i = AES-Enc(CB_i) ^ M_i`. AES-CBC on the other hand *decrypts* via `M_i = AES-Dec(C_i) ^ C_{i-1}`, where `C_{-1} = IV`. The padding oracle can tell us if, after switching to CBC mode, the plaintext recovered is padded with a valid PKCS5 padding.
Since `AES-Dec(C_i ^ M_i) = CB_i`, if we set `IV' = CB_i ^ 0x10*[16]`, where `0x10*[16]` is the byte `0x10` repeated 16 times, and `C_0' = C_i ^ M_i'` the resulting one block message `(IV', C_0')` will have valid PKCS5 padding if our guess `M_i'` for `M_i` was correct, since the decrypted message consists of 16 bytes of value `0x10`, the PKCS5 padded empty string.
Note however, that an incorrect guess might also result in a valid padding, if the AES decryption result randomly happens to end in `0x01`, `0x0202`, or a longer valid padding. In order to ensure that the guess was indeed correct, a second check using `IV'' = IV' ^ (0x00*[15] || 0x11)` with the same ciphertext block has to be performed. This will decrypt to 15 bytes of value `0x10` and one byte of value `0x01` if our initial guess was correct, producing a valid padding. On an incorrect guess, this second ciphertext forgery will have an invalid padding with a probability of 1:2^128, as one can easily see.
This issue is fixed in V2 of the API, by using the `KMS+context` key wrapping scheme for new files, authenticating the algorithm. Old files encrypted with the `KMS` key wrapping scheme remain vulnerable until they are reencrypted with the new scheme.
### Mitigation
Using the version 2 of the S3 crypto SDK will not produce vulnerable files anymore. Old files remain vulnerable to this problem if they were originally encrypted with GCM mode and use the `KMS` key wrapping option.
### Proof of concept
A [Proof of concept](https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc) is available in a separate github repository.
This particular issue is described in [combined_oracle_exploit.go](https://github.com/sophieschmieg/exploits/blob/master/aws_s3_crypto_poc/exploit/combined_oracle_exploit.go):
```golang
func CombinedOracleExploit(bucket string, key string, input *OnlineAttackInput) (string, error) {
data, header, err := input.S3Mock.GetObjectDirect(bucket, key)
if alg := header.Get("X-Amz-Meta-X-Amz-Cek-Alg"); alg != "AES/GCM/NoPadding" {
return "", fmt.Errorf("Algorithm is %q, not GCM!", alg)
}
gcmIv, err := base64.StdEncoding.DecodeString(header.Get("X-Amz-Meta-X-Amz-Iv"))
if len(gcmIv) != 12 {
return "", fmt.Errorf("GCM IV is %d bytes, not 12", len(gcmIv))
}
fullIv := make([]byte, 16)
confirmIv := make([]byte, 16)
for i := 0; i < 12; i++ {
fullIv[i] = gcmIv[i] ^ 0x10
confirmIv[i] = gcmIv[i] ^ 0x10
}
// Set i to the block we want to attempt to decrypt
counter := i + 2
for j := 15; j >= 12; j-- {
v := byte(counter % 256)
fullIv[j] = 0x10 ^ v
confirmIv[j] = 0x10 ^ v
counter /= 256
}
confirmIv[15] ^= 0x11
fullIvEnc := base64.StdEncoding.EncodeToString(fullIv)
confirmIvEnc := base64.StdEncoding.EncodeToString(confirmIv)
success := false
// Set plaintextGuess to the guess for the plaintext of this block
newData := []byte(plaintextGuess)
for j := 0; j < 16; j++ {
newData[j] ^= data[16*i+j]
}
newHeader := header.Clone()
newHeader.Set("X-Amz-Meta-X-Amz-Cek-Alg", "AES/CBC/PKCS5Padding")
newHeader.Set("X-Amz-Meta-X-Amz-Iv", fullIvEnc)
newHeader.Set("X-Amz-Meta-X-Amz-Unencrypted-Content-Length", "16")
input.S3Mock.PutObjectDirect(bucket, key+"guess", newData, newHeader)
if input.Oracle(bucket, key+"guess") {
newHeader.Set("X-Amz-Meta-X-Amz-Iv", confirmIvEnc)
input.S3Mock.PutObjectDirect(bucket, key+"guess", newData, newHeader)
if input.Oracle(bucket, key+"guess") {
return plaintextGuess, nil
}
}
return "", fmt.Errorf("Block %d could not be decrypted", i)
}
``` | {'CVE-2020-8912'} | 2022-04-19T19:02:32Z | 2022-02-11T23:23:13Z | LOW | 2.5 | {'CWE-327'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/pull/3403', 'https://github.com/advisories/GHSA-7f33-f4f5-xwgw', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8912', 'https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw', 'https://bugzilla.redhat.com/show_bug.cgi?id=1869801', 'https://github.com/sophieschmieg/exploits/tree/master/aws_s3_crypto_poc', 'https://aws.amazon.com/blogs/developer/updates-to-the-amazon-s3-encryption-client/?s=09', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} | null | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://github.com/aws/aws-sdk-go/commit/ae9b9fd92af132cfd8d879809d8611825ba135f4'} |
GHSA | GHSA-4278-2v5v-65r4 | Heap buffer overflow in `RaggedBinCount` | ### Impact
If the `splits` argument of `RaggedBincount` does not specify a valid [`SparseTensor`](https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow:
```python
import tensorflow as tf
tf.raw_ops.RaggedBincount(splits=[0], values=[1,1,1,1,1], size=5, weights=[1,2,3,4], binary_output=False)
```
This will cause a read from outside the bounds of the `splits` tensor buffer in the [implementation of the `RaggedBincount` op](https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433):
```cc
for (int idx = 0; idx < num_values; ++idx) {
while (idx >= splits(batch_idx)) {
batch_idx++;
}
...
}
```
Before the `for` loop, `batch_idx` is set to 0. The user controls the `splits` array, making it contain only one element, 0. Thus, the code in the `while` loop would increment `batch_idx` and then try to read `splits(1)`, which is outside of bounds.
### Patches
We have patched the issue in GitHub commit [eebb96c2830d48597d055d247c0e9aebaea94cd5](https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5).
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, as these are also affected.
### 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-29512'} | 2021-05-21T14:20:40Z | 2021-05-21T14:20:40Z | LOW | 2.5 | {'CWE-787', 'CWE-120'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29512', 'https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4278-2v5v-65r4', 'https://github.com/advisories/GHSA-4278-2v5v-65r4'} | null | {'https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5'} | {'https://github.com/tensorflow/tensorflow/commit/eebb96c2830d48597d055d247c0e9aebaea94cd5'} |
GHSA | GHSA-6cp7-g972-w9m9 | Use of a Key Past its Expiration Date and Insufficient Session Expiration in Maddy Mail Server | ### Impact
Any configuration on any maddy version <0.5.4 using auth.pam is affected.
No password expiry or account expiry checking is done when authenticating using PAM.
### Patches
Patch is available as part of the 0.5.4 release.
### Workarounds
If /etc/shadow authentication is used, it is possible to replace auth.pam with auth.shadow which is not affected.
It is possible to blacklist expired accounts via existing filtering mechanisms (e.g. auth_map to invalid accounts in storage.imapsql).
### References
* https://github.com/foxcpp/maddy/blob/3412e59a2c92106e194fa69f2f1017c020037c9c/internal/auth/pam/pam.c
* https://linux.die.net/man/3/pam_acct_mgmt
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/foxcpp/maddy
* Email fox.cpp@disroot.org
| {'CVE-2022-24732'} | 2022-03-18T20:12:31Z | 2022-03-07T16:59:31Z | MODERATE | 6.3 | {'CWE-324', 'CWE-613'} | {'https://github.com/advisories/GHSA-6cp7-g972-w9m9', 'https://github.com/foxcpp/maddy/commit/7ee6a39c6a1939b376545f030a5efd6f90913583', 'https://github.com/foxcpp/maddy/releases/tag/v0.5.4', 'https://github.com/foxcpp/maddy/security/advisories/GHSA-6cp7-g972-w9m9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24732'} | null | {'https://github.com/foxcpp/maddy/commit/7ee6a39c6a1939b376545f030a5efd6f90913583'} | {'https://github.com/foxcpp/maddy/commit/7ee6a39c6a1939b376545f030a5efd6f90913583'} |
GHSA | GHSA-rfw2-x9f8-2f6m | Cross-Site Scripting | LinkedIn Oncall through 1.4.0 allows reflected XSS via /query because of mishandling of the "No results found for" message in the search bar. | {'CVE-2021-26722'} | 2021-04-30T17:27:53Z | 2021-04-30T17:27:53Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/linkedin/oncall/issues/341', 'https://github.com/advisories/GHSA-rfw2-x9f8-2f6m', 'https://pypi.org/project/oncall/', 'https://github.com/linkedin/oncall/commit/843bc106a1c1b1699e9e52b6b0d01c7efe1d6225', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26722'} | null | {'https://github.com/linkedin/oncall/commit/843bc106a1c1b1699e9e52b6b0d01c7efe1d6225'} | {'https://github.com/linkedin/oncall/commit/843bc106a1c1b1699e9e52b6b0d01c7efe1d6225'} |
GHSA | GHSA-px3r-jm9g-c8w8 | Moderate severity vulnerability that affects rails-html-sanitizer | There is a possible XSS vulnerability in all rails-html-sanitizer gem versions below 1.0.4 for Ruby. The gem allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments, and these attributes can lead to an XSS attack on target applications. This issue is similar to CVE-2018-8048 in Loofah. All users running an affected release should either upgrade or use one of the workarounds immediately. | {'CVE-2018-3741'} | 2021-01-08T18:19:13Z | 2018-04-26T15:41:10Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3741', 'https://github.com/advisories/GHSA-px3r-jm9g-c8w8'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae'} | {'https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae'} |
GHSA | GHSA-m296-j53x-xv95 | Data races in tiny_future | `tiny_future` contains a light-weight implementation of `Future`s. The `Future`
type it has lacked bound on its `Send` and `Sync` traits.
This allows for a bug where non-thread safe types such as `Cell` can be used in
`Future`s and cause data races in concurrent programs.
The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s
`Send` and `Sync`.
| null | 2021-08-25T21:00:32Z | 2021-08-25T21:00:32Z | MODERATE | 0 | {'CWE-362'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0118.html', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39', 'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/issues/1', 'https://github.com/advisories/GHSA-m296-j53x-xv95'} | null | {'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39'} | {'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39'} |
GHSA | GHSA-crjr-9rc5-ghw8 | Inefficient Regular Expression Complexity in Nokogiri | ## Summary
Nokogiri `< v1.13.4` contains an inefficient regular expression that is susceptible to excessive backtracking when attempting to detect encoding in HTML documents.
## Mitigation
Upgrade to Nokogiri `>= 1.13.4`.
## Severity
The Nokogiri maintainers have evaluated this as [**High Severity** 7.5 (CVSS3.1)](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
## References
[CWE-1333](https://cwe.mitre.org/data/definitions/1333.html) Inefficient Regular Expression Complexity
## Credit
This vulnerability was reported by HackerOne user ooooooo_q (ななおく).
| {'CVE-2022-24836'} | 2022-04-26T18:00:11Z | 2022-04-11T21:18:06Z | HIGH | 7.5 | {'CWE-400', 'CWE-1333'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24836', 'https://github.com/advisories/GHSA-crjr-9rc5-ghw8', 'https://groups.google.com/g/ruby-security-ann/c/vX7qSjsvWis/m/TJWN4oOKBwAJ?utm_medium=email&utm_source=footer', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XMDCWRQXJQ3TFSETPCEFMQ6RR6ME5UA3/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OUPLBUZVM4WPFSXBEP2JS3R6LMKRTLFC/', 'https://github.com/sparklemotion/nokogiri/releases/tag/v1.13.4', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-crjr-9rc5-ghw8', 'https://github.com/sparklemotion/nokogiri/commit/e444525ef1634b675cd1cf52d39f4320ef0aecfd'} | null | {'https://github.com/sparklemotion/nokogiri/commit/e444525ef1634b675cd1cf52d39f4320ef0aecfd'} | {'https://github.com/sparklemotion/nokogiri/commit/e444525ef1634b675cd1cf52d39f4320ef0aecfd'} |
GHSA | GHSA-f4cj-3q3h-884r | Partial authorization bypass on document save in xwiki-platform | XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Any user with SCRIPT right (EDIT right before XWiki 7.4) can save a document with the right of the current user which allow accessing API requiring programming right if the current user has programming right. It has been patched in XWiki 13.0. The only workaround is to give SCRIPT right only to trusted users. | {'CVE-2022-23615'} | 2022-05-05T18:01:30Z | 2022-02-09T21:21:53Z | MODERATE | 5.4 | {'CWE-863'} | {'https://github.com/xwiki/xwiki-platform/commit/7ab0fe7b96809c7a3881454147598d46a1c9bbbe', 'https://github.com/advisories/GHSA-f4cj-3q3h-884r', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23615', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-f4cj-3q3h-884r', 'https://jira.xwiki.org/browse/XWIKI-5024'} | null | {'https://github.com/xwiki/xwiki-platform/commit/7ab0fe7b96809c7a3881454147598d46a1c9bbbe'} | {'https://github.com/xwiki/xwiki-platform/commit/7ab0fe7b96809c7a3881454147598d46a1c9bbbe'} |
GHSA | GHSA-6x77-rpqf-j6mw | High severity vulnerability that affects ejs | nodejs ejs version older than 2.5.5 is vulnerable to a denial-of-service due to weak input validation in the ejs.renderFile() | {'CVE-2017-1000189'} | 2021-09-02T19:10:59Z | 2018-03-05T18:54:33Z | HIGH | 7.5 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-1000189', 'https://github.com/mde/ejs/commit/49264e0037e313a0a3e033450b5c184112516d8f', 'http://www.securityfocus.com/bid/101893', 'https://github.com/advisories/GHSA-6x77-rpqf-j6mw'} | null | {'https://github.com/mde/ejs/commit/49264e0037e313a0a3e033450b5c184112516d8f'} | {'https://github.com/mde/ejs/commit/49264e0037e313a0a3e033450b5c184112516d8f'} |
GHSA | GHSA-8h4j-vm3r-vcq3 | Use after free in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free. | {'CVE-2020-35870'} | 2021-08-25T20:47:48Z | 2021-08-25T20:47:48Z | CRITICAL | 9.8 | {'CWE-416'} | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/advisories/GHSA-8h4j-vm3r-vcq3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35870'} | null | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'} | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'} |
GHSA | GHSA-gq4h-f254-7cw9 | Data races in ticketed_lock | Affected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`.
This allows to send non-Send `T` to other threads.
This can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior.
The flaw was corrected in commit a986a93 by adding `T: Send` bounds to `Send` impls of `ReadTicket<T>`/`WriteTicket<T>`.
| null | 2021-08-25T21:00:34Z | 2021-08-25T21:00:34Z | MODERATE | 0 | {'CWE-362'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0119.html', 'https://github.com/kvark/ticketed_lock/issues/7', 'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f', 'https://github.com/advisories/GHSA-gq4h-f254-7cw9'} | null | {'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f'} | {'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f'} |
GHSA | GHSA-jjv7-qpx3-h62q | Denial-of-Service Memory Exhaustion in qs | Versions prior to 1.0 of `qs` are affected by a denial of service condition. This condition is triggered by parsing a crafted string that deserializes into very large sparse arrays, resulting in the process running out of memory and eventually crashing.
## Recommendation
Update to version 1.0.0 or later. | {'CVE-2014-7191'} | 2021-09-14T19:46:49Z | 2017-10-24T18:33:36Z | HIGH | 0 | null | {'https://github.com/advisories/GHSA-jjv7-qpx3-h62q', 'https://github.com/visionmedia/node-querystring/issues/104', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/96729', 'https://access.redhat.com/errata/RHSA-2016:1380', 'http://www-01.ibm.com/support/docview.wss?uid=swg21687263', 'http://secunia.com/advisories/62170', 'https://www.npmjs.com/advisories/29', 'http://www-01.ibm.com/support/docview.wss?uid=swg21687928', 'http://secunia.com/advisories/60026', 'http://www-01.ibm.com/support/docview.wss?uid=swg21685987', 'https://nvd.nist.gov/vuln/detail/CVE-2014-7191', 'https://nodesecurity.io/advisories/qs_dos_memory_exhaustion', 'https://github.com/raymondfeng/node-querystring/commit/43a604b7847e56bba49d0ce3e222fe89569354d8'} | null | {'https://github.com/raymondfeng/node-querystring/commit/43a604b7847e56bba49d0ce3e222fe89569354d8'} | {'https://github.com/raymondfeng/node-querystring/commit/43a604b7847e56bba49d0ce3e222fe89569354d8'} |
GHSA | GHSA-gwpf-62xp-vrg6 | Information Exposure in cordova-android | Versions of `cordova-android` prior to 6.0.0 are vulnerable to Information Exposure through log files. The application calls methods of the Log class. Messages passed to these methods (Log.v(), Log.d(), Log.i(), Log.w(), and Log.e()) are stored in a series of circular buffers on the device. By default, a maximum of four 16 KB rotated logs are kept in addition to the current log. The logged data can be read using Logcat on the device. When using platforms prior to Android 4.1 (Jelly Bean), the log data is not sandboxed per application; any application installed on the device has the capability to read data logged by other applications.
## Recommendation
Upgrade to version 6.0.0 or later. | {'CVE-2016-6799'} | 2021-09-28T16:53:05Z | 2020-09-11T21:14:49Z | HIGH | 7.5 | {'CWE-532'} | {'http://www.securityfocus.com/bid/98365', 'https://snyk.io/vuln/SNYK-JS-CORDOVAANDROID-174935', 'https://github.com/apache/cordova-android/commit/4a0a7bc424fae14c9689f4a8a2dc250ae3a47f82', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6799', 'https://nvd.nist.gov/vuln/detail/CVE-2016-6799', 'https://github.com/advisories/GHSA-gwpf-62xp-vrg6', 'https://www.npmjs.com/advisories/964', 'https://lists.apache.org/thread.html/1f3e7b0319d64b455f73616f572acee36fbca31f87f5b2e509c45b69@%3Cdev.cordova.apache.org%3E'} | null | {'https://github.com/apache/cordova-android/commit/4a0a7bc424fae14c9689f4a8a2dc250ae3a47f82'} | {'https://github.com/apache/cordova-android/commit/4a0a7bc424fae14c9689f4a8a2dc250ae3a47f82'} |
GHSA | GHSA-gg84-qgv9-w4pq | CRLF injection in httplib2 | ### Impact
Attacker controlling unescaped part of uri for `httplib2.Http.request()` could change request headers and body, send additional hidden requests to same server.
Impacts software that uses httplib2 with uri constructed by string concatenation, as opposed to proper urllib building with escaping.
### Patches
Problem has been fixed in 0.18.0
Space, CR, LF characters are now quoted before any use.
This solution should not impact any valid usage of httplib2 library, that is uri constructed by urllib.
### Workarounds
Create URI with `urllib.parse` family functions: `urlencode`, `urlunsplit`.
```diff
user_input = " HTTP/1.1\r\ninjected: attack\r\nignore-http:"
-uri = "https://api.server/?q={}".format(user_input)
+uri = urllib.parse.urlunsplit(("https", "api.server", "/v1", urllib.parse.urlencode({"q": user_input}), ""))
http.request(uri)
```
### References
https://cwe.mitre.org/data/definitions/93.html
https://docs.python.org/3/library/urllib.parse.html
Thanks to Recar https://github.com/Ciyfly for finding vulnerability and discrete notification.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [httplib2](https://github.com/httplib2/httplib2/issues/new)
* Email [current maintainer at 2020-05](mailto:temotor@gmail.com) | {'CVE-2020-11078'} | 2022-04-19T19:02:26Z | 2020-05-20T15:55:47Z | LOW | 6.8 | {'CWE-93'} | {'https://lists.debian.org/debian-lts-announce/2020/06/msg00000.html', 'https://lists.apache.org/thread.html/rad8872fc99f670958c2774e2bf84ee32a3a0562a0c787465cf3dfa23@%3Cissues.beam.apache.org%3E', 'https://lists.apache.org/thread.html/r23711190c2e98152cb6f216b95090d5eeb978543bb7e0bad22ce47fc@%3Cissues.beam.apache.org%3E', 'https://lists.apache.org/thread.html/rc9eff9572946142b657c900fe63ea4bbd3535911e8d4ce4d08fe4b89@%3Ccommits.allura.apache.org%3E', 'https://lists.apache.org/thread.html/r7f364000066748299b331b615ba51c62f55ab5b201ddce9a22d98202@%3Cissues.beam.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IXCX2AWROGWGY5GXR7VN3BKF34A2FO6J/', 'https://lists.apache.org/thread.html/r69a462e690b5f2c3d418a288a2c98ae764d58587bd0b5d6ab141f25f@%3Cissues.beam.apache.org%3E', 'https://lists.apache.org/thread.html/r4d35dac106fab979f0db75a07fc4e320ad848b722103e79667ff99e1@%3Cissues.beam.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11078', 'https://github.com/advisories/GHSA-gg84-qgv9-w4pq', 'https://github.com/httplib2/httplib2/security/advisories/GHSA-gg84-qgv9-w4pq', 'https://github.com/httplib2/httplib2/commit/a1457cc31f3206cf691d11d2bf34e98865873e9e', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PZJ3D6JSM7CFZESZZKGUW2VX55BOSOXI/'} | null | {'https://github.com/httplib2/httplib2/commit/a1457cc31f3206cf691d11d2bf34e98865873e9e'} | {'https://github.com/httplib2/httplib2/commit/a1457cc31f3206cf691d11d2bf34e98865873e9e'} |
GHSA | GHSA-8fxw-76px-3rxv | Memory leak in Tensorflow | ### Impact
If a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L100-L104
The allocated memory is from
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L256
The issue occurs because the `status` argument during validation failures is not properly checked:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267
Since each of the above methods can return an error status, the `status` value must be checked before continuing.
### Patches
We have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions.
We recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been discovered during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v). | {'CVE-2020-15192'} | 2021-08-26T15:09:35Z | 2020-09-25T18:28:17Z | MODERATE | 4.3 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15192', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/advisories/GHSA-8fxw-76px-3rxv', 'https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8'} | {'https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8'} |
GHSA | GHSA-3c9c-2p65-qvwv | Prototype pollution in aurelia-path | ### Impact
The vulnerability exposes Aurelia application that uses `aurelia-path` package to parse a string. The majority of this will be Aurelia applications that employ the `aurelia-router` package. An example is this could allow an attacker to change the prototype of base object class `Object` by tricking an application to parse the following URL: `https://aurelia.io/blog/?__proto__[asdf]=asdf`
### Patches
The problem should be patched in version `1.1.7`. Any version earlier than this is vulnerable.
### Workarounds
A partial work around is to free the Object prototype:
```ts
Object.freeze(Object.prototype)
``` | {'CVE-2021-41097'} | 2022-04-19T19:03:10Z | 2021-09-27T20:12:16Z | HIGH | 9.1 | {'CWE-1321', 'CWE-915'} | {'https://github.com/aurelia/path/commit/7c4e235433a4a2df9acc313fbe891758084fdec1', 'https://www.npmjs.com/package/aurelia-path', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41097', 'https://github.com/advisories/GHSA-3c9c-2p65-qvwv', 'https://github.com/aurelia/path/security/advisories/GHSA-3c9c-2p65-qvwv', 'https://github.com/aurelia/path/issues/44', 'https://github.com/aurelia/path/releases/tag/1.1.7'} | null | {'https://github.com/aurelia/path/commit/7c4e235433a4a2df9acc313fbe891758084fdec1'} | {'https://github.com/aurelia/path/commit/7c4e235433a4a2df9acc313fbe891758084fdec1'} |
GHSA | GHSA-36m2-8rhx-f36j | Sandbox bypass in Latte templates | ### Impact
The problem affects users who use the sandbox in Latte and templates from untrusted sources.
### Patches
Sandbox first appeared in Latte 2.8.0. The issue is fixed in the versions 2.8.8, 2.9.6 and 2.10.8.
### References
The issues were discovered by
- JinYiTong (https://github.com/JinYiTong)
- 赵钰迪 <20212010122@fudan.edu.cn> | {'CVE-2022-21648'} | 2022-04-19T19:03:19Z | 2022-01-06T23:17:07Z | HIGH | 8.2 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21648', 'https://github.com/advisories/GHSA-36m2-8rhx-f36j', 'https://github.com/nette/latte/security/advisories/GHSA-36m2-8rhx-f36j', 'https://github.com/nette/latte/commit/9e1b4f7d70f7a9c3fa6753ffa7d7e450a3d4abb0'} | null | {'https://github.com/nette/latte/commit/9e1b4f7d70f7a9c3fa6753ffa7d7e450a3d4abb0'} | {'https://github.com/nette/latte/commit/9e1b4f7d70f7a9c3fa6753ffa7d7e450a3d4abb0'} |
GHSA | GHSA-66q9-f7ff-mmx6 | Local file inclusion vulnerability in http4s | ### Impact
This vulnerability applies to all users of:
* `org.http4s.server.staticcontent.FileService`
* `org.http4s.server.staticcontent.ResourceService`
* `org.http4s.server.staticcontent.WebjarService`
#### Path escaping
URI normalization is applied incorrectly. Requests whose path info contain `../` or `//` can expose resources outside of the configured location. Specifically:
* `FileService` may expose any file on the local file system.
* `ResourceService` may expose any resource on the class path.
#### Prefix matching
When the service is configured with a non-empty `pathPrefix` that doesn't end in a slash, any directories whose names are a prefix of `systemPath` (from `FileService`) or `pathPrefix` (from `ResourceService`) are exposed. For example, if `pathPrefix` is `/foo` and `systemPath` is `/bar`, a request to `/foobaz/quux.txt` exposes file `/barbaz/quux.txt`, when only files beneath `/bar` should be available.
#### URI decoding
URI segments are not decoded before resource resolution. This causes resources with reserved characters in their name to incorrectly return a 404. It also may incorrectly expose the rare resource whose name is URI encoded. This applies to `FileService`, `ResourceService`, and `WebjarService`.
### Patches
In all three services, paths with an empty segment, a `.` segment, or a `..` segment are now rejected with a `400 Bad Request` response. This fixes exposure outside the configured root. Many clients already eliminate dot segments according to the rules in [RFC3986, Section 5.2.4](https://tools.ietf.org/html/rfc3986#section-5.2.4). A middleware that does so at the server level may be considered if there is demand.
If `pathInfo` is non-empty, and does not begin with `/`, then a 404 response is generated. This fixes the prefix matching exposure.
All path segments are URI decoded before being passed to the file system or resource path. This allows resolution of resources with reserved characters in the name, and prevents incorrect exposure of resources whose names are themselves URI encoded.
### Workarounds
The recommended course is to upgrade:
* v0.18.26, binary compatible with the 0.18.x series
* v0.20.20, binary compatible with the 0.20.x series
* v0.21.2, binary compatible with the 0.21.x series
Note that 0.19.0 is a deprecated release and has never been supported.
If an upgrade is impossible:
* Temporarily copy `FileService.scala`, `ResourceService.scala`, and `WebjarService.scala` from the appropriate release series into your project and recompile with that, changing the package name and reference in your application.
* Users of a servlet backend can use the servlet container's file serving capabilities.
### Credits
Thank you to Thomas Gøytil for the discovery, responsible disclosure, and assistance testing of this vulnerability.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [http4s/http4s](http://github.com/http4s/http4s)
* Email a maintainer:
* [Ross A. Baker](mailto:ross@rossabaker.com) | {'CVE-2020-5280'} | 2021-01-14T17:48:19Z | 2020-03-25T17:35:51Z | CRITICAL | 7.6 | {'CWE-23'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5280', 'https://github.com/http4s/http4s/commit/752b3f63a05a31d2de4f8706877aa08d6b89efca', 'https://github.com/http4s/http4s/commit/250afddbb2e65b70ca9ddaec9d1eb3aaa56de7ec', 'https://github.com/advisories/GHSA-66q9-f7ff-mmx6', 'https://github.com/http4s/http4s/security/advisories/GHSA-66q9-f7ff-mmx6', 'https://github.com/http4s/http4s/commit/b87f31b2292dabe667bec3b04ce66176c8a3e17b'} | null | {'https://github.com/http4s/http4s/commit/b87f31b2292dabe667bec3b04ce66176c8a3e17b', 'https://github.com/http4s/http4s/commit/250afddbb2e65b70ca9ddaec9d1eb3aaa56de7ec', 'https://github.com/http4s/http4s/commit/752b3f63a05a31d2de4f8706877aa08d6b89efca'} | {'https://github.com/http4s/http4s/commit/250afddbb2e65b70ca9ddaec9d1eb3aaa56de7ec', 'https://github.com/http4s/http4s/commit/752b3f63a05a31d2de4f8706877aa08d6b89efca', 'https://github.com/http4s/http4s/commit/b87f31b2292dabe667bec3b04ce66176c8a3e17b'} |
GHSA | GHSA-47wr-426j-fr82 | Symbolic links in an unpacking routine may enable attackers to read and/or write to arbitrary locations in dbdeployer | ### Impact
_Users unpacking a tarball through dbdeployer may use a maliciously packaged tarball that contains symlinks to files external to the target. In such scenario, an attacker could induce dbdeployer to write into a system file, thus altering the computer defences._
### Mitigating factors
For the attach to succeed, the following factors need to contribute:
* The user is logged in as root. While dbdeployer is usable as root, it was designed to run as unprivileged user.
* The user has taken a tarball from a non secure source, without testing the checksum. When the tarball is retrieved through dbdeployer, the checksum is compared before attempting to unpack.
### Analysis
An attacker could inject a symbolic link into the tarball, so that a file could result into `fake_file -> /etc/passwd` or some equally important file.
As it is now, dbdeployer would create the symlink as defined, with a local file `fake_file` linked to `/etc/passwd`. The danger here is that any process with the privileges to write to both `fake_file` and `/etc/passwd` could overwrite the system file. Even without malicious intent, this could result in the system to become unusable.
As noted above, the user must have write privileges to the target file to do the damage.
### Remedies
It has been suggested that the extract procedure use `filepath.EvalSymlinks` to determine whether the target is within the extraction directory. Unfortunately, this approach is unavailable in this context, because it would prevent legitimate patterns from being carried out.
A simple case is a file `mysql-8.0.22-macos10.15-x86_64/bin/libprotobuf-lite.3.11.4.dylib` with a linkName `../lib/libprotobuf-lite.3.11.4.dylib`, if the linked file has not been created yet, `filepath.EvalSymlinks` would fail, as it acts on existing files only.
An alternative method is comparing the depth (how many directories) of the file name with the depth of the link name. If the link name has a higher depth than the local file, we block the operation with an appropriate error:
```
Unpacking tarball exploit/mysql-8.0.22-macos10.15-x86_64.tar.gz to $HOME/opt/mysql/test8.0.22
......
link '../../../../../../../../../../etc' points outside target directory
exit status 1
```
As an additional fortifier, we can check whether the link points to an existing file, calculate its absolute name, and compare it with the absolute name of the extraction directory. A link to a full path (such as `/etc/passwd`) would fail this test, and trigger an error.
The same check can be applied to a link to a non existing file with absolute path.
### Patches
Patched in release 1.58.2
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [dbdeployer](https://github.com/datacharmer/dbdeployer) | {'CVE-2020-26277'} | 2022-04-19T19:02:43Z | 2022-02-12T00:14:07Z | MODERATE | 6.1 | {'CWE-59'} | {'https://github.com/datacharmer/dbdeployer/security/advisories/GHSA-47wr-426j-fr82', 'https://github.com/advisories/GHSA-47wr-426j-fr82', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26277', 'https://github.com/datacharmer/dbdeployer/commit/548e256c1de2f99746e861454e7714ec6bc9bb10'} | null | {'https://github.com/datacharmer/dbdeployer/commit/548e256c1de2f99746e861454e7714ec6bc9bb10'} | {'https://github.com/datacharmer/dbdeployer/commit/548e256c1de2f99746e861454e7714ec6bc9bb10'} |
GHSA | GHSA-pxpf-v376-7xx5 | tagify can pass a malicious placeholder to initiate the cross-site scripting (XSS) payload | This affects the package @yaireo/tagify before 4.9.8. The package is used for rendering UI components inside the input or text fields, and an attacker can pass a malicious placeholder value to it to fire the cross-site scripting (XSS) payload. | {'CVE-2022-25854'} | 2022-05-03T04:55:33Z | 2022-04-30T00:00:33Z | MODERATE | 0 | null | {'https://github.com/yairEO/tagify/issues/988', 'https://snyk.io/vuln/SNYK-JS-YAIREOTAGIFY-2404358', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25854', 'https://github.com/yairEO/tagify/commit/198c0451fad188390390395ccfc84ab371def4c7', 'https://github.com/yairEO/tagify/releases/tag/v4.9.8', 'https://github.com/advisories/GHSA-pxpf-v376-7xx5'} | null | {'https://github.com/yairEO/tagify/commit/198c0451fad188390390395ccfc84ab371def4c7'} | {'https://github.com/yairEO/tagify/commit/198c0451fad188390390395ccfc84ab371def4c7'} |
GHSA | GHSA-7gcp-w6ww-2xv9 | Path traversal and files overwrite with unsquashfs in singularity | ### Impact
Due to insecure handling of path traversal and the lack of path sanitization within `unsquashfs` (a distribution provided utility used by Singularity), it is possible to overwrite/create any files on the host filesystem during the extraction of a crafted squashfs filesystem.
Squashfs extraction occurs automatically for unprivileged execution of Singularity (either `--without-suid` installation or with `allow setuid = no`) when a user attempts to run an image which:
- is a local SIF image or a single file containing a squashfs filesystem
- is pulled from remote sources `library://` or `shub://`
Image build is also impacted in a more serious way as it is often performed by the root user, allowing an attacker to overwrite/create files leading to a system compromise. Bootstrap methods `library`, `shub` and `localimage` trigger a squashfs extraction.
### Patches
This issue is addressed in Singularity 3.6.4.
All users are advised to upgrade to 3.6.4 especially if they use Singularity mainly for building image as root user.
### Workarounds
There is no solid workaround except to temporarily avoid use of unprivileged mode with single file images, in favor of sandbox images instead. Regarding image build, temporarily avoid building from `library` and `shub` sources, and as much as possible use `--fakeroot` or a VM to limit potential impact.
### For more information
General questions about the impact of the advisory / changes made in the 3.6.0 release can be asked in the:
* [Singularity Slack Channel](https://bit.ly/2m0g3lX)
* [Singularity Mailing List](https://groups.google.com/a/lbl.gov/forum/??sdf%7Csort:date#!forum/singularity)
Any sensitive security concerns should be directed to: security@sylabs.io
See our Security Policy here: https://sylabs.io/security-policy | {'CVE-2020-15229'} | 2022-04-19T19:02:36Z | 2021-05-24T16:59:53Z | HIGH | 8.2 | {'CWE-22'} | {'https://github.com/hpcng/singularity/blob/v3.6.4/CHANGELOG.md#security-related-fixes', 'https://github.com/hpcng/singularity/pull/5611', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00070.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15229', 'https://github.com/hpcng/singularity/security/advisories/GHSA-7gcp-w6ww-2xv9', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00071.html', 'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e', 'http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00009.html', 'https://github.com/advisories/GHSA-7gcp-w6ww-2xv9'} | null | {'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e'} | {'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e'} |
GHSA | GHSA-cjvr-mfj7-j4j8 | Incorrect Authorization and Exposure of Sensitive Information to an Unauthorized Actor in scrapy | ### Impact
If you manually define cookies on a [`Request`](https://docs.scrapy.org/en/latest/topics/request-response.html#scrapy.http.Request) object, and that `Request` object gets a redirect response, the new `Request` object scheduled to follow the redirect keeps those user-defined cookies, regardless of the target domain.
### Patches
Upgrade to Scrapy 2.6.0, which resets cookies when creating `Request` objects to follow redirects¹, and drops the ``Cookie`` header if manually-defined if the redirect target URL domain name does not match the source URL domain name².
If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.6.0 is not an option, you may upgrade to Scrapy 1.8.2 instead.
¹ At that point the original, user-set cookies have been processed by the cookie middleware into the global or request-specific cookiejar, with their domain restricted to the domain of the original URL, so when the cookie middleware processes the new (redirect) request it will incorporate those cookies into the new request as long as the domain of the new request matches the domain of the original request.
² This prevents cookie leaks to unintended domains even if the cookies middleware is not used.
### Workarounds
If you cannot upgrade, set your cookies using a list of dictionaries instead of a single dictionary, as described in the [`Request` documentation](https://docs.scrapy.org/en/latest/topics/request-response.html#scrapy.http.Request), and set the right domain for each cookie.
Alternatively, you can [disable cookies altogether](https://docs.scrapy.org/en/latest/topics/downloader-middleware.html#std-setting-COOKIES_ENABLED), or [limit target domains](https://docs.scrapy.org/en/latest/topics/spiders.html#scrapy.spiders.Spider.allowed_domains) to domains that you trust with all your user-set cookies.
### References
* Originally reported at [huntr.dev](https://huntr.dev/bounties/3da527b1-2348-4f69-9e88-2e11a96ac585/)
### For more information
If you have any questions or comments about this advisory:
* [Open an issue](https://github.com/scrapy/scrapy/issues)
* [Email us](mailto:opensource@zyte.com) | {'CVE-2022-0577'} | 2022-04-05T18:51:14Z | 2022-03-01T22:12:47Z | MODERATE | 6.5 | {'CWE-200', 'CWE-863'} | {'https://github.com/advisories/GHSA-cjvr-mfj7-j4j8', 'https://github.com/scrapy/scrapy/commit/8ce01b3b76d4634f55067d6cfdf632ec70ba304a', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00021.html', 'https://github.com/scrapy/scrapy/security/advisories/GHSA-cjvr-mfj7-j4j8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0577', 'https://github.com/pypa/advisory-database/tree/main/vulns/scrapy/PYSEC-2022-159.yaml', 'https://huntr.dev/bounties/3da527b1-2348-4f69-9e88-2e11a96ac585'} | null | {'https://github.com/scrapy/scrapy/commit/8ce01b3b76d4634f55067d6cfdf632ec70ba304a'} | {'https://github.com/scrapy/scrapy/commit/8ce01b3b76d4634f55067d6cfdf632ec70ba304a'} |
GHSA | GHSA-92vm-mxjf-jqf3 | Improper Verification of Cryptographic Signature in starkbank-ecdsa | The `verify` function in the Stark Bank Python ECDSA library (starkbank-ecdsa) 2.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages. | {'CVE-2021-43572'} | 2022-03-29T22:08:01Z | 2021-11-10T20:41:39Z | CRITICAL | 9.8 | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43572', 'https://github.com/starkbank/ecdsa-python/commit/d136170666e9510eb63c2572551805807bd4c17f', 'https://github.com/advisories/GHSA-92vm-mxjf-jqf3', 'https://research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries/', 'https://github.com/starkbank/ecdsa-python/releases/tag/v2.0.1'} | null | {'https://github.com/starkbank/ecdsa-python/commit/d136170666e9510eb63c2572551805807bd4c17f'} | {'https://github.com/starkbank/ecdsa-python/commit/d136170666e9510eb63c2572551805807bd4c17f'} |
GHSA | GHSA-vm67-7vmg-66vm | Arbitrary Command Injection in portprocesses | ### Impact
An Arbitrary Command Injection vulnerability was reported in `portprocesses` impacting versions <= 1.0.4.
### Example (Proof of Concept)
The following example demonstrates the vulnerability and will run `touch success` therefore creating a file named `success`.
```js
const portprocesses = require("portprocesses");
portprocesses.killProcess("$(touch success)");
``` | {'CVE-2021-23348'} | 2022-04-19T19:02:49Z | 2021-04-06T17:24:50Z | MODERATE | 6.4 | {'CWE-77', 'CWE-78'} | {'https://github.com/rrainn/PortProcesses/security/advisories/GHSA-vm67-7vmg-66vm', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23348', 'https://github.com/rrainn/PortProcesses/blob/fffceb09aff7180afbd0bd172e820404b33c8299/index.js%23L23', 'https://github.com/rrainn/PortProcesses/commit/86811216c9b97b01b5722f879f8c88a7aa4214e1', 'https://snyk.io/vuln/SNYK-JS-PORTPROCESSES-1078536', 'https://github.com/advisories/GHSA-vm67-7vmg-66vm'} | null | {'https://github.com/rrainn/PortProcesses/commit/86811216c9b97b01b5722f879f8c88a7aa4214e1'} | {'https://github.com/rrainn/PortProcesses/commit/86811216c9b97b01b5722f879f8c88a7aa4214e1'} |
GHSA | GHSA-6635-c626-vj4r | Command Injection Vulnerability with Mercurial in VCS | URLs and local file paths passed to the Mercurial (hg) APIs that are specially crafted can contain commands which are executed by Mercurial if it is installed on the host operating system. The `vcs` package uses the underly version control system, in this case `hg`, to implement the needed functionality. When `hg` is executed, argument strings are passed to `hg` in a way that additional flags can be set. The additional flags can be used to perform a command injection. Other version control systems with an implemented interface may also be vulnerable. The issue has been fixed in version 1.13.2. A work around is to sanitize data passed to the `vcs` package APIs to ensure it does not contain commands or unexpected data. This is important for user input data that is passed directly to the package APIs. | {'CVE-2022-21235'} | 2022-04-18T21:47:33Z | 2022-04-01T14:05:33Z | CRITICAL | 9.8 | {'CWE-88', 'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21235', 'https://github.com/Masterminds/vcs/commit/922a5122330ea8fbe56352a0172ddb6bf019cd22', 'https://github.com/advisories/GHSA-6635-c626-vj4r', 'https://github.com/Masterminds/vcs/security/advisories/GHSA-6635-c626-vj4r', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMASTERMINDSVCS-2437078', 'https://github.com/Masterminds/vcs/pull/105', 'https://github.com/Masterminds/vcs/releases/tag/v1.13.2'} | null | {'https://github.com/Masterminds/vcs/commit/922a5122330ea8fbe56352a0172ddb6bf019cd22'} | {'https://github.com/Masterminds/vcs/commit/922a5122330ea8fbe56352a0172ddb6bf019cd22'} |
GHSA | GHSA-q42q-523g-3fwv | Cross-Site Request Forgery | This affects the package com.softwaremill.akka-http-session:core_2.13 before 0.5.11; the package com.softwaremill.akka-http-session:core_2.12 before 0.5.11; the package com.softwaremill.akka-http-session:core_2.11 before 0.5.11. For older versions, endpoints protected by randomTokenCsrfProtection could be bypassed with an empty X-XSRF-TOKEN header and an empty XSRF-TOKEN cookie. | {'CVE-2020-7780'} | 2022-02-09T23:06:40Z | 2022-02-09T23:06:40Z | MODERATE | 8.8 | {'CWE-352'} | {'https://github.com/softwaremill/akka-http-session/issues/77', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7780', 'https://snyk.io/vuln/SNYK-JAVA-COMSOFTWAREMILLAKKAHTTPSESSION-1045352', 'https://github.com/advisories/GHSA-q42q-523g-3fwv', 'https://github.com/softwaremill/akka-http-session/commit/57f11663eecb84be03383d164f655b9c5f953b41', 'https://snyk.io/vuln/SNYK-JAVA-COMSOFTWAREMILLAKKAHTTPSESSION-1046655', 'https://snyk.io/vuln/SNYK-JAVA-COMSOFTWAREMILLAKKAHTTPSESSION-1046654', 'https://github.com/softwaremill/akka-http-session/issues/74'} | null | {'https://github.com/softwaremill/akka-http-session/commit/57f11663eecb84be03383d164f655b9c5f953b41'} | {'https://github.com/softwaremill/akka-http-session/commit/57f11663eecb84be03383d164f655b9c5f953b41'} |
GHSA | GHSA-pwqf-9h7j-7mv8 | Incorrect threshold signature computation in TUF | ### Impact
Metadadata signature verification, as used in `tuf.client.updater`, counted each of multiple signatures with identical authorized keyids separately towards the threshold. Therefore, an attacker with access to a valid signing key could create multiple valid signatures in order to meet the minimum threshold of keys before the metadata was considered valid.
The tuf maintainers would like to thank Erik MacLean of Analog Devices, Inc. for reporting this issue.
### Patches
A [fix](https://github.com/theupdateframework/tuf/pull/974) is available in version [0.12.2](https://github.com/theupdateframework/tuf/releases/tag/v0.12.2) or newer.
### Workarounds
No workarounds are known for this issue.
### References
* [CVE-2020-6174](https://nvd.nist.gov/vuln/detail/CVE-2020-6174)
* Pull request resolving the issue [PR 974](https://github.com/theupdateframework/tuf/pull/974) | {'CVE-2020-6174'} | 2022-03-23T23:02:07Z | 2020-08-21T16:25:26Z | CRITICAL | 9.8 | {'CWE-347'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-6174', 'https://github.com/theupdateframework/tuf/security/advisories/GHSA-pwqf-9h7j-7mv8', 'https://github.com/theupdateframework/tuf/pull/974/commits/a0397c7c820ec1c30ebc793cc9469b61c8d3f50e', 'https://github.com/advisories/GHSA-pwqf-9h7j-7mv8', 'https://github.com/theupdateframework/tuf/pull/974'} | null | {'https://github.com/theupdateframework/tuf/pull/974/commits/a0397c7c820ec1c30ebc793cc9469b61c8d3f50e'} | {'https://github.com/theupdateframework/tuf/pull/974/commits/a0397c7c820ec1c30ebc793cc9469b61c8d3f50e'} |
GHSA | GHSA-23r4-5mxp-c7g5 | New anonymous user session acts as if it's created with password | ### Impact
Developers that use the REST API to signup users and also allow users to login anonymously. When an anonymous user is first signed up using REST, the server creates session incorrectly, particularly the `authProvider` field in `_Session` class under `createdWith` shows the user logged in creating a password. If a developer later depends on the `createdWith` field to provide a different level of access between a password user and anonymous user, the server incorrectly classified the session type as being created with a `password`.
The server currently doesn't use `createdWith` to make decisions on how things work internally, so if a developer isn't using `createdWith` directly, there's nothing to worry about. The vulnerability only affects users who depend on `createdWith` by using it directly.
### Patches
Upgrade to version 4.5.1.
### Workarounds
Don't use the `createdWith` Session field to make decisions if you allow anonymous login.
### References
n/a | {'CVE-2021-39138'} | 2022-04-19T19:02:51Z | 2021-08-23T19:41:52Z | MODERATE | 4.8 | {'CWE-287'} | {'https://github.com/parse-community/parse-server/security/advisories/GHSA-23r4-5mxp-c7g5', 'https://github.com/parse-community/parse-server/releases/tag/4.5.2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39138', 'https://github.com/parse-community/parse-server/commit/147bd9a3dc43391e92c36e05d5db860b04ca27db', 'https://github.com/advisories/GHSA-23r4-5mxp-c7g5'} | null | {'https://github.com/parse-community/parse-server/commit/147bd9a3dc43391e92c36e05d5db860b04ca27db'} | {'https://github.com/parse-community/parse-server/commit/147bd9a3dc43391e92c36e05d5db860b04ca27db'} |
GHSA | GHSA-wc73-w5r9-x9pc | Cross-site Scripting in XXL-JOB | XXL-JOB 2.2.0 allows Stored XSS (in Add User) to bypass the 20-character limit via xxl-job-admin/src/main/java/com/xxl/job/admin/controller/UserController.java. | {'CVE-2020-29204'} | 2021-10-12T16:41:36Z | 2021-10-12T16:41:36Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-29204', 'https://github.com/advisories/GHSA-wc73-w5r9-x9pc', 'https://github.com/xuxueli/xxl-job/issues/2083', 'https://github.com/xuxueli/xxl-job/commit/227628567354d3c156951009d683c6fec3006e0e'} | null | {'https://github.com/xuxueli/xxl-job/commit/227628567354d3c156951009d683c6fec3006e0e'} | {'https://github.com/xuxueli/xxl-job/commit/227628567354d3c156951009d683c6fec3006e0e'} |
GHSA | GHSA-4fr2-j4g9-mppf | Improperly Controlled Modification of Dynamically-Determined Object Attributes in deephas | Prototype pollution vulnerability in 'deephas' versions 1.0.0 through 1.0.5 allows attacker to cause a denial of service and may lead to remote code execution. | {'CVE-2020-28271'} | 2021-09-24T15:42:21Z | 2021-09-24T15:42:21Z | CRITICAL | 9.8 | {'CWE-915'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28271', 'https://github.com/sharpred/deepHas/commit/2fe011713a6178c50f7deb6f039a8e5435981e20', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28271,', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2020-28271', 'https://github.com/advisories/GHSA-4fr2-j4g9-mppf'} | null | {'https://github.com/sharpred/deepHas/commit/2fe011713a6178c50f7deb6f039a8e5435981e20'} | {'https://github.com/sharpred/deepHas/commit/2fe011713a6178c50f7deb6f039a8e5435981e20'} |
GHSA | GHSA-fpv6-f8jw-rc3r | Remote code execution via the web UI backend | ### Impact
Elvish's backend for the experimental web UI (started by `elvish -web`) hosts an endpoint that allows executing the code sent from the web UI.
The backend does not check the origin of requests correctly. As a result, if the user has the web UI backend open and visits a compromised or malicious website, the website can send arbitrary code to the endpoint in localhost.
### Patches
All Elvish releases since 0.14.0 no longer include the experimental web UI, although it is still possible for the user to build a version from source that includes it.
The issue can be patched for previous versions by removing the web UI (found in web, pkg/web or pkg/prog/web, depending on the exact version).
### Workarounds
Do not use the experimental web UI.
### For more information
If you have any questions or comments about this advisory, please email xiaqqaix@gmail.com. | {'CVE-2021-41088'} | 2022-04-19T19:03:09Z | 2021-09-23T23:17:33Z | MODERATE | 8 | {'CWE-668'} | {'https://github.com/advisories/GHSA-fpv6-f8jw-rc3r', 'https://github.com/elves/elvish/security/advisories/GHSA-fpv6-f8jw-rc3r', 'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41088'} | null | {'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5'} | {'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5'} |
GHSA | GHSA-p24j-h477-76q3 | Uncontrolled Search Path Element in sharkdp/bat | bat on windows before 0.18.2 executes programs named less.exe from the current working directory. This can lead to unintended code execution. | {'CVE-2021-36753'} | 2021-09-09T16:57:53Z | 2021-08-25T21:01:37Z | HIGH | 7.8 | {'CWE-427'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-36753', 'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956', 'https://github.com/sharkdp/bat/releases/tag/v0.18.2', 'https://github.com/sharkdp/bat/pull/1724', 'https://github.com/advisories/GHSA-p24j-h477-76q3', 'https://vuln.ryotak.me/advisories/53'} | null | {'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956'} | {'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956'} |
GHSA | GHSA-3r8j-pmch-5j2h | Internal exception message exposure for login action in Sylius | ## Internal exception message exposure for login action
### Impact
Exception messages from internal exceptions (like database exception) are wrapped by `\Symfony\Component\Security\Core\Exception\AuthenticationServiceException` and propagated through the system to UI. Therefore, some internal system information may leak and be visible to the customer.
A validation message with the exception details will be presented to the user when one will try to log into the shop.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
### Workarounds
The `src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig` file should be overridden and lines https://github.com/Sylius/Sylius/blob/1.4/src/Sylius/Bundle/UiBundle/Resources/views/Security/_login.html.twig#L13-L17 should be replaced with
```twig
{% if last_error %}
<div class="ui left aligned basic segment">
{{ messages.error(last_error.messageKey) }}
</div>
{% endif %}
```
The `messageKey` field should be used instead of the `message`. | {'CVE-2019-16768'} | 2021-01-08T21:20:33Z | 2019-12-05T19:57:04Z | LOW | 3.5 | {'CWE-209'} | {'https://github.com/Sylius/Sylius/commit/be245302dfc594d8690fe50dd47631d186aa945f', 'https://github.com/Sylius/Sylius/security/advisories/GHSA-3r8j-pmch-5j2h', 'https://github.com/advisories/GHSA-3r8j-pmch-5j2h', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16768'} | null | {'https://github.com/Sylius/Sylius/commit/be245302dfc594d8690fe50dd47631d186aa945f'} | {'https://github.com/Sylius/Sylius/commit/be245302dfc594d8690fe50dd47631d186aa945f'} |
GHSA | GHSA-4w2v-q235-vp99 | Server-Side Request Forgery in Axios | Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address. | {'CVE-2020-28168'} | 2021-01-29T20:58:12Z | 2021-01-04T20:59:40Z | HIGH | 0 | {'CWE-918'} | {'https://www.npmjs.com/package/axios', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28168', 'https://www.npmjs.com/advisories/1594', 'https://snyk.io/vuln/SNYK-JS-AXIOS-1038255', 'https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55', 'https://lists.apache.org/thread.html/rdfd2901b8b697a3f6e2c9c6ecc688fd90d7f881937affb5144d61d6e@%3Ccommits.druid.apache.org%3E', 'https://github.com/axios/axios/issues/3369', 'https://github.com/advisories/GHSA-4w2v-q235-vp99', 'https://lists.apache.org/thread.html/r25d53acd06f29244b8a103781b0339c5e7efee9099a4d52f0c230e4a@%3Ccommits.druid.apache.org%3E', 'https://lists.apache.org/thread.html/r954d80fd18e9dafef6e813963eb7e08c228151c2b6268ecd63b35d1f@%3Ccommits.druid.apache.org%3E'} | null | {'https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55'} | {'https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55'} |
GHSA | GHSA-gwcx-jrx4-92w2 | Segfault in `simplifyBroadcast` in Tensorflow | ### Impact
The [`simplifyBroadcast` function in the MLIR-TFRT infrastructure in TensorFlow](https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/compiler/mlir/tfrt/jit/transforms/tf_cpurt_symbolic_shape_optimization.cc#L149-L205) is vulnerable to a segfault (hence, denial of service), if called with scalar shapes.
```cc
size_t maxRank = 0;
for (auto shape : llvm::enumerate(shapes)) {
auto found_shape = analysis.dimensionsForShapeTensor(shape.value());
if (!found_shape) return {};
shapes_found.push_back(*found_shape);
maxRank = std::max(maxRank, found_shape->size());
}
SmallVector<const ShapeComponentAnalysis::SymbolicDimension*>
joined_dimensions(maxRank);
```
If all shapes are scalar, then `maxRank` is 0, so we build an empty `SmallVector`.
### Patches
We have patched the issue in GitHub commit [35f0fabb4c178253a964d7aabdbb15c6a398b69a](https://github.com/tensorflow/tensorflow/commit/35f0fabb4c178253a964d7aabdbb15c6a398b69a).
The fix will be included in TensorFlow 2.8.0. This is the only affected version.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2022-23593'} | 2022-03-28T19:30:27Z | 2022-02-09T23:32:08Z | HIGH | 5.9 | {'CWE-754'} | {'https://github.com/advisories/GHSA-gwcx-jrx4-92w2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23593', 'https://github.com/tensorflow/tensorflow/commit/35f0fabb4c178253a964d7aabdbb15c6a398b69a', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-gwcx-jrx4-92w2', 'https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/compiler/mlir/tfrt/jit/transforms/tf_cpurt_symbolic_shape_optimization.cc#L149-L205'} | null | {'https://github.com/tensorflow/tensorflow/commit/35f0fabb4c178253a964d7aabdbb15c6a398b69a'} | {'https://github.com/tensorflow/tensorflow/commit/35f0fabb4c178253a964d7aabdbb15c6a398b69a'} |
GHSA | GHSA-jcxv-2j3h-mg59 | Improper Restriction of Operations within the Bounds of a Memory Buffer in OpenCV | OpenCV 3.3.1 (corresponding with opencv-python and opencv-contrib-python 3.3.1.11) has a Buffer Overflow in the cv::PxMDecoder::readData function in grfmt_pxm.cpp, because an incorrect size value is used. | {'CVE-2017-17760'} | 2021-11-18T15:31:01Z | 2021-10-12T22:03:09Z | MODERATE | 6.5 | {'CWE-119'} | {'https://lists.debian.org/debian-lts-announce/2018/01/msg00008.html', 'https://github.com/advisories/GHSA-jcxv-2j3h-mg59', 'https://github.com/opencv/opencv/pull/10369/commits/7bbe1a53cfc097b82b1589f7915a2120de39274c', 'http://www.securityfocus.com/bid/102974', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00028.html', 'https://nvd.nist.gov/vuln/detail/CVE-2017-17760', 'https://github.com/opencv/opencv/issues/10351', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00030.html'} | null | {'https://github.com/opencv/opencv/pull/10369/commits/7bbe1a53cfc097b82b1589f7915a2120de39274c'} | {'https://github.com/opencv/opencv/pull/10369/commits/7bbe1a53cfc097b82b1589f7915a2120de39274c'} |
GHSA | GHSA-6w9p-88qg-p3g3 | Cross-site Scripting in CKAN | In CKAN, versions 2.9.0 to 2.9.3 are affected by a stored XSS vulnerability via SVG file upload of users’ profile picture. This allows low privileged application users to store malicious scripts in their profile picture. These scripts are executed in a victim’s browser when they open the malicious profile picture | {'CVE-2021-25967'} | 2021-12-03T20:44:48Z | 2021-12-03T20:44:48Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/ckan/ckan/commit/5a46989c0a4f2c2873ca182c196da83b82babd25', 'https://github.com/ckan/ckan/pull/6477', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25967', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25967', 'https://github.com/advisories/GHSA-6w9p-88qg-p3g3'} | null | {'https://github.com/ckan/ckan/commit/5a46989c0a4f2c2873ca182c196da83b82babd25'} | {'https://github.com/ckan/ckan/commit/5a46989c0a4f2c2873ca182c196da83b82babd25'} |
GHSA | GHSA-x4r7-m2q9-69c8 | GraphiQL introspection schema template injection attack | - [1. Impact](#11-impact)
- [2. Scope](#12-scope)
- [3. Patches](#13-patches)
- [3.1 CDN bundle implementations may be automatically patched](#131-cdn-bundle-implementations-may-be-automatically-patched)
- [4. Workarounds for Older Versions](#14-workarounds-for-older-versions)
- [5. How to Re-create the Exploit](#15-how-to-re-create-the-exploit)
- [6. Credit](#16-credit)
- [7. References](#17-references)
- [8. For more information](#18-for-more-information)
This is a security advisory for an XSS vulnerability in `graphiql`.
A similar vulnerability affects `graphql-playground`, a fork of `graphiql`. There is a corresponding `graphql-playground` [advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw).
## 1. Impact
All versions of `graphiql` older than [`graphiql@1.4.7`](https://github.com/graphql/graphiql/releases/tag/v1.4.7) are vulnerable to compromised HTTP schema introspection responses or `schema` prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete.
In order for the attack to take place, the user must load a vulnerable schema in `graphiql`. There are a number of ways that can occur.
By default, the schema URL is _not_ attacker-controllable in `graphiql` or in its suggested implementations or examples, leaving only very complex attack vectors.
If a custom implementation of `graphiql`'s `fetcher` allows the schema URL to be set dynamically, such as a URL query parameter like `?endpoint=` in `graphql-playground`, or a database provided value, then this custom `graphiql` implementation is _vulnerable to phishing attacks_, and thus much more readily available, low or no privelege level xss attacks. The URLs could look like any generic looking graphql schema URL.
Because this exposes an XSS attack surface, it would be possible for a threat actor to exfiltrate user credentials, data, etc. using arbitrary malicious scripts, without it being known to the user.
## 2. Scope
This advisory describes the impact on the `graphiql` package. The vulnerability also affects other projects forked from `graphiql` such as [`graphql-playground`](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and the `graphql-playground` fork distributed by Apollo Server. The impact is more severe in the `graphql-playground` implementations; see the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7) and [Apollo Server advisory](https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw) for details.
This vulnerability does not impact `codemirror-graphql`, `monaco-graphql` or other dependents, as it exists in `onHasCompletion.ts` in `graphiql`. It does impact all forks of `graphiql`, and every released version of `graphiql`.
It should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this.
## 3. Patches
`graphiql@1.4.7` addresses this issue via defense in depth.
- **HTML-escaping text** that should be treated as text rather than HTML. In most of the app, this happens automatically because React escapes all interpolated text by default. However, one vulnerable component uses the unsafe `innerHTML` API and interpolated type names directly into HTML. We now properly escape that type name, which fixes the known vulnerability.
- **Validates the schema** upon receiving the introspection response or schema changes. Schemas with names that violate the GraphQL spec will no longer be loaded. (This includes preventing the Doc Explorer from loading.) This change is also sufficient to fix the known vulnerability. You can disable this validation by setting `dangerouslyAssumeSchemaIsValid={true}`, which means you are relying only on escaping values to protect you from this attack.
- **Ensuring that user-generated HTML is safe**. Schemas can contain Markdown in `description` and `deprecationReason` fields, and the web app renders them to HTML using the `markdown-it` library. As part of the development of `graphiql@1.4.7`, we verified that our use of `markdown-it` prevents the inclusion of arbitrary HTML. We use `markdown-it` without setting `html: true`, so we are comfortable relying on [`markdown-it`'s HTML escaping](https://github.com/markdown-it/markdown-it/blob/master/docs/security.md) here. We considered running a second level of sanitization over all rendered Markdown using a library such as `dompurify` but believe that is unnecessary as `markdown-it`'s sanitization appears to be adequate. `graphiql@1.4.7` does update to the latest version of `markdown-it` (v12, from v10) so that any security fixes in v11 and v12 will take effect.
### 3.1 CDN bundle implementations may be automatically patched
Note that if your implementation is depending on a CDN version of `graphiql`, and is pointed to the `latest` tag (usually the default for most cdns if no version is specified) then this issue is already mitigated, in case you were vulnerable to it before.
## 4. Workarounds for Older Versions
If you cannot use `graphiql@1.4.7` or later
- Always use a static URL to a trusted server that is serving a trusted GraphQL schema.
- If you have a custom implementation that allows using user-provided schema URLs via a query parameter, database value, etc, you must either disable this customization, or only allow trusted URLs.
## 5. How to Re-create the Exploit
You can see an example on [codesandbox](https://codesandbox.io/s/graphiql-xss-exploit-gr22f?file=/src/App.js). These are both fixed to the last `graphiql` release `1.4.6` which is the last vulnerable release; however it would work with any previous release of `graphiql`.
Both of these examples are meant to demonstrate the phishing attack surface, so they are customized to accept a `url` parameter. To demonstrate the phishing attack, add `?url=https://graphql-xss-schema.netlify.app/graphql` to the in-codesandbox browser.
Erase the contents of the given query and type `{u`. You will see an alert window open, showing that attacker-controlled code was executed.
Note that when React is in development mode, a validation exception is thrown visibly; however that exception is usually buried in the browser console in a production build of `graphiql`. This validation exception comes from `getDiagnostics`, which invokes `graphql` `validate()` which in turn will `assertValidSchema()`, as `apollo-server-core` does on executing each operation. This validation does not prevent the exploit from being successful.
Note that something like the `url` parameter is not required for the attack to happen if `graphiql`'s `fetcher` is configured in a different way to communicate with a compromised GraphQL server.
## 6. Credit
This vulnerability was discovered by [@Ry0taK](https://github.com/Ry0taK), thank you! :1st_place_medal:
Others who contributed:
- [@imolorhe](https://github.com/imolorhe)
- [@glasser](https://github.com/glasser)
- [@divyenduz](https://github.com/divyenduz)
- [@dotansimha](https://github.com/dotansimha)
- [@acao](https://github.com/acao)
- [@benjie](https://github.com/benjie) and many others who provided morale support
## 7. References
**The vulnerability has always been present**
[In the first commit](https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87)
[And later moved to onHasCompletion.js in 2016](https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110) (now `.ts` after the typescript migration)
## 8. For more information
If you have any questions or comments about this advisory:
- Open an issue in [graphiql repo](https://github.com/graphql/graphiql/new/issues)
- Read [more details](https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability) on the vulnerability | {'CVE-2021-41248'} | 2022-04-19T19:03:03Z | 2021-11-08T18:03:50Z | HIGH | 7.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41248', 'https://github.com/graphql/graphiql/blob/main/docs/security/2021-introspection-schema-xss.md#2-more-details-on-the-vulnerability', 'https://github.com/graphql/graphiql/commit/cb237eeeaf7333c4954c752122261db7520f7bf4', 'https://github.com/advisories/GHSA-x4r7-m2q9-69c8', 'https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110', 'https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7', 'https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87', 'https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8'} | null | {'https://github.com/graphql/graphiql/commit/cb237eeeaf7333c4954c752122261db7520f7bf4', 'https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110', 'https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87'} | {'https://github.com/graphql/graphiql/commit/b9dec272d89d9c590727fd10d62e4a47e0317fc7#diff-855b77f6310b7e4fb1bcac779cd945092ed49fd759f4684ea391b45101166437R87', 'https://github.com/graphql/graphiql/commit/cb237eeeaf7333c4954c752122261db7520f7bf4', 'https://github.com/graphql/graphiql/commit/6701b0b626e43800e32413590a295e5c1e3d5419#diff-d45eb76aebcffd27d3a123214487116fa95e0b5a11d70a94a0ce3033ce09f879R110'} |
GHSA | GHSA-qc53-44cj-vfvx | Denial of Service in Tensorflow | ### Impact
The `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L185
However, malicious users can pass in tensors of different rank, resulting in a `CHECK` assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor.
### Patches
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.
We recommend users to upgrade to TensorFlow 2.3.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4) | {'CVE-2020-15197'} | 2021-08-26T15:12:10Z | 2020-09-25T18:28:30Z | MODERATE | 6.3 | {'CWE-20', 'CWE-617'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qc53-44cj-vfvx', 'https://github.com/advisories/GHSA-qc53-44cj-vfvx', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15197', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'} | null | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} | {'https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02'} |
GHSA | GHSA-cwp9-956f-vcwh | 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-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1195, CVE-2019-1196, CVE-2019-1197. | {'CVE-2019-1141'} | 2021-03-29T20:57:56Z | 2021-03-29T20:57:56Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/chakra-core/ChakraCore/commit/329d9d213e7b286349c0b156be4b5a088555de90', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1141', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1141', 'https://github.com/advisories/GHSA-cwp9-956f-vcwh', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | null | {'https://github.com/chakra-core/ChakraCore/commit/329d9d213e7b286349c0b156be4b5a088555de90', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} | {'https://github.com/chakra-core/ChakraCore/commit/329d9d213e7b286349c0b156be4b5a088555de90', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'} |
GHSA | GHSA-5mg8-w23w-74h3 | Information Disclosure in Guava | A temp directory creation vulnerability exists in all Guava versions allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava `com.google.common.io.Files.createTempDir()`. The permissions granted to the directory created default to the standard unix-like /tmp ones, leaving the files open. We recommend explicitly changing the permissions after the creation of the directory, or removing uses of the vulnerable method
| {'CVE-2020-8908'} | 2022-04-26T20:59:22Z | 2021-03-25T17:04:19Z | LOW | 3.3 | {'CWE-200', 'CWE-173', 'CWE-732'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8908', 'https://lists.apache.org/thread.html/reebbd63c25bc1a946caa419cec2be78079f8449d1af48e52d47c9e85@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/r6874dfe26eefc41b7c9a5e4a0487846fc4accf8c78ff948b24a1104a@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r037fed1d0ebde50c9caf8d99815db3093c344c3f651c5a49a09824ce@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r5d61b98ceb7bba939a651de5900dbd67be3817db6bfcc41c6e04e199@%3Cyarn-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/re120f6b3d2f8222121080342c5801fdafca2f5188ceeb3b49c8a1d27@%3Cyarn-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/r68d86f4b06c808204f62bcb254fcb5b0432528ee8d37a07ef4bc8222@%3Ccommits.ws.apache.org%3E', 'https://lists.apache.org/thread.html/r2fe45d96eea8434b91592ca08109118f6308d60f6d0e21d52438cfb4@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rd7e12d56d49d73e2b8549694974b07561b79b05455f7f781954231bf@%3Cdev.pig.apache.org%3E', 'https://lists.apache.org/thread.html/rd01f5ff0164c468ec7abc96ff7646cea3cce6378da2e4aa29c6bcb95@%3Cgithub.arrow.apache.org%3E', 'https://lists.apache.org/thread.html/rf00b688ffa620c990597f829ff85fdbba8bf73ee7bfb34783e1f0d4e@%3Cyarn-dev.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/ra7ab308481ee729f998691e8e3e02e93b1dedfc98f6b1cd3d86923b3@%3Cyarn-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/rb8c0f1b7589864396690fe42a91a71dea9412e86eec66dc85bbacaaf@%3Ccommits.cxf.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/rc607bc52f3507b8b9c28c6a747c3122f51ac24afe80af2a670785b97@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/r58a8775205ab1839dba43054b09a9ab3b25b423a4170b2413c4067ac@%3Ccommon-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/rbc7642b9800249553f13457e46b813bea1aec99d2bc9106510e00ff3@%3Ctorque-dev.db.apache.org%3E', 'https://github.com/advisories/GHSA-5mg8-w23w-74h3', 'https://lists.apache.org/thread.html/rb2364f4cf4d274eab5a7ecfaf64bf575cedf8b0173551997c749d322@%3Cgitbox.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r3c3b33ee5bef0c67391d27a97cbfd89d44f328cf072b601b58d4e748@%3Ccommits.pulsar.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20220210-0003/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/rd5d58088812cf8e677d99b07f73c654014c524c94e7fedbdee047604@%3Ctorque-dev.db.apache.org%3E', 'https://lists.apache.org/thread.html/r5b3d93dfdfb7708e796e8762ab40edbde8ff8add48aba53e5ea26f44@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/rd2704306ec729ccac726e50339b8a8f079515cc29ccb77713b16e7c5@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/rf9f0fa84b8ae1a285f0210bafec6de2a9eba083007d04640b82aa625@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/rc2dbc4633a6eea1fcbce6831876cfa17b73759a98c65326d1896cb1a@%3Ctorque-dev.db.apache.org%3E', 'https://lists.apache.org/thread.html/r294be9d31c0312d2c0837087204b5d4bf49d0552890e6eec716fa6a6@%3Cyarn-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/r07ed3e4417ad043a27bee7bb33322e9bfc7d7e6d1719b8e3dfd95c14@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r215b3d50f56faeb2f9383505f3e62faa9f549bb23e8a9848b78a968e@%3Ccommits.ws.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/rcafc3a637d82bdc9a24036b2ddcad1e519dd0e6f848fcc3d606fd78f@%3Cdev.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r49549a8322f62cd3acfa4490d25bfba0be04f3f9ff4d14fe36199d27@%3Cyarn-dev.hadoop.apache.org%3E', 'https://github.com/google/guava/issues/4011', 'https://lists.apache.org/thread.html/r007add131977f4f576c232b25e024249a3d16f66aad14a4b52819d21@%3Ccommon-issues.hadoop.apache.org%3E', 'https://lists.apache.org/thread.html/r3dd8881de891598d622227e9840dd7c2ef1d08abbb49e9690c7ae1bc@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/r161b87f8037bbaff400194a63cd2016c9a69f5949f06dcc79beeab54@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rfc27e2727a20a574f39273e0432aa97486a332f9b3068f6ac1346594@%3Cdev.myfaces.apache.org%3E', 'https://lists.apache.org/thread.html/r79e47ed555bdb1180e528420a7a2bb898541367a29a3bc6bbf0baf2c@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r841c5e14e1b55281523ebcde661ece00b38a0569e00ef5e12bd5f6ba@%3Cissues.maven.apache.org%3E', 'https://lists.apache.org/thread.html/r7b0e81d8367264d6cad98766a469d64d11248eb654417809bfdacf09@%3Cyarn-issues.hadoop.apache.org%3E', 'https://github.com/google/guava/commit/fec0dbc4634006a6162cfd4d0d09c962073ddf40', 'https://lists.apache.org/thread.html/r4776f62dfae4a0006658542f43034a7fc199350e35a66d4e18164ee6@%3Ccommits.cxf.apache.org%3E', 'https://snyk.io/vuln/SNYK-JAVA-COMGOOGLEGUAVA-1015415', 'https://www.oracle.com//security-alerts/cpujul2021.html'} | null | {'https://github.com/google/guava/commit/fec0dbc4634006a6162cfd4d0d09c962073ddf40'} | {'https://github.com/google/guava/commit/fec0dbc4634006a6162cfd4d0d09c962073ddf40'} |
GHSA | GHSA-x8wj-cqmp-3wmm | Cross-site Scripting in Zenario CMS | Zenario CMS 9.0.54156 is vulnerable to Cross Site Scripting (XSS) via upload file to *.SVG. An attacker can send malicious files to victims and steals victim's cookie leads to account takeover. The person viewing the image of a contact can be victim of XSS. | {'CVE-2021-41952'} | 2022-03-29T21:14:28Z | 2022-03-15T00:00:59Z | MODERATE | 4.8 | {'CWE-79'} | {'https://github.com/TribalSystems/Zenario/commit/4566d8a9ac6755f098b3373252fdb17754a77007', 'https://github.com/TribalSystems/Zenario/releases/tag/9.0.55141', 'https://github.com/advisories/GHSA-x8wj-cqmp-3wmm', 'https://github.com/hieuminhnv/Zenario-CMS-9.0-last-version/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41952'} | null | {'https://github.com/TribalSystems/Zenario/commit/4566d8a9ac6755f098b3373252fdb17754a77007'} | {'https://github.com/TribalSystems/Zenario/commit/4566d8a9ac6755f098b3373252fdb17754a77007'} |
GHSA | GHSA-37pf-w9ff-gqvm | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0933, CVE-2019-0937. | {'CVE-2019-0927'} | 2021-03-29T20:58:59Z | 2021-03-29T20:58:59Z | HIGH | 7.5 | {'CWE-787'} | {'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0927', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0927', 'https://github.com/advisories/GHSA-37pf-w9ff-gqvm', 'https://github.com/chakra-core/ChakraCore/commit/87ac2b5a751710ee288fdda3fd4d9818e22387a1'} | null | {'https://github.com/chakra-core/ChakraCore/commit/87ac2b5a751710ee288fdda3fd4d9818e22387a1', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/87ac2b5a751710ee288fdda3fd4d9818e22387a1'} |
GHSA | GHSA-h4mf-75hf-67w4 | Information disclosure in parse-server | 1. you can fetch all the users' objects, by using regex in the NoSQL query.
Using the NoSQL, you can use a regex on sessionToken `("_SessionToken":{"$regex":"r:027f"}}` and find valid accounts this way.
Using this method, it's possible to retrieve accounts without interaction from the users.
GET /parse/users/me HTTP/1.1
```
{
"_ApplicationId": "appName",
"_JavaScriptKey": "javascriptkey",
"_ClientVersion": "js2.10.0",
"_InstallationId": "ca713ee2-6e60-d023-a8fe-14e1bfb2f300",
"_SessionToken": {
"$regex": "r:5"
}
}
```
When trying it with an update query the same thing luckily doesn't seem to work:
POST /parse/classes/_User/PPNk59jPPZ
2. There is another similar vulnerability in verify email and the request password reset.
If you sign up with someone else's email address, you can simply use regex in the token param to verify the account: `http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&username=some@email.com`
The same thing can be done for reset password: `http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&username=some@email.com`
You may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed. | {'CVE-2020-5251'} | 2022-04-19T19:02:41Z | 2020-03-04T20:20:27Z | HIGH | 7.7 | {'CWE-200', 'CWE-285'} | {'https://github.com/parse-community/parse-server/commit/3a3a5eee5ffa48da1352423312cb767de14de269', 'https://github.com/parse-community/parse-server/security/advisories/GHSA-h4mf-75hf-67w4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5251', 'https://github.com/advisories/GHSA-h4mf-75hf-67w4'} | null | {'https://github.com/parse-community/parse-server/commit/3a3a5eee5ffa48da1352423312cb767de14de269'} | {'https://github.com/parse-community/parse-server/commit/3a3a5eee5ffa48da1352423312cb767de14de269'} |
GHSA | GHSA-mvqp-q37c-wf9j | Moderate severity vulnerability that affects io.ratpack:ratpack-core | ## CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')
Versions of Ratpack 0.9.1 through and including 1.7.4 are vulnerable to [HTTP Response Splitting](https://www.owasp.org/index.php/HTTP_Response_Splitting),
if untrusted and unsanitized data is used to populate the headers of an HTTP response.
An attacker can utilize this vulnerability to have the server issue any HTTP response they specify.
If your application uses arbitrary user input as the value of a response header it is vulnerable.
If your application does not use arbitrary values as response header values, it is not vulnerable.
Previously, Ratpack did not validate response header values.
Now, adding a header value that contains the header value termination characters (CRLF) produces a runtime exception.
Since there is no mechanism for escaping or encoding the termination characters in a String, a runtime exception is necessary.
As potentially dangerous values now cause runtime exceptions, it is a good idea to continue to validate and sanitize any user-supplied values being used as response headers.
We would like to thank [Jonathan Leitschuh](https://github.com/JLLeitschuh) for reporting this vulnerability.
### Vulnerable Example
The following example server uses a query parameter value as a response header, without validating or sanitizing it.
```java
RatpackServer startedServer = RatpackServer.start(server -> {
server.handlers(chain -> chain.all(ctx -> {
// User supplied query parameter
String header = ctx.getRequest().getQueryParams().get("header");
// User supplied data used to populate a header value.
ctx.header("the-header", header)
.render("OK!");
}));
});
```
Sending a request to the server with the following value for the `header` query param would allow the execution of arbitrary Javascript.
```
Content-Type: text/html
X-XSS-Protection: 0
<script>alert(document.domain)</script>
```
### Impact
- Cross-User Defacement
- Cache Poisoning
- Cross-Site Scripting
- Page Hijacking
### Patches
This vulnerability has been patched in Ratpack version 1.7.5.
### Root Cause
The root cause was due to using the netty `DefaultHttpHeaders` object with verification disabled.
https://github.com/ratpack/ratpack/blob/af1e8c8590f164d7dd84d4212886fad4ead99080/ratpack-core/src/main/java/ratpack/server/internal/NettyHandlerAdapter.java#L159
This vulnerability is now more clearly documented in the Netty documentation: https://github.com/netty/netty/pull/9646
### Workarounds
The workaround for this vulnerability is to either not use arbitrary input as response header values or validate such values before being used to ensure they don't contain a carriage return and/or line feed characters.
### References
- [CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html)
- Fix commit: https://github.com/ratpack/ratpack/commit/efb910d38a96494256f36675ef0e5061097dd77d
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [ratpack/ratpack](https://github.com/ratpack/ratpack/issues)
* Ask in our [Slack channel](https://slack-signup.ratpack.io/) | {'CVE-2019-17513'} | 2021-09-15T21:01:30Z | 2019-10-21T16:08:43Z | HIGH | 7.5 | {'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-17513', 'https://github.com/ratpack/ratpack/releases/tag/v1.7.5', 'https://github.com/ratpack/ratpack/commit/efb910d38a96494256f36675ef0e5061097dd77d', 'https://github.com/ratpack/ratpack/commit/c560a8d10cb8bdd7a526c1ca2e67c8f224ca23ae', 'https://ratpack.io/versions/1.7.5', 'https://github.com/advisories/GHSA-mvqp-q37c-wf9j', 'https://github.com/ratpack/ratpack/security/advisories/GHSA-mvqp-q37c-wf9j'} | null | {'https://github.com/ratpack/ratpack/commit/efb910d38a96494256f36675ef0e5061097dd77d', 'https://github.com/ratpack/ratpack/commit/c560a8d10cb8bdd7a526c1ca2e67c8f224ca23ae'} | {'https://github.com/ratpack/ratpack/commit/c560a8d10cb8bdd7a526c1ca2e67c8f224ca23ae', 'https://github.com/ratpack/ratpack/commit/efb910d38a96494256f36675ef0e5061097dd77d'} |
GHSA | GHSA-7gc6-qh9x-w6h8 | Incorrect Authorization in cross-fetch | When fetching a remote url with Cookie if it get Location response header then it will follow that url and try to fetch that url with provided cookie . So cookie is leaked here to thirdparty.
Ex: you try to fetch example.com with cookie and if it get redirect url to attacker.com then it fetch that redirect url with provided cookie . | {'CVE-2022-1365'} | 2022-05-03T17:48:17Z | 2022-04-17T00:00:32Z | MODERATE | 6.1 | {'CWE-863', 'CWE-359'} | {'https://github.com/lquixada/cross-fetch/pull/135', 'https://huntr.dev/bounties/ab55dfdd-2a60-437a-a832-e3efe3d264ac', 'https://github.com/lquixada/cross-fetch/commit/a3b3a9481091ddd06b8f83784ba9c4e034dc912a', 'https://github.com/advisories/GHSA-7gc6-qh9x-w6h8', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1365'} | null | {'https://github.com/lquixada/cross-fetch/commit/a3b3a9481091ddd06b8f83784ba9c4e034dc912a'} | {'https://github.com/lquixada/cross-fetch/commit/a3b3a9481091ddd06b8f83784ba9c4e034dc912a'} |
GHSA | GHSA-x27w-qxhg-343v | Access Restriction Bypass in go-ldap | In the ldap.v2 (aka go-ldap) package through 2.5.0 for Go, an attacker may be able to login with an empty password. This issue affects an application using this package if these conditions are met: (1) it relies only on the return error of the Bind function call to determine whether a user is authorized (i.e., a nil return value is interpreted as successful authorization) and (2) it is used with an LDAP server allowing unauthenticated bind. | {'CVE-2017-14623'} | 2022-04-12T22:32:59Z | 2022-02-15T01:57:18Z | HIGH | 8.1 | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-14623', 'https://github.com/go-ldap/ldap/pull/126', 'https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66', 'https://github.com/advisories/GHSA-x27w-qxhg-343v'} | null | {'https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66'} | {'https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66'} |
GHSA | GHSA-545q-3fg6-48m7 | Regular expression denial of service (ReDoS) | This affects the package html-parse-stringify before 2.0.1; all versions of package html-parse-stringify2. Sending certain input could cause one of the regular expressions that is used for parsing to backtrack, freezing the process. | {'CVE-2021-23346'} | 2021-03-18T19:39:32Z | 2021-03-18T19:39:31Z | MODERATE | 5.3 | {'CWE-400'} | {'https://github.com/advisories/GHSA-545q-3fg6-48m7', 'https://github.com/HenrikJoreteg/html-parse-stringify/releases/tag/v2.0.1', 'https://snyk.io/vuln/SNYK-JS-HTMLPARSESTRINGIFY-1079306', 'https://snyk.io/vuln/SNYK-JS-HTMLPARSESTRINGIFY2-1079307', 'https://github.com/rayd/html-parse-stringify2/blob/master/lib/parse.js%23L2', 'https://github.com/HenrikJoreteg/html-parse-stringify/commit/c7274a48e59c92b2b7e906fedf9065159e73fe12', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1080633', 'https://github.com/HenrikJoreteg/html-parse-stringify/blob/master/lib/parse.js%23L2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23346'} | null | {'https://github.com/HenrikJoreteg/html-parse-stringify/commit/c7274a48e59c92b2b7e906fedf9065159e73fe12'} | {'https://github.com/HenrikJoreteg/html-parse-stringify/commit/c7274a48e59c92b2b7e906fedf9065159e73fe12'} |
GHSA | GHSA-g2qj-pmxm-9f8f | User enumeration in authentication mechanisms | Description
-----------
The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. It was also possible to enumerate users by using a timing attack, by comparing time elapsed when authenticating an existing user and authenticating a non-existing user.
Resolution
----------
We now ensure that 403s are returned whether the user exists or not if the password is invalid or if the user does not exist.
The patch for this issue is available [here](https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011) for branch 3.4.
Credits
-------
I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue. | null | 2021-10-08T21:21:13Z | 2021-05-17T20:52:32Z | LOW | 0 | {'CWE-200'} | {'https://github.com/symfony/symfony/security/advisories/GHSA-g2qj-pmxm-9f8f', 'https://github.com/advisories/GHSA-g2qj-pmxm-9f8f', 'https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011'} | null | {'https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011'} | {'https://github.com/symfony/symfony/commit/2a581d22cc621b33d5464ed65c4bc2057f72f011'} |
GHSA | GHSA-9qq2-xhmc-h9qr | Access Control Bypass | An issue was discovered in Rancher 2 through 2.1.5. Any project member with access to the default namespace can mount the netes-default service account in a pod, and then use that pod to execute administrative privileged commands against the k8s cluster. This could be mitigated by isolating the default namespace in a separate project, where only cluster admins can be given permissions to access. As of 2018-12-20, this bug affected ALL clusters created or imported by Rancher. | {'CVE-2018-20321'} | 2022-04-25T20:21:12Z | 2021-06-23T17:57:10Z | MODERATE | 4.2 | {'CWE-288', 'CWE-668'} | {'https://rancher.com/blog/2019/2019-01-29-explaining-security-vulnerabilities-addressed-in-rancher-v2-1-6-and-v2-0-11/', 'https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20321', 'https://github.com/rancher/rancher/releases/tag/v2.1.6', 'https://forums.rancher.com/c/announcements', 'https://github.com/advisories/GHSA-9qq2-xhmc-h9qr'} | null | {'https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448'} | {'https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448'} |
GHSA | GHSA-68q3-7wjp-7q3j | The filename of uploaded files vulnerable to stored XSS | ### Impact
The filename of uploaded files was vulnerable to stored XSS. It is not possible to inject javascript code in the file name when creating/uploading the file. But, once created/uploaded, it can be renamed to inject the payload in it.
Additionally, the measures to prevent renaming the file to disallowed filename extensions could be circumvented.
### Patches
This is fixed in Bolt 3.7.1.
### References
Related issue: https://github.com/bolt/bolt/pull/7853 | {'CVE-2020-4041'} | 2022-04-19T19:02:28Z | 2020-06-09T00:25:34Z | MODERATE | 7.4 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-4041', 'https://github.com/bolt/bolt/pull/7853', 'https://github.com/bolt/bolt/commit/b42cbfcf3e3108c46a80581216ba03ef449e419f', 'https://github.com/bolt/bolt/security/advisories/GHSA-68q3-7wjp-7q3j', 'https://github.com/advisories/GHSA-68q3-7wjp-7q3j', 'http://packetstormsecurity.com/files/158299/Bolt-CMS-3.7.0-XSS-CSRF-Shell-Upload.html', 'http://seclists.org/fulldisclosure/2020/Jul/4'} | null | {'https://github.com/bolt/bolt/commit/b42cbfcf3e3108c46a80581216ba03ef449e419f'} | {'https://github.com/bolt/bolt/commit/b42cbfcf3e3108c46a80581216ba03ef449e419f'} |
GHSA | GHSA-82v2-mx6x-wq7q | Incorrect Default Permissions in log4js | ### Impact
Default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config.
### Patches
Fixed by:
* https://github.com/log4js-node/log4js-node/pull/1141
* https://github.com/log4js-node/streamroller/pull/87
Released to NPM in log4js@6.4.0
### Workarounds
Every version of log4js published allows passing the mode parameter to the configuration of file appenders, see the documentation for details.
### References
Thanks to [ranjit-git](https://www.huntr.dev/users/ranjit-git) for raising the issue, and to @peteriman for fixing the problem.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [logj4s-node](https://github.com/log4js-node/log4js-node)
* Ask a question in the [slack channel](https://join.slack.com/t/log4js-node/shared_invite/enQtODkzMDQ3MzExMDczLWUzZmY0MmI0YWI1ZjFhODY0YjI0YmU1N2U5ZTRkOTYyYzg3MjY5NWI4M2FjZThjYjdiOGM0NjU2NzBmYTJjOGI)
* Email us at [gareth.nomiddlename@gmail.com](mailto:gareth.nomiddlename@gmail.com)
| {'CVE-2022-21704'} | 2022-04-19T19:03:20Z | 2022-01-21T18:53:27Z | MODERATE | 5.5 | {'CWE-276'} | {'https://github.com/advisories/GHSA-82v2-mx6x-wq7q', 'https://github.com/log4js-node/log4js-node/blob/v6.4.0/CHANGELOG.md#640', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21704', 'https://github.com/log4js-node/log4js-node/pull/1141/commits/8042252861a1b65adb66931fdf702ead34fa9b76', 'https://github.com/log4js-node/streamroller/pull/87', 'https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q'} | null | {'https://github.com/log4js-node/log4js-node/pull/1141/commits/8042252861a1b65adb66931fdf702ead34fa9b76'} | {'https://github.com/log4js-node/log4js-node/pull/1141/commits/8042252861a1b65adb66931fdf702ead34fa9b76'} |
GHSA | GHSA-c2h3-6mxw-7mvq | Insufficiently restricted permissions on plugin directories | ### Impact
A bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files.
### Patches
This vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability.
### Workarounds
Limit access to the host to trusted users. Update directory permission on container bundles directories.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [github.com/containerd/containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io)
| {'CVE-2021-41103'} | 2021-11-18T15:14:52Z | 2021-10-04T20:14:47Z | MODERATE | 5.9 | {'CWE-22'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZNFADTCHHYWVM6W4NJ6CB4FNFM2VMBIB/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41103', 'https://github.com/containerd/containerd/commit/5b46e404f6b9f661a205e28d59c982d3634148f8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/B5Q6G6I4W5COQE25QMC7FJY3I3PAYFBB/', 'https://github.com/containerd/containerd/releases/tag/v1.4.11', 'https://github.com/containerd/containerd/releases/tag/v1.5.7', 'https://github.com/advisories/GHSA-c2h3-6mxw-7mvq', 'https://www.debian.org/security/2021/dsa-5002', 'https://github.com/containerd/containerd/security/advisories/GHSA-c2h3-6mxw-7mvq'} | null | {'https://github.com/containerd/containerd/commit/5b46e404f6b9f661a205e28d59c982d3634148f8'} | {'https://github.com/containerd/containerd/commit/5b46e404f6b9f661a205e28d59c982d3634148f8'} |
GHSA | GHSA-pqrv-8r2f-7278 | Crash due to erroneous `StatusOr` in TensorFlow | ### Impact
A `GraphDef` from a TensorFlow `SavedModel` can be maliciously altered to cause a TensorFlow process to crash due to encountering [a `StatusOr` value that is an error and forcibly extracting the value from it](https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/core/graph/graph.cc#L560-L567):
```cc
if (op_reg_data->type_ctor != nullptr) {
VLOG(3) << "AddNode: found type constructor for " << node_def.name();
const auto ctor_type =
full_type::SpecializeType(AttrSlice(node_def), op_reg_data->op_def);
const FullTypeDef ctor_typedef = ctor_type.ValueOrDie();
if (ctor_typedef.type_id() != TFT_UNSET) {
*(node_def.mutable_experimental_type()) = ctor_typedef;
}
}
```
If `ctor_type` is an error status, `ValueOrDie` results in a crash.
### Patches
We have patched the issue in GitHub commit [955059813cc325dc1db5e2daa6221271406d4439](https://github.com/tensorflow/tensorflow/commit/955059813cc325dc1db5e2daa6221271406d4439).
We have patched the issue in multiple GitHub commits and these will be included in TensorFlow 2.8.0 and TensorFlow 2.7.1, as both are affected.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. | {'CVE-2022-23590'} | 2022-02-11T20:00:43Z | 2022-02-09T23:29:38Z | MODERATE | 5.9 | {'CWE-754'} | {'https://github.com/tensorflow/tensorflow/commit/955059813cc325dc1db5e2daa6221271406d4439', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23590', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pqrv-8r2f-7278', 'https://github.com/advisories/GHSA-pqrv-8r2f-7278', 'https://github.com/tensorflow/tensorflow/blob/274df9b02330b790aa8de1cee164b70f72b9b244/tensorflow/core/graph/graph.cc#L560-L567'} | null | {'https://github.com/tensorflow/tensorflow/commit/955059813cc325dc1db5e2daa6221271406d4439'} | {'https://github.com/tensorflow/tensorflow/commit/955059813cc325dc1db5e2daa6221271406d4439'} |
GHSA | GHSA-vmf5-924f-25f2 | 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-1062, CVE-2019-1092, CVE-2019-1106, CVE-2019-1107. | {'CVE-2019-1103'} | 2021-03-29T20:59:12Z | 2021-03-29T20:59:12Z | HIGH | 7.5 | {'CWE-787'} | {'https://github.com/advisories/GHSA-vmf5-924f-25f2', 'https://github.com/chakra-core/ChakraCore/commit/efab3101028045cbfa0cc21bd852f75bcc037dba', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1103', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1103', 'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8'} | null | {'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8', 'https://github.com/chakra-core/ChakraCore/commit/efab3101028045cbfa0cc21bd852f75bcc037dba'} | {'https://github.com/chakra-core/ChakraCore/commit/efab3101028045cbfa0cc21bd852f75bcc037dba', 'https://github.com/chakra-core/ChakraCore/commit/75162b7f2d8ac2b37d17564e9c979ba1bae707e8'} |
GHSA | GHSA-cqp5-m4pq-gfgp | Prototype Pollution in defaults-deep | Versions of `default-deep` before 0.2.4 are vulnerable to prototype pollution
## Recommendation
Update to version 0.2.4 or later. | {'CVE-2018-3723'} | 2021-01-08T18:56:59Z | 2018-07-26T15:18:43Z | LOW | 0 | {'CWE-471'} | {'https://github.com/jonschlinkert/defaults-deep/commit/c873f341327ad885ff4d0f23b3d3bca31b0343e5', 'https://github.com/advisories/GHSA-cqp5-m4pq-gfgp', 'https://hackerone.com/reports/310514', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3723', 'https://www.npmjs.com/advisories/581'} | null | {'https://github.com/jonschlinkert/defaults-deep/commit/c873f341327ad885ff4d0f23b3d3bca31b0343e5'} | {'https://github.com/jonschlinkert/defaults-deep/commit/c873f341327ad885ff4d0f23b3d3bca31b0343e5'} |
GHSA | GHSA-5f9h-9pjv-v6j7 | Directory traversal in Rack::Directory app bundled with Rack | A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure. | {'CVE-2020-8161'} | 2021-01-08T21:28:30Z | 2020-07-06T21:31:02Z | MODERATE | 0 | {'CWE-548'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8161', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00006.html', 'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e', 'https://usn.ubuntu.com/4561-1/', 'https://hackerone.com/reports/434404', 'https://github.com/advisories/GHSA-5f9h-9pjv-v6j7', 'https://groups.google.com/g/rubyonrails-security/c/IOO1vNZTzPA', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2020-8161.yml', 'https://groups.google.com/forum/#!topic/ruby-security-ann/T4ZIsfRf2eA'} | null | {'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e'} | {'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e'} |
GHSA | GHSA-h3vq-wv8j-36gw | Cross-site Scripting in Scratch-Svg-Renderer | A DOM-based cross-site scripting (XSS) vulnerability in Scratch-Svg-Renderer v0.2.0 allows attackers to execute arbitrary web scripts or HTML via a crafted sb3 file. | {'CVE-2020-27428'} | 2022-01-08T00:44:33Z | 2022-01-08T00:44:33Z | MODERATE | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-h3vq-wv8j-36gw', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27428', 'https://github.com/LLK/scratch-svg-renderer/commit/7c74ec7de3254143ec3c557677f5355a90a3d07f'} | null | {'https://github.com/LLK/scratch-svg-renderer/commit/7c74ec7de3254143ec3c557677f5355a90a3d07f'} | {'https://github.com/LLK/scratch-svg-renderer/commit/7c74ec7de3254143ec3c557677f5355a90a3d07f'} |
GHSA | GHSA-5rq8-3wvf-wrfg | Out-of-bounds write | A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0937. | {'CVE-2019-0933'} | 2021-03-29T20:59:01Z | 2021-03-29T20:59:01Z | HIGH | 7.5 | {'CWE-787'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-0933', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0933', 'https://github.com/advisories/GHSA-5rq8-3wvf-wrfg', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/1a550c67b33b27675c0553152cabd09e4ffe3abf'} | null | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/1a550c67b33b27675c0553152cabd09e4ffe3abf'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/1a550c67b33b27675c0553152cabd09e4ffe3abf'} |
GHSA | GHSA-4365-fhm5-qcrx | Maliciously Crafted Model Archive Can Lead To Arbitrary File Write | ### Impact
An Archive Extraction (Zip Slip) vulnerability in the functionality that allows a user to load a trained model archive in Rasa 2.8.9 and older allows an attacker arbitrary write capability within specific directories using a malicious crafted archive file.
### Patches
The vulnerability is fixed in Rasa 2.8.10
### Workarounds
Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.
### For more information
If you have any questions or comments about this advisory:
* Email [the Rasa Security Team](mailto:security@rasa.com)
| {'CVE-2021-41127'} | 2021-10-22T16:19:13Z | 2021-10-22T16:19:13Z | HIGH | 7.3 | {'CWE-23', 'CWE-22'} | {'https://github.com/advisories/GHSA-4365-fhm5-qcrx', 'https://github.com/RasaHQ/rasa/commit/1b6b502f52d73b4f8cd1959ce724b8ad0eb33989', 'https://github.com/RasaHQ/rasa/security/advisories/GHSA-4365-fhm5-qcrx'} | null | {'https://github.com/RasaHQ/rasa/commit/1b6b502f52d73b4f8cd1959ce724b8ad0eb33989'} | {'https://github.com/RasaHQ/rasa/commit/1b6b502f52d73b4f8cd1959ce724b8ad0eb33989'} |
GHSA | GHSA-624f-cqvr-3qw4 | URL Redirection to Untrusted Site ('Open Redirect') in Flask-AppBuilder | ### Impact
If using Flask-AppBuilder OAuth, an attacker can share a carefully crafted URL with a trusted domain for an application built with Flask-AppBuilder, this URL can redirect a user to a malicious site. This is an open redirect vulnerability
### Patches
Install Flask-AppBuilder 3.2.2 or above
### Workarounds
Filter HTTP traffic containing `?next={next-site}` where the `next-site` domain is different from the application you are protecting
| {'CVE-2021-32805'} | 2021-09-09T13:33:27Z | 2021-09-08T21:11:14Z | HIGH | 7.2 | {'CWE-601'} | {'https://github.com/advisories/GHSA-624f-cqvr-3qw4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32805', 'https://github.com/dpgaspar/Flask-AppBuilder/commit/6af28521589599b1dbafd6313256229ee9a4fa74', 'https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-624f-cqvr-3qw4', 'https://github.com/dpgaspar/Flask-AppBuilder/releases/tag/v3.3.2', 'https://pypi.org/project/Flask-AppBuilder/'} | null | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/6af28521589599b1dbafd6313256229ee9a4fa74'} | {'https://github.com/dpgaspar/Flask-AppBuilder/commit/6af28521589599b1dbafd6313256229ee9a4fa74'} |
GHSA | GHSA-694p-xrhg-x3wm | CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request Header Injection') | ### Vulnerability
Micronaut's HTTP client is vulnerable to "HTTP Request Header Injection" due to not validating request headers passed to the client.
Example of vulnerable code:
```java
@Controller("/hello")
public class HelloController {
@Inject
@Client("/")
RxHttpClient client;
@Get("/external-exploit")
@Produces(MediaType.TEXT_PLAIN)
public String externalExploit(@QueryValue("header-value") String headerValue) {
return client.toBlocking().retrieve(
HttpRequest.GET("/hello")
.header("Test", headerValue)
);
}
}
```
In the above case a query value received from a user is passed as a header value to the client. Since the client doesn't validate the header value the request headers and body have the potential to be manipulated.
For example, a user that supplies the following payload, can force the client to make multiple attacker-controlled HTTP requests.
```java
List<String> headerData = List.of(
"Connection: Keep-Alive", // This keeps the connection open so another request can be stuffed in.
"",
"",
"POST /hello/super-secret HTTP/1.1",
"Host: 127.0.0.1",
"Content-Length: 31",
"",
"{\"new\":\"json\",\"content\":\"here\"}",
"",
""
);
String headerValue = "H\r\n" + String.join("\r\n", headerData);;
URI theURI =
UriBuilder
.of("/hello/external-exploit")
.queryParam("header-value", headerValue) // Automatically URL encodes data
.build();
HttpRequest<String> request = HttpRequest.GET(theURI);
String body = client.toBlocking().retrieve(request);
```
Note that using `@HeaderValue` instead of `@QueryValue` is not vulnerable since Micronaut's HTTP server does validate the headers passed to the server, so the exploit can only be triggered by using user data that is not an HTTP header (query values, form data etc.).
### Impact
The attacker is able to control the entirety of the HTTP body for their custom requests.
As such, this vulnerability enables attackers to perform a variant of [Server Side Request Forgery](https://cwe.mitre.org/data/definitions/918.html).
### Patches
The problem has been patched in the `micronaut-http-client` versions 1.2.11 and 1.3.2 and above.
### Workarounds
Do not pass user data directly received from HTTP request parameters as headers in the HTTP client.
### References
Fix commits
- https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1
- https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d
- https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [micronaut-core](https://github.com/micronaut-projects/micronaut-core)
* Email us at [info@micronaut.io](mailto:info@micronaut.io)
### Credit
Originally reported by @JLLeitschuh
| {'CVE-2020-7611'} | 2022-04-19T19:02:23Z | 2020-03-30T20:54:55Z | CRITICAL | 9.8 | {'CWE-444'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-7611', 'https://github.com/micronaut-projects/micronaut-core/security/advisories/GHSA-694p-xrhg-x3wm', 'https://snyk.io/vuln/SNYK-JAVA-IOMICRONAUT-561342', 'https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add', 'https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d', 'https://github.com/advisories/GHSA-694p-xrhg-x3wm', 'https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1'} | null | {'https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d', 'https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add', 'https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1'} | {'https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d', 'https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add', 'https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1'} |
GHSA | GHSA-4w23-c97g-fq5v | snipe-it is vulnerable to Cross-Site Request Forgery (CSRF) | snipe-it is vulnerable to Cross-Site Request Forgery (CSRF) | {'CVE-2021-4130'} | 2022-01-05T20:33:16Z | 2022-01-05T20:33:16Z | HIGH | 8.8 | {'CWE-352'} | {'https://huntr.dev/bounties/ccf073cd-7f54-4d51-89f2-6b4a2e4ae81e', 'https://github.com/advisories/GHSA-4w23-c97g-fq5v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4130', 'https://github.com/snipe/snipe-it/commit/9b2dd6522f214a3fbee6a4e32699104d0ea2b6ae'} | null | {'https://github.com/snipe/snipe-it/commit/9b2dd6522f214a3fbee6a4e32699104d0ea2b6ae'} | {'https://github.com/snipe/snipe-it/commit/9b2dd6522f214a3fbee6a4e32699104d0ea2b6ae'} |
GHSA | GHSA-pv4c-p2j5-38j4 | Open Redirect in url-parse | Versions of `url-parse` before 1.4.3 returns the wrong hostname which could lead to Open Redirect, Server Side Request Forgery (SSRF), or Bypass Authentication Protocol vulnerabilities.
## Recommendation
Update to version 1.4.3 or later. | {'CVE-2018-3774'} | 2021-01-08T18:18:31Z | 2018-08-13T15:02:15Z | HIGH | 0 | {'CWE-425'} | {'https://github.com/advisories/GHSA-pv4c-p2j5-38j4', 'https://hackerone.com/reports/384029', 'https://github.com/unshiftio/url-parse/commit/d7b582ec1243e8024e60ac0b62d2569c939ef5de', 'https://www.npmjs.com/advisories/678', 'https://github.com/unshiftio/url-parse/commit/53b1794e54d0711ceb52505e0f74145270570d5a', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3774'} | null | {'https://github.com/unshiftio/url-parse/commit/53b1794e54d0711ceb52505e0f74145270570d5a', 'https://github.com/unshiftio/url-parse/commit/d7b582ec1243e8024e60ac0b62d2569c939ef5de'} | {'https://github.com/unshiftio/url-parse/commit/d7b582ec1243e8024e60ac0b62d2569c939ef5de', 'https://github.com/unshiftio/url-parse/commit/53b1794e54d0711ceb52505e0f74145270570d5a'} |
GHSA | GHSA-phwq-j96m-2c2q | Template injection in ejs | The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation). | {'CVE-2022-29078'} | 2022-04-27T14:36:25Z | 2022-04-26T00:00:40Z | HIGH | 0 | {'CWE-74'} | {'https://github.com/mde/ejs/commit/15ee698583c98dadc456639d6245580d17a24baf', 'https://github.com/advisories/GHSA-phwq-j96m-2c2q', 'https://eslam.io/posts/ejs-server-side-template-injection-rce/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29078'} | null | {'https://github.com/mde/ejs/commit/15ee698583c98dadc456639d6245580d17a24baf'} | {'https://github.com/mde/ejs/commit/15ee698583c98dadc456639d6245580d17a24baf'} |
GHSA | GHSA-xw79-hhv6-578c | Cross-Site Scripting in serve | Versions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package does not encode output, allowing attackers to execute arbitrary JavaScript in the victim's browser if user-supplied input is rendered.
## Recommendation
Upgrade to version 10.0.2 or later. | null | 2021-09-28T16:54:34Z | 2020-09-11T21:16:59Z | HIGH | 0 | {'CWE-79'} | {'https://github.com/advisories/GHSA-xw79-hhv6-578c', 'https://github.com/zeit/serve-handler/commit/65b4d4183a31a8076c78c40118acb0ca1b64f620', 'https://hackerone.com/reports/358641', 'https://hackerone.com/reports/398285', 'https://www.npmjs.com/advisories/971'} | null | {'https://github.com/zeit/serve-handler/commit/65b4d4183a31a8076c78c40118acb0ca1b64f620'} | {'https://github.com/zeit/serve-handler/commit/65b4d4183a31a8076c78c40118acb0ca1b64f620'} |
GHSA | GHSA-xrpj-f9v6-2332 | CSV injection in Craft CMS | # Withdrawn
Duplicate of GHSA-h7vq-5qgw-jwwq | null | 2021-10-18T19:09:51Z | 2021-10-04T20:12:45Z | HIGH | 8.8 | {'CWE-1236', 'CWE-74'} | {'https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3714---2021-09-28', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41824', 'https://github.com/craftcms/cms/security/advisories/GHSA-h7vq-5qgw-jwwq', 'https://github.com/advisories/GHSA-xrpj-f9v6-2332', 'https://github.com/craftcms/cms/commit/c9cb2225f1b908fb1e8401d401219228634b26b2', 'https://twitter.com/craftcmsupdates/status/1442928690145366018'} | null | {'https://github.com/craftcms/cms/commit/c9cb2225f1b908fb1e8401d401219228634b26b2'} | {'https://github.com/craftcms/cms/commit/c9cb2225f1b908fb1e8401d401219228634b26b2'} |
GHSA | GHSA-v3q9-2p3m-7g43 | Token reuse in github.com/ory/fosite | ### Impact
When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion `jti`:
> A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
Hydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:
```
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM","expires_in":3599,"scope":"application openid","token_type":"bearer"}⏎
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4","expires_in":3599,"scope":"application openid","token_type":"bearer"}
```
### Patches
_Has the problem been patched? What versions should users upgrade to?_
### Workarounds
Do not allow clients to use `private_key_jwt`.
### References
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication | {'CVE-2020-15222'} | 2021-11-19T15:24:07Z | 2021-05-24T16:57:52Z | HIGH | 8.1 | {'CWE-287', 'CWE-345'} | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/advisories/GHSA-v3q9-2p3m-7g43', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15222', 'https://github.com/ory/fosite/releases/tag/v0.31.0', 'https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication'} | null | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9'} | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9'} |
GHSA | GHSA-5vq5-pg3r-9ph3 | Path Traversal in Zope | Zope is an open-source web application server. This advisory extends the previous advisory at https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36 with additional cases of TAL expression traversal vulnerabilities. Most Python modules are not available for using in TAL expressions that you can add through-the-web, for example in Zope Page Templates. This restriction avoids file system access, for example via the 'os' module. But some of the untrusted modules are available indirectly through Python modules that are available for direct use. By default, you need to have the Manager role to add or edit Zope Page Templates through the web. Only sites that allow untrusted users to add/edit Zope Page Templates through the web are at risk. The problem has been fixed in Zope 5.2.1 and 4.6.1. The workaround is the same as for https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36: A site administrator can restrict adding/editing Zope Page Templates through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing Zope Page Templates through the web should be restricted to trusted users only. | {'CVE-2021-32674'} | 2022-01-03T15:56:18Z | 2021-06-10T17:22:08Z | HIGH | 8.8 | {'CWE-12', 'CWE-22'} | {'https://github.com/advisories/GHSA-5vq5-pg3r-9ph3', 'https://github.com/zopefoundation/Zope/commit/1d897910139e2c0b11984fc9b78c1da1365bec21', 'https://github.com/zopefoundation/Zope/security/advisories/GHSA-rpcg-f9q6-2mq6', 'https://pypi.org/project/Zope/', 'https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32674'} | null | {'https://github.com/zopefoundation/Zope/commit/1d897910139e2c0b11984fc9b78c1da1365bec21'} | {'https://github.com/zopefoundation/Zope/commit/1d897910139e2c0b11984fc9b78c1da1365bec21'} |
GHSA | GHSA-pp7h-53gx-mx7r | Remote Memory Exposure in bl | A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls. | {'CVE-2020-8244'} | 2021-05-10T16:25:30Z | 2020-09-02T15:26:19Z | HIGH | 6.5 | {'CWE-126', 'CWE-125'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8244', 'https://github.com/rvagg/bl/commit/8a8c13c880e2bef519133ea43e0e9b78b5d0c91e', 'https://github.com/rvagg/bl/commit/dacc4ac7d5fcd6201bcf26fbd886951be9537466', 'https://github.com/advisories/GHSA-pp7h-53gx-mx7r', 'https://github.com/rvagg/bl/commit/d3e240e3b8ba4048d3c76ef5fb9dd1f8872d3190', 'https://hackerone.com/reports/966347'} | null | {'https://github.com/rvagg/bl/commit/8a8c13c880e2bef519133ea43e0e9b78b5d0c91e', 'https://github.com/rvagg/bl/commit/dacc4ac7d5fcd6201bcf26fbd886951be9537466', 'https://github.com/rvagg/bl/commit/d3e240e3b8ba4048d3c76ef5fb9dd1f8872d3190'} | {'https://github.com/rvagg/bl/commit/d3e240e3b8ba4048d3c76ef5fb9dd1f8872d3190', 'https://github.com/rvagg/bl/commit/8a8c13c880e2bef519133ea43e0e9b78b5d0c91e', 'https://github.com/rvagg/bl/commit/dacc4ac7d5fcd6201bcf26fbd886951be9537466'} |
GHSA | GHSA-7wgr-7666-7pwj | Path Traversal in openapi-python-client | ### Impact
Path traversal vulnerability. If a user generated a client using a maliciously crafted OpenAPI document, it is possible for generated files to be placed in arbitrary locations on disk.
Giving this a CVSS score of 3.0 (Low) with CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N/E:P/RL:U/RC:C
### Patches
A fix is being worked on for version 0.5.3
### Workarounds
Inspect OpenAPI documents before generating clients for them.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [openapi-python-client](https://github.com/triaxtec/openapi-python-client/issues)
* Email us at [danthony@triaxtec.com](mailto:danthony@triaxtec.com) | {'CVE-2020-15141'} | 2022-04-19T19:02:33Z | 2020-08-20T14:38:13Z | LOW | 3 | {'CWE-22'} | {'https://github.com/triaxtec/openapi-python-client/blob/main/CHANGELOG.md#053---2020-08-13', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15141', 'https://pypi.org/project/openapi-python-client', 'https://github.com/triaxtec/openapi-python-client/commit/3e7dfae5d0b3685abf1ede1bc6c086a116ac4746', 'https://github.com/triaxtec/openapi-python-client/security/advisories/GHSA-7wgr-7666-7pwj', 'https://github.com/advisories/GHSA-7wgr-7666-7pwj', 'https://pypi.org/project/openapi-python-client/'} | null | {'https://github.com/triaxtec/openapi-python-client/commit/3e7dfae5d0b3685abf1ede1bc6c086a116ac4746'} | {'https://github.com/triaxtec/openapi-python-client/commit/3e7dfae5d0b3685abf1ede1bc6c086a116ac4746'} |
GHSA | GHSA-7v7w-f7c6-f829 | yetiforcecrm is vulnerable to Business Logic Errors | yetiforcecrm is vulnerable to Business Logic Errors. | {'CVE-2021-4111'} | 2022-01-03T15:47:59Z | 2021-12-16T21:01:15Z | HIGH | 7.3 | null | {'https://github.com/advisories/GHSA-7v7w-f7c6-f829', 'https://github.com/yetiforcecompany/yetiforcecrm/commit/c1ad7111a090adfcd5898af40724907adc987acf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4111', 'https://huntr.dev/bounties/8afc8981-baff-4082-b640-be535b29eb9a'} | null | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/c1ad7111a090adfcd5898af40724907adc987acf'} | {'https://github.com/yetiforcecompany/yetiforcecrm/commit/c1ad7111a090adfcd5898af40724907adc987acf'} |
GHSA | GHSA-952p-fqcp-g8pc | HTML injection possibility in voucher code form in Shopware | ### Impact
HTML injection possibility in voucher code form
## Patches
Patched in 6.4.8.1, maintainers recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
## Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version. | {'CVE-2022-24746'} | 2022-03-18T20:14:16Z | 2022-03-10T17:49:26Z | MODERATE | 6.1 | {'CWE-79'} | {'https://github.com/shopware/platform/commit/651598a61073cbe59368e311817bdc6e7fb349c6', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2022?category=security-updates', 'https://github.com/advisories/GHSA-952p-fqcp-g8pc', 'https://github.com/shopware/platform/security/advisories/GHSA-952p-fqcp-g8pc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24746', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2022'} | null | {'https://github.com/shopware/platform/commit/651598a61073cbe59368e311817bdc6e7fb349c6'} | {'https://github.com/shopware/platform/commit/651598a61073cbe59368e311817bdc6e7fb349c6'} |
GHSA | GHSA-jhj6-5mh6-4pvf | Denial-of-Service within Docker container | ### Impact
If you run teler inside a Docker container and encounter `errors.Exit` function, it will cause denial-of-service (`SIGSEGV`) because it doesn't get process ID and process group ID of teler properly to kills.
### Patches
Upgrade to the >= 0.0.1 version.
### Workarounds
N/A
### References
- https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Issues Section](https://github.com/kitabisa/teler/issues)
* Email us at [infosec@kitabisa.com](mailto:infosec@kitabisa.com)
| {'CVE-2020-26213'} | 2021-10-11T21:06:20Z | 2021-05-24T17:00:46Z | MODERATE | 7.5 | {'CWE-476'} | {'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e', 'https://github.com/advisories/GHSA-jhj6-5mh6-4pvf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26213', 'https://github.com/kitabisa/teler/security/advisories/GHSA-jhj6-5mh6-4pvf'} | null | {'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e'} | {'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e'} |
GHSA | GHSA-45q2-34rf-mr94 | Code Injection in mquery | lib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., __proto__) can be copied during a merge or clone operation. | {'CVE-2020-35149'} | 2020-12-18T18:23:43Z | 2020-12-18T18:23:43Z | MODERATE | 5.3 | {'CWE-94'} | {'https://github.com/aheckmann/mquery/commit/792e69fd0a7281a0300be5cade5a6d7c1d468ad4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35149', 'https://github.com/advisories/GHSA-45q2-34rf-mr94'} | null | {'https://github.com/aheckmann/mquery/commit/792e69fd0a7281a0300be5cade5a6d7c1d468ad4'} | {'https://github.com/aheckmann/mquery/commit/792e69fd0a7281a0300be5cade5a6d7c1d468ad4'} |
GHSA | GHSA-9735-p6r2-2hgh | Out-of-bounds write | A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0884, CVE-2019-0918. | {'CVE-2019-0911'} | 2021-03-29T21:00:00Z | 2021-03-29T21:00:00Z | HIGH | 7.5 | {'CWE-787'} | {'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0911', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0911', 'https://github.com/chakra-core/ChakraCore/commit/a2deba5e1850782014a2a34678464b251e448337', 'https://github.com/advisories/GHSA-9735-p6r2-2hgh'} | null | {'https://github.com/chakra-core/ChakraCore/commit/a2deba5e1850782014a2a34678464b251e448337', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7'} | {'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/a2deba5e1850782014a2a34678464b251e448337'} |
GHSA | GHSA-c38g-469g-cmgx | "Improper Neutralization of Special Elements in Output in helm.sh/helm/v3" |
Since Helm 2 was released, a well-documented aspect of Helm is that the Helm chart's version number MUST follow the SemVer2 specification. In the past, Helm would not permit charts with malformed versions. At some point, a patch was merged that changed this - On a version parse error, the version number was simply passed along as-is. This provided a vector for malicious data to be injected into Helm and potentially used in various ways.
Core maintainers were able to send deceptive information to a terminal screen running the `helm` command, as well as obscure or alter information on the screen. In some cases, we could send codes that terminals used to execute higher-order logic, like clearing a terminal screen.
Further, during evaluation, the Helm maintainers discovered a few other fields that were not properly sanitized when read out of repository index files. This fix remedies all such cases, and once again enforces SemVer2 policies on version fields.
All users of the Helm 3 should upgrade.
Those who use Helm as a library should verify that they either sanitize this data on their own, or use the proper Helm API calls to sanitize the data.
### Patches
This issue has been resolved in Helm 3.5.1.
While this fix does not constitute a breaking change, as all field formatting is now enforced as documented, it is possible that charts that were mistakenly allowed (but invalid) may no longer be available in search indexes. Specifically, **malformed SemVer versions are no longer supported**. This has always been the documented case, but it is true that malformed versions were allowed.
Note that this is the first security release since Helm 2's final deprecation. Helm 2 was not audited for vulnerability to this issue, and should be assumed vulnerable. | {'CVE-2021-21303'} | 2021-06-23T18:14:40Z | 2021-06-23T18:14:40Z | MODERATE | 5.9 | {'CWE-74', 'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-21303', 'https://github.com/helm/helm/releases/tag/v3.5.2', 'https://github.com/helm/helm/commit/6ce9ba60b73013857e2e7c73d3f86ed70bc1ac9a', 'https://github.com/helm/helm/security/advisories/GHSA-c38g-469g-cmgx', 'https://github.com/advisories/GHSA-c38g-469g-cmgx'} | null | {'https://github.com/helm/helm/commit/6ce9ba60b73013857e2e7c73d3f86ed70bc1ac9a'} | {'https://github.com/helm/helm/commit/6ce9ba60b73013857e2e7c73d3f86ed70bc1ac9a'} |
GHSA | GHSA-733f-44f3-3frw | Open redirect | macaron before 1.3.7 has an open redirect in the static handler, as demonstrated by the http://127.0.0.1:4000//example.com/ URL. | {'CVE-2020-12666'} | 2021-05-18T21:08:35Z | 2021-05-18T21:08:35Z | MODERATE | 6.1 | {'CWE-601'} | {'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7', 'https://github.com/go-macaron/macaron/releases/tag/v1.3.7', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12666', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3QEUOHRC4EN4WZ66EVFML2UCV7ZQ63XZ/', 'https://github.com/advisories/GHSA-733f-44f3-3frw', 'https://github.com/go-macaron/macaron/issues/198#issuecomment-622885959', 'https://github.com/go-macaron/macaron/issues/198'} | null | {'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7'} | {'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7'} |
GHSA | GHSA-hxcm-v35h-mg2x | Prototype Pollution | A vulnerability was found in querystringify before 2.0.0. It's possible to override built-in properties of the resulting query string object if a malicious string is inserted in the query string. | null | 2021-02-25T17:25:44Z | 2019-06-07T21:12:50Z | HIGH | 0 | {'CWE-1312'} | {'https://github.com/unshiftio/querystringify/pull/19', 'https://github.com/unshiftio/querystringify/commit/422eb4f6c7c28ee5f100dcc64177d3b68bb2b080', 'https://github.com/advisories/GHSA-hxcm-v35h-mg2x'} | null | {'https://github.com/unshiftio/querystringify/commit/422eb4f6c7c28ee5f100dcc64177d3b68bb2b080'} | {'https://github.com/unshiftio/querystringify/commit/422eb4f6c7c28ee5f100dcc64177d3b68bb2b080'} |
GHSA | GHSA-699q-wcff-g9mj | Unsafe deserialization in Yii 2 | ### Impact
Remote code execution in case application calls `unserialize()` on user input containing specially crafted string.
### Patches
2.0.38
### Workarounds
Add the following to BatchQueryResult.php:
```php
public function __sleep()
{
throw new \BadMethodCallException('Cannot serialize '.__CLASS__);
}
public function __wakeup()
{
throw new \BadMethodCallException('Cannot unserialize '.__CLASS__);
}
```
### For more information
If you have any questions or comments about this advisory, [contact us through security form](https://www.yiiframework.com/security). | {'CVE-2020-15148'} | 2022-04-19T19:02:33Z | 2020-09-15T18:19:56Z | HIGH | 8.9 | {'CWE-502'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15148', 'https://github.com/yiisoft/yii2/security/advisories/GHSA-699q-wcff-g9mj', 'https://github.com/yiisoft/yii2/commit/9abccb96d7c5ddb569f92d1a748f50ee9b3e2b99', 'https://github.com/advisories/GHSA-699q-wcff-g9mj'} | null | {'https://github.com/yiisoft/yii2/commit/9abccb96d7c5ddb569f92d1a748f50ee9b3e2b99'} | {'https://github.com/yiisoft/yii2/commit/9abccb96d7c5ddb569f92d1a748f50ee9b3e2b99'} |
GHSA | GHSA-pcqq-5962-hvcw | Denial of Service in uap-core when processing crafted User-Agent strings | ### Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
### Patches
Please update `uap-ruby` to >= v2.6.0
### For more information
https://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p
Reported in `uap-core` by Ben Caller @bcaller | null | 2022-04-19T19:02:24Z | 2020-03-10T18:02:49Z | HIGH | 0 | null | {'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a', 'https://github.com/ua-parser/uap-ruby/security/advisories/GHSA-pcqq-5962-hvcw', 'https://github.com/advisories/GHSA-pcqq-5962-hvcw'} | null | {'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a'} | {'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a'} |
GHSA | GHSA-5jxc-hmqf-3f73 | Cross-Site Scripting in grav | grav prior to version 1.7.24 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). | {'CVE-2021-3904'} | 2021-11-01T19:17:31Z | 2021-11-01T19:17:31Z | MODERATE | 6.3 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3904', 'https://github.com/getgrav/grav/commit/afc69a3229bb6fe120b2c1ea27bc6f196ed7284d', 'https://github.com/advisories/GHSA-5jxc-hmqf-3f73', 'https://huntr.dev/bounties/b1182515-d911-4da9-b4f7-b4c341a62a8d'} | null | {'https://github.com/getgrav/grav/commit/afc69a3229bb6fe120b2c1ea27bc6f196ed7284d'} | {'https://github.com/getgrav/grav/commit/afc69a3229bb6fe120b2c1ea27bc6f196ed7284d'} |
GHSA | GHSA-xf5p-87ch-gxw2 | Regular Expression Denial of Service in marked | Versions of `marked` prior to 0.6.2 and later than 0.3.14 are vulnerable to Regular Expression Denial of Service. Email addresses may be evaluated in quadratic time, allowing attackers to potentially crash the node process due to resource exhaustion.
## Recommendation
Upgrade to version 0.6.2 or later. | null | 2021-08-04T20:53:01Z | 2019-06-05T14:10:03Z | MODERATE | 5.3 | {'CWE-400'} | {'https://www.npmjs.com/advisories/812', 'https://github.com/markedjs/marked/issues/1070', 'https://github.com/markedjs/marked/pull/1460', 'https://snyk.io/vuln/SNYK-JS-MARKED-174116', 'https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d', 'https://github.com/advisories/GHSA-xf5p-87ch-gxw2'} | null | {'https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d'} | {'https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d'} |
GHSA | GHSA-h74j-692g-48mq | Path Traversal in MHolt Archiver | All versions of archiver allow attacker to perform a Zip Slip attack via the "unarchive" functions. It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily. | {'CVE-2019-10743'} | 2021-05-18T15:31:53Z | 2021-05-18T15:31:53Z | MODERATE | 5.5 | {'CWE-29'} | {'https://github.com/advisories/GHSA-h74j-692g-48mq', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10743', 'https://github.com/mholt/archiver/pull/169', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARC-174728,', 'https://github.com/snyk/zip-slip-vulnerability', 'https://github.com/mholt/archiver/pull/203', 'https://github.com/mholt/archiver/commit/8217ed3a206c0473b4ec1aff51375b398838073a', 'https://snyk.io/research/zip-slip-vulnerability'} | null | {'https://github.com/mholt/archiver/commit/8217ed3a206c0473b4ec1aff51375b398838073a'} | {'https://github.com/mholt/archiver/commit/8217ed3a206c0473b4ec1aff51375b398838073a'} |
GHSA | GHSA-fp63-499m-hq6m | Files or Directories Accessible to External Parties in ether/logs | ### Impact
A vulnerability was found that allowed authenticated admin users to access any file on the server.
### Patches
The vulnerability has been fixed in 3.0.4.
### Workarounds
We recommend disabling the plugin if untrustworthy sources have admin access.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [ether/logs](https://github.com/ethercreative/logs/issues)
| {'CVE-2021-32752'} | 2021-07-12T23:09:42Z | 2021-07-12T16:53:00Z | HIGH | 7.2 | {'CWE-552'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-32752', 'https://github.com/ethercreative/logs/security/advisories/GHSA-fp63-499m-hq6m', 'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4', 'https://github.com/ethercreative/logs/releases/tag/3.0.4', 'https://github.com/advisories/GHSA-fp63-499m-hq6m'} | null | {'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4'} | {'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4'} |
GHSA | GHSA-g98m-96g9-wfjq | Insecure path handling in Bundler | Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed. | {'CVE-2019-3881'} | 2021-11-03T14:52:01Z | 2021-05-10T14:53:59Z | HIGH | 7 | {'CWE-552', 'CWE-427'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-3881', 'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998', 'https://github.com/advisories/GHSA-g98m-96g9-wfjq', 'https://bugzilla.redhat.com/show_bug.cgi?id=1651826', 'https://github.com/rubygems/bundler/issues/6501'} | null | {'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998'} | {'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998'} |
GHSA | GHSA-3vjf-82ff-p4r3 | Incorrect protocol extraction via \r, \n and \t characters | \r, \n and \t characters in user-input URLs can potentially lead to incorrect protocol extraction when using npm package urijs prior to version 1.19.11.
This can lead to XSS when the module is used to prevent passing in malicious javascript: links into HTML or Javascript (see following example):
````
const parse = require('urijs')
const express = require('express')
const app = express()
const port = 3000
input = "ja\r\nvascript:alert(1)"
url = parse(input)
console.log(url)
app.get('/', (req, res) => {
if (url.protocol !== "javascript:") {res.send("<iframe src=\'" + input + "\'>CLICK ME!</iframe>")}
})
app.listen(port, () => {
console.log(`Example app listening on port ${port}`)
})
```` | {'CVE-2022-1243'} | 2022-04-14T20:13:56Z | 2022-04-06T00:01:31Z | HIGH | 7.2 | {'CWE-20'} | {'https://github.com/advisories/GHSA-3vjf-82ff-p4r3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1243', 'https://huntr.dev/bounties/8c5afc47-1553-4eba-a98e-024e4cc3dfb7', 'https://github.com/medialize/uri.js/commit/b0c9796aa1a95a85f40924fb18b1e5da3dc8ffae'} | null | {'https://github.com/medialize/uri.js/commit/b0c9796aa1a95a85f40924fb18b1e5da3dc8ffae'} | {'https://github.com/medialize/uri.js/commit/b0c9796aa1a95a85f40924fb18b1e5da3dc8ffae'} |
GHSA | GHSA-m697-4v8f-55qg | Header dropping in traefik | # Impact
There exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.
# Details
If you have a chain of Traefik middlewares, and one of them sets a request header `Important-Security-Header`, then sending a request with the following Connection header will cause it to be removed before the request was sent:
```
curl 'https://example.com' -H "Connection: Important-Security-Header" -0
```
In this case, the backend does not see the request header `Important-Security-Header`.
# Patches
Traefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13
# Workarounds
No.
# For more information
If you have any questions or comments about this advisory, [open an issue](https://github.com/traefik/traefik/issues).
| {'CVE-2021-32813'} | 2021-08-31T20:57:11Z | 2021-08-05T17:04:21Z | MODERATE | 4.8 | {'CWE-913'} | {'https://github.com/traefik/traefik/releases/tag/v2.4.13', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32813', 'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9', 'https://github.com/traefik/traefik/security/advisories/GHSA-m697-4v8f-55qg', 'https://github.com/advisories/GHSA-m697-4v8f-55qg'} | null | {'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9'} | {'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9'} |
GHSA | GHSA-2877-693q-pj33 | OS Command Injection in GenieACS | In GenieACS 1.2.x before 1.2.8, the UI interface API is vulnerable to unauthenticated OS command injection via the ping host argument (lib/ui/api.ts and lib/ping.ts). The vulnerability arises from insufficient input validation combined with a missing authorization check. | {'CVE-2021-46704'} | 2022-03-14T21:30:23Z | 2022-03-07T00:00:40Z | CRITICAL | 9.8 | {'CWE-78'} | {'https://github.com/genieacs/genieacs/commit/7f295beeecc1c1f14308a93c82413bb334045af6', 'https://github.com/genieacs/genieacs/releases/tag/v1.2.8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46704', 'https://github.com/advisories/GHSA-2877-693q-pj33'} | null | {'https://github.com/genieacs/genieacs/commit/7f295beeecc1c1f14308a93c82413bb334045af6'} | {'https://github.com/genieacs/genieacs/commit/7f295beeecc1c1f14308a93c82413bb334045af6'} |
GHSA | GHSA-j4f2-536g-r55m | Resource exhaustion in engine.io | Engine.IO before 4.0.0 allows attackers to cause a denial of service (resource consumption) via a POST request to the long polling transport. | {'CVE-2020-36048'} | 2022-02-09T22:29:04Z | 2022-02-09T22:29:04Z | HIGH | 7.5 | {'CWE-400'} | {'https://github.com/socketio/engine.io/commit/734f9d1268840722c41219e69eb58318e0b2ac6b', 'https://github.com/bcaller/kill-engine-io', 'https://blog.caller.xyz/socketio-engineio-dos/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36048', 'https://github.com/advisories/GHSA-j4f2-536g-r55m'} | null | {'https://github.com/socketio/engine.io/commit/734f9d1268840722c41219e69eb58318e0b2ac6b'} | {'https://github.com/socketio/engine.io/commit/734f9d1268840722c41219e69eb58318e0b2ac6b'} |
GHSA | GHSA-88jf-7rch-32qc | Path Traversal in github.com/unknwon/cae/tz | "The ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading "..". This allows an attacker to add or replace files system-wide." | {'CVE-2020-7668'} | 2022-01-04T19:33:15Z | 2021-05-18T20:31:18Z | HIGH | 7.5 | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAETZ-570384', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7668', 'https://github.com/advisories/GHSA-88jf-7rch-32qc', 'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | null | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} |
GHSA | GHSA-c45w-2wxr-pp53 | Heap OOB read in `tf.raw_ops.Dequantize` | ### Impact
Due to lack of validation in `tf.raw_ops.Dequantize`, an attacker can trigger a read from outside of bounds of heap allocated data:
```python
import tensorflow as tf
input_tensor=tf.constant(
[75, 75, 75, 75, -6, -9, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\
-10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\
-10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\
-10, -10, -10, -10], shape=[5, 10], dtype=tf.int32)
input_tensor=tf.cast(input_tensor, dtype=tf.quint8)
min_range = tf.constant([-10], shape=[1], dtype=tf.float32)
max_range = tf.constant([24, 758, 758, 758, 758], shape=[5], dtype=tf.float32)
tf.raw_ops.Dequantize(
input=input_tensor, min_range=min_range, max_range=max_range, mode='SCALED',
narrow_range=True, axis=0, dtype=tf.dtypes.float32)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/26003593aa94b1742f34dc22ce88a1e17776a67d/tensorflow/core/kernels/dequantize_op.cc#L106-L131) accesses the `min_range` and `max_range` tensors in parallel but fails to check that they have the same shape:
```cc
if (num_slices == 1) {
const float min_range = input_min_tensor.flat<float>()(0);
const float max_range = input_max_tensor.flat<float>()(0);
DequantizeTensor(ctx, input, min_range, max_range, &float_output);
} else {
...
auto min_ranges = input_min_tensor.vec<float>();
auto max_ranges = input_max_tensor.vec<float>();
for (int i = 0; i < num_slices; ++i) {
DequantizeSlice(ctx->eigen_device<Device>(), ctx,
input_tensor.template chip<1>(i), min_ranges(i),
max_ranges(i), output_tensor.template chip<1>(i));
...
}
}
```
### Patches
We have patched the issue in GitHub commit [5899741d0421391ca878da47907b1452f06aaf1b](https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b).
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-29582'} | 2021-05-21T14:26:32Z | 2021-05-21T14:26:32Z | LOW | 2.5 | {'CWE-125'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c45w-2wxr-pp53', 'https://github.com/advisories/GHSA-c45w-2wxr-pp53', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29582', 'https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b'} | null | {'https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b'} | {'https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b'} |
GHSA | GHSA-w4vg-rf63-f3j3 | Arbitrary code using "crafted image file" approach affecting Pillow | Pillow before 3.3.2 allows context-dependent attackers to execute arbitrary code by using the "crafted image file" approach, related to an "Insecure Sign Extension" issue affecting the ImagingNew in Storage.c component. | {'CVE-2016-9190'} | 2022-04-26T18:06:20Z | 2018-07-12T14:45:42Z | HIGH | 7.8 | {'CWE-284'} | {'https://github.com/python-pillow/Pillow/pull/2146/commits/5d8a0be45aad78c5a22c8d099118ee26ef8144af', 'http://pillow.readthedocs.io/en/3.4.x/releasenotes/3.3.2.html', 'http://www.securityfocus.com/bid/94234', 'https://security.gentoo.org/glsa/201612-52', 'https://github.com/python-pillow/Pillow/issues/2105', 'http://www.debian.org/security/2016/dsa-3710', 'https://github.com/advisories/GHSA-w4vg-rf63-f3j3', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9190'} | null | {'https://github.com/python-pillow/Pillow/pull/2146/commits/5d8a0be45aad78c5a22c8d099118ee26ef8144af'} | {'https://github.com/python-pillow/Pillow/pull/2146/commits/5d8a0be45aad78c5a22c8d099118ee26ef8144af'} |
GHSA | GHSA-5vfx-8w6m-h3v4 | Authentication bypass due to improper user-provided security token verification | A malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user.
## Impact
Due to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user.
This controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`.
There are a few different areas of the Panel that store values into the cache that are integers, and a user who determines what those cache keys are could pass one of those keys which would cause this code pathway to reference an arbitrary user.
## Scope
At its heart this is a high-risk login bypass vulnerability. However, there are a few additional conditions that must be met in order for this to be successfully executed, notably:
1.) The account referenced by the malicious cache key **must** have two-factor authentication enabled. An account without two-factor authentication would cause an exception to be triggered by the authentication logic, thusly exiting this authentication flow.
2.) Even if the malicious user is able to reference a valid cache key that references a valid user account with two-factor authentication, they **must** provide a valid two-factor authentication token.
However, due to the design of this endpoint once a valid user account is found with two-factor authentication enabled there is no rate-limiting present, thusly allowing an attacker to brute force combinations until successful. This leads to a third condition that must be met:
3.) For the duration of this attack sequence the cache key being referenced must continue to exist with a valid `user_id` value. Depending on the specific key being used for this attack, this value may disappear quickly, or be changed by other random user interactions on the Panel, outside the control of the attacker.
### About the Severity
As you may have noticed, this is not a trivial authentication bypass bug to exploit, and is likely incredibly difficult for a layperson to pull off. However, the severity of this disclosure has been prepared based on the nature of the bug and the potential for unexpected administrative account access under very rare conditions.
## Mitigation
In order to mitigate this vulnerability the underlying authentication logic was changed to use an encrypted session store that the user is therefore unable to control the value of. This completely removed the use of a user-controlled value being used. In addition, the code was audited to ensure this type of vulnerability is not present elsewhere.
If you have any questions or concerns about the content of this disclosure please contact `Tactical Fish#8008` on Discord, or email `dane ät pterodactyl.io`. | {'CVE-2021-41129'} | 2021-10-12T21:45:12Z | 2021-10-04T20:14:13Z | HIGH | 8.1 | {'CWE-502', 'CWE-639', 'CWE-807'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41129', 'https://github.com/pterodactyl/panel/blob/v1.6.2/CHANGELOG.md#v162', 'https://github.com/pterodactyl/panel/releases/tag/v1.6.2', 'https://github.com/pterodactyl/panel/security/advisories/GHSA-5vfx-8w6m-h3v4', 'https://github.com/advisories/GHSA-5vfx-8w6m-h3v4', 'https://github.com/pterodactyl/panel/commit/4a84c36009be10dbd83051ac1771662c056e4977'} | null | {'https://github.com/pterodactyl/panel/commit/4a84c36009be10dbd83051ac1771662c056e4977'} | {'https://github.com/pterodactyl/panel/commit/4a84c36009be10dbd83051ac1771662c056e4977'} |
GHSA | GHSA-9vp5-m38w-j776 | Aliases are never checked in helm | ### Impact
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart.
### Patches
This issue has been patched in Helm 3.3.2 and 2.16.11
### Workarounds
Manually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters. | {'CVE-2020-15184'} | 2021-11-19T15:29:13Z | 2021-05-24T16:56:58Z | LOW | 3.7 | {'CWE-74', 'CWE-20'} | {'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm/security/advisories/GHSA-9vp5-m38w-j776', 'https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15184', 'https://github.com/advisories/GHSA-9vp5-m38w-j776'} | null | {'https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946'} | {'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850'} |
GHSA | GHSA-vgmw-9cww-qq99 | Incorrect Authorization in calibreweb | calibreweb prior to version 0.6.16 contains an Incorrect Authorization vulnerability. | {'CVE-2022-0273'} | 2022-02-16T22:04:14Z | 2022-01-31T00:00:29Z | MODERATE | 6.5 | {'CWE-863', 'CWE-284'} | {'https://github.com/advisories/GHSA-vgmw-9cww-qq99', 'https://huntr.dev/bounties/8f27686f-d698-4ab6-8ef0-899125792f13', 'https://github.com/janeczku/calibre-web/commit/0c0313f375bed7b035c8c0482bbb09599e16bfcf', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0273'} | null | {'https://github.com/janeczku/calibre-web/commit/0c0313f375bed7b035c8c0482bbb09599e16bfcf'} | {'https://github.com/janeczku/calibre-web/commit/0c0313f375bed7b035c8c0482bbb09599e16bfcf'} |
GHSA | GHSA-54xj-q58h-9x57 | Arbitrary File Write in iobroker.admin | Versions of `iobroker.admin` prior to 3.6.12 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended folder in the `/log/` route, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.
## Recommendation
Upgrade to version 3.6.12 or later. | {'CVE-2019-10765'} | 2021-10-01T20:14:11Z | 2020-09-04T15:24:56Z | CRITICAL | 9.8 | {'CWE-22'} | {'https://github.com/advisories/GHSA-54xj-q58h-9x57', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10765', 'https://www.npmjs.com/advisories/1346', 'https://snyk.io/vuln/SNYK-JS-IOBROKERADMIN-534634', 'https://github.com/ioBroker/ioBroker.admin/commit/16b2b325ab47896090bc7f54b77b0a97ed74f5cd'} | null | {'https://github.com/ioBroker/ioBroker.admin/commit/16b2b325ab47896090bc7f54b77b0a97ed74f5cd'} | {'https://github.com/ioBroker/ioBroker.admin/commit/16b2b325ab47896090bc7f54b77b0a97ed74f5cd'} |
GHSA | GHSA-3qgw-p4fm-x7gf | Division by zero in TFLite's convolution code | ### Impact
TFLite's [convolution code](https://github.com/tensorflow/tensorflow/blob/09c73bca7d648e961dd05898292d91a8322a9d45/tensorflow/lite/kernels/conv.cc) has multiple division where the divisor is controlled by the user and not checked to be non-zero. For example:
```cc
const int input_size = NumElements(input) / SizeOfDimension(input, 0);
```
### Patches
We have patched the issue in GitHub commit [ff489d95a9006be080ad14feb378f2b4dac35552](https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552).
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-29594'} | 2021-05-21T14:27:45Z | 2021-05-21T14:27:45Z | LOW | 2.5 | {'CWE-369'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3qgw-p4fm-x7gf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29594', 'https://github.com/advisories/GHSA-3qgw-p4fm-x7gf', 'https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552'} | null | {'https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552'} | {'https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552'} |
GHSA | GHSA-53m6-44rc-h2q5 | Missing server signature validation in OctoberCMS | ### Impact
This advisory affects authors of plugins and themes listed on the October CMS marketplace where an end-user will inadvertently expose authors to potential financial loss by entering their private license key into a compromised server.
It has been disclosed that a project fork of October CMS v1.0 is using a compromised gateway to access the October CMS marketplace service. The compromised gateway captures the personal/business information of users and authors, including private source code files. It was also disclosed that captured plugin files are freely redistributed to other users without authorization.
1. End-users are provided with a forked version of October CMS v1.0. The provided software is modified to use a compromised gateway server.
2. The user is instructed to enter their October CMS license key into the administration panel to access the October CMS marketplace. The key is sent to the compromised server while appearing to access the genuine October CMS gateway server.
3. The compromised gateway server uses a "man in the middle" mechanism that captures information while forwarding the request to the genuine October CMS gateway and relaying the response back to the client.
4. The compromised gateway server stores the license key and other information about the user account including client name, email address and contents of purchased plugins and privately uploaded plugin files.
5. The stored plugin files are made available to other users of the compromised gateway server.
### Patches
The issue has been patched in Build 475 (v1.0.475) and v1.1.11.
### Workarounds
Apply https://github.com/octobercms/october/commit/e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a to your installation manually if unable to upgrade to Build 475 or v1.1.11.
### Recommendations
We recommend the following steps to make sure your account information stays secure:
- Do not share your license key with anyone except October CMS.
- Check to make sure that your gateway update server has not been modified.
- Be aware of phishing websites, including other platforms that use the same appearance.
- For authors, you may contact us for help requesting the removal of affected plugins.
- Before providing plugin support, verify that the user holds a legitimate copy of the plugin.
### References
Credits for research on this exploit:
• Nikita Khaetsky
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com) | {'CVE-2022-23655'} | 2022-03-08T18:23:38Z | 2022-02-24T13:09:30Z | MODERATE | 4.8 | {'CWE-347'} | {'https://github.com/octobercms/october/security/advisories/GHSA-53m6-44rc-h2q5', 'https://github.com/octobercms/october/commit/e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a', 'https://github.com/advisories/GHSA-53m6-44rc-h2q5', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23655'} | null | {'https://github.com/octobercms/october/commit/e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a'} | {'https://github.com/octobercms/october/commit/e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.