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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RubyGems | GHSA-ggxm-pgc9-g7fp | Arbitrary Code Execution in rdoc | In RDoc 3.11 through 6.x before 6.3.1, as distributed with Ruby through 3.0.1, it is possible to execute arbitrary code via | and tags in a filename. | {'CVE-2021-31799'} | 2022-04-22T15:47:43.374950Z | 2021-09-01T18:53:15Z | HIGH | null | {'CWE-74', 'CWE-77'} | {'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://github.com/ruby/rdoc/commit/a7f5d6ab88632b3b482fe10611382ff73d14eed7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31799', 'https://security.netapp.com/advisory/ntap-20210902-0004/', 'https://security-tracker.debian.org/tracker/CVE-2021-31799', 'https://github.com/ruby/rdoc', 'https://www.ruby-lang.org/en/news/2021/05/02/os-command-injection-in-rdoc/', 'https://lists.debian.org/debian-lts-announce/2021/10/msg00009.html'} | null | {'https://github.com/ruby/rdoc/commit/a7f5d6ab88632b3b482fe10611382ff73d14eed7'} | {'https://github.com/ruby/rdoc/commit/a7f5d6ab88632b3b482fe10611382ff73d14eed7'} |
RubyGems | GHSA-fwcm-636p-68r5 | Server-side request forgery in CarrierWave | ### Impact
[CarrierWave download feature](https://github.com/carrierwaveuploader/carrierwave#uploading-files-from-a-remote-location) has an SSRF vulnerability, allowing attacks to provide DNS entries or IP addresses that are intended for internal use and gather information about the Intranet infrastructure of the platform.
### Patches
Upgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).
### Workarounds
Using proper network segmentation and applying the principle of least privilege to outbound connections from application servers can reduce the severity of SSRF vulnerabilities. Ideally the vulnerable gem should run on an isolated server without access to any internal network resources or cloud metadata access.
### References
[Server-Side Request Forgery Prevention Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)
* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com) | {'CVE-2021-21288'} | 2022-03-03T05:13:46.424790Z | 2021-02-08T19:16:26Z | LOW | null | {'CWE-918'} | {'https://github.com/carrierwaveuploader/carrierwave/blob/master/CHANGELOG.md#211---2021-02-08', 'https://github.com/carrierwaveuploader/carrierwave/security/advisories/GHSA-fwcm-636p-68r5', 'https://rubygems.org/gems/carrierwave/', 'https://github.com/carrierwaveuploader/carrierwave/blob/master/CHANGELOG.md#132---2021-02-08', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21288', 'https://github.com/carrierwaveuploader/carrierwave/commit/012702eb3ba1663452aa025831caa304d1a665c0'} | null | {'https://github.com/carrierwaveuploader/carrierwave/commit/012702eb3ba1663452aa025831caa304d1a665c0'} | {'https://github.com/carrierwaveuploader/carrierwave/commit/012702eb3ba1663452aa025831caa304d1a665c0'} |
RubyGems | GHSA-x3rq-r3cm-5vc4 | Business Logic Errors in Publify | Publify (formerly known as Typo) prior to version 9.2.7 is vulnerable to business logic errors. | {'CVE-2022-0524'} | 2022-03-03T05:12:56.204589Z | 2022-02-09T00:00:27Z | HIGH | null | null | {'https://huntr.dev/bounties/bfffae58-b3cd-4e0e-b1f2-3db387a22c3d', 'https://github.com/publify/publify/', 'https://github.com/publify/publify/releases/tag/v9.2.7', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0524', 'https://github.com/publify/publify/commit/16fceecadbe80ab0ef846b62a12dc7bfff10b8c5'} | null | {'https://github.com/publify/publify/commit/16fceecadbe80ab0ef846b62a12dc7bfff10b8c5'} | {'https://github.com/publify/publify/commit/16fceecadbe80ab0ef846b62a12dc7bfff10b8c5'} |
RubyGems | GHSA-g89m-3wjw-h857 | Low severity vulnerability that affects puppet | Directory traversal vulnerability in lib/puppet/reports/store.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, when Delete is enabled in auth.conf, allows remote authenticated users to delete arbitrary files on the puppet master server via a .. (dot dot) in a node name. | {'CVE-2012-3865'} | 2022-03-03T05:13:46.452209Z | 2017-10-24T18:33:37Z | LOW | null | {'CWE-22'} | {'https://github.com/puppetlabs/puppet/commit/554eefc55f57ed2b76e5ee04d8f194d36f6ee67f', 'https://github.com/puppetlabs/puppet', 'https://bugzilla.redhat.com/show_bug.cgi?id=839131', 'http://www.debian.org/security/2012/dsa-2511', 'http://www.ubuntu.com/usn/USN-1506-1', 'https://github.com/puppetlabs/puppet/commit/d80478208d79a3e6d6cb1fbc525e24817fe8c4c6', 'http://lists.opensuse.org/opensuse-security-announce/2012-08/msg00006.html', 'http://puppetlabs.com/security/cve/cve-2012-3865/', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3865', 'https://github.com/advisories/GHSA-g89m-3wjw-h857', 'http://secunia.com/advisories/50014', 'http://lists.opensuse.org/opensuse-updates/2012-07/msg00036.html'} | null | {'https://github.com/puppetlabs/puppet/commit/d80478208d79a3e6d6cb1fbc525e24817fe8c4c6', 'https://github.com/puppetlabs/puppet/commit/554eefc55f57ed2b76e5ee04d8f194d36f6ee67f'} | {'https://github.com/puppetlabs/puppet/commit/554eefc55f57ed2b76e5ee04d8f194d36f6ee67f', 'https://github.com/puppetlabs/puppet/commit/d80478208d79a3e6d6cb1fbc525e24817fe8c4c6'} |
RubyGems | GHSA-f599-5m7p-hcpf | Moderate severity vulnerability that affects grape | The grape rubygem suffers from a cross-site scripting (XSS) vulnerability via "format" parameter. | {'CVE-2018-3769'} | 2022-03-03T05:13:20.669121Z | 2018-08-13T20:45:32Z | MODERATE | null | {'CWE-79'} | {'https://github.com/ruby-grape/grape/pull/1763', 'https://github.com/advisories/GHSA-f599-5m7p-hcpf', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3769', 'https://github.com/ruby-grape/grape/issues/1762', 'https://github.com/ruby-grape/grape/commit/6876b71efc7b03f7ce1be3f075eaa4e7e6de19af'} | null | {'https://github.com/ruby-grape/grape/commit/6876b71efc7b03f7ce1be3f075eaa4e7e6de19af'} | {'https://github.com/ruby-grape/grape/commit/6876b71efc7b03f7ce1be3f075eaa4e7e6de19af'} |
RubyGems | GHSA-xq52-rv6w-397c | Directive injection when using dynamic overrides with user input | ### Impact
If user-supplied input was passed into `append/override_content_security_policy_directives`, a semicolon could be injected leading to directive injection.
This could be used to e.g. override a `script-src` directive. Duplicate directives are ignored and the first one wins. The directives in `secure_headers` are sorted alphabetically so they pretty much all come before `script-src`. A previously undefined directive would receive a value even if `SecureHeaders::OPT_OUT` was supplied.
The fixed versions will silently convert the semicolons to spaces and emit a deprecation warning when this happens. This will result in innocuous browser console messages if being exploited/accidentally used. In future releases, we will raise application errors resulting in 500s.
> Duplicate script-src directives detected. All but the first instance will be ignored.
See https://www.w3.org/TR/CSP3/#parse-serialized-policy
> Note: In this case, the user agent SHOULD notify developers that a duplicate directive was ignored. A console warning might be appropriate, for example.
### Patches
Depending on what major version you are using, the fixed versions are 6.2.0, 5.1.0, 3.8.0.
### Workarounds
If you are passing user input into the above methods, you could filter out the input:
```ruby
override_content_security_policy_directives(:frame_src, [user_input.gsub(";", " ")])
```
### References
Reported in https://github.com/twitter/secure_headers/issues/418
https://www.w3.org/TR/CSP3/#parse-serialized-policy
### 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/issues/new)
* DM @ndm on twitter | {'CVE-2020-5217'} | 2022-03-03T05:13:11.160362Z | 2020-01-23T02:28:11Z | MODERATE | null | {'CWE-95'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-5217', 'https://github.com/twitter/secure_headers/issues/418', 'https://github.com/twitter/secure_headers/pull/421', 'https://github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3', 'https://github.com/twitter/secure_headers/security/advisories/GHSA-xq52-rv6w-397c'} | null | {'https://github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3'} | {'https://github.com/twitter/secure_headers/commit/936a160e3e9659737a9f9eafce13eea36b5c9fa3'} |
RubyGems | GHSA-v3rr-cph9-2g2q | Moderate severity vulnerability that affects rack-ssl | Cross-site scripting (XSS) vulnerability in lib/rack/ssl.rb in the rack-ssl gem before 1.4.0 for Ruby allows remote attackers to inject arbitrary web script or HTML via a URI, which might not be properly handled by third-party adapters such as JRuby-Rack. | {'CVE-2014-2538'} | 2022-03-03T05:13:09.421535Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-79'} | {'https://github.com/josh/rack-ssl', 'http://www.securityfocus.com/bid/66314', 'https://nvd.nist.gov/vuln/detail/CVE-2014-2538', 'http://lists.opensuse.org/opensuse-updates/2014-04/msg00032.html', 'https://github.com/advisories/GHSA-v3rr-cph9-2g2q', 'https://github.com/josh/rack-ssl/commit/9d7d7300b907e496db68d89d07fbc2e0df0b487b', 'http://www.openwall.com/lists/oss-security/2014/03/19/20', 'http://secunia.com/advisories/57466'} | null | {'https://github.com/josh/rack-ssl/commit/9d7d7300b907e496db68d89d07fbc2e0df0b487b'} | {'https://github.com/josh/rack-ssl/commit/9d7d7300b907e496db68d89d07fbc2e0df0b487b'} |
RubyGems | GHSA-q58g-455p-8vw9 | In RubyGem excon, interrupted Persistent Connections May Leak Response Data | ### Impact
There was a race condition around persistent connections, where a connection which is interrupted (such as by a timeout) would leave data on the socket. Subsequent requests would then read this data, returning content from the previous response. The race condition window appears to be short, and it would be difficult to purposefully exploit this.
### Patches
The problem has been patched in 0.71.0, users should upgrade to this or a newer version (if one exists).
### Workarounds
Users can workaround the problem by disabling persistent connections, though this may cause performance implications.
### References
See the [patch](https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29) for further details.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [excon/issues](https://github.com/excon/excon/issues)
* Email us at [geemus+github@gmail.com](mailto:geemus+github@gmail.com) | {'CVE-2019-16779'} | 2022-03-03T05:12:58.973224Z | 2019-12-16T19:30:17Z | MODERATE | null | {'CWE-362', 'CWE-664'} | {'https://github.com/excon/excon/security/advisories/GHSA-q58g-455p-8vw9', 'https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16779', 'https://lists.debian.org/debian-lts-announce/2020/01/msg00015.html', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00021.html', 'https://github.com/excon/excon', 'http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00062.html'} | null | {'https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29'} | {'https://github.com/excon/excon/commit/ccb57d7a422f020dc74f1de4e8fb505ab46d8a29'} |
RubyGems | GHSA-hj56-84jw-67h6 | Potential Denial-of-Service in bindata | In the bindata RubyGem before version 2.4.10 there is a potential denial-of-service vulnerability. In affected versions it is very slow for certain classes in BinData to be created. For example BinData::Bit100000, BinData::Bit100001, BinData::Bit100002, BinData::Bit<N>. In combination with <user_input>.constantize there is a potential for a CPU-based DoS. In version 2.4.10 bindata improved the creation time of Bits and Integers.
| {'CVE-2021-32823'} | 2022-03-03T05:13:23.518004Z | 2021-06-23T23:42:04Z | LOW | null | {'CWE-400'} | {'https://github.com/dmendel/bindata/blob/v2.4.10/ChangeLog.rdoc#version-2410-2021-05-18-', 'https://github.com/dmendel/bindata/commit/d99f050b88337559be2cb35906c1f8da49531323', 'https://about.gitlab.com/releases/2021/06/01/security-release-gitlab-13-12-2-released/#update-bindata-dependency', 'https://github.com/dmendel/bindata/blob/master/ChangeLog.rdoc#version-2410-2021-05-18-', 'https://rubygems.org/gems/bindata', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32823', 'https://github.com/rubysec/ruby-advisory-db/issues/476'} | null | {'https://github.com/dmendel/bindata/commit/d99f050b88337559be2cb35906c1f8da49531323'} | {'https://github.com/dmendel/bindata/commit/d99f050b88337559be2cb35906c1f8da49531323'} |
RubyGems | GHSA-864j-6qpp-cmrr | SQL Injection in Geocoder | sql.rb in Geocoder before 1.6.1 allows Boolean-based SQL injection when within_bounding_box is used in conjunction with untrusted sw_lat, sw_lng, ne_lat, or ne_lng data. | {'CVE-2020-7981'} | 2022-03-03T05:14:07.999518Z | 2020-06-10T20:03:02Z | CRITICAL | null | {'CWE-89'} | {'https://github.com/alexreisner/geocoder/compare/v1.6.0...v1.6.1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7981', 'https://github.com/alexreisner/geocoder/commit/dcdc3d8675411edce3965941a2ca7c441ca48613', 'https://github.com/alexreisner/geocoder', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/geocoder/CVE-2020-7981.yml', 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7981'} | null | {'https://github.com/alexreisner/geocoder/commit/dcdc3d8675411edce3965941a2ca7c441ca48613'} | {'https://github.com/alexreisner/geocoder/commit/dcdc3d8675411edce3965941a2ca7c441ca48613'} |
RubyGems | GHSA-78vq-9j56-wrfr | Cross-site Scripting in gon | An issue was discovered in the gon gem before gon-6.4.0 for Ruby. MultiJson does not honor the escape_mode parameter to escape fields as an XSS protection mechanism. To mitigate, json_dumper.rb in gon now does escaping for XSS by default without relying on MultiJson. | {'CVE-2020-25739'} | 2022-03-03T05:13:59.881533Z | 2021-04-30T17:29:15Z | MODERATE | null | {'CWE-79'} | {'https://lists.debian.org/debian-lts-announce/2020/09/msg00018.html', 'https://usn.ubuntu.com/4560-1/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25739', 'https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7'} | null | {'https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7'} | {'https://github.com/gazay/gon/commit/fe3c7b2191a992386dc9edd37de5447a4e809bc7'} |
RubyGems | GHSA-j5hj-fhc9-g24m | Moderate severity vulnerability that affects rack-mini-profiler | The rack-mini-profiler gem before 0.10.1 for Ruby allows remote attackers to obtain sensitive information about allocated strings and objects by leveraging incorrect ordering of security checks. | {'CVE-2016-4442'} | 2022-03-03T05:10:09.396301Z | 2017-10-24T18:33:35Z | MODERATE | null | {'CWE-200'} | {'https://github.com/advisories/GHSA-j5hj-fhc9-g24m', 'https://github.com/MiniProfiler/rack-mini-profiler/commit/4273771d65f1a7411e3ef5843329308d0e2d257c', 'https://github.com/MiniProfiler/rack-mini-profiler/', 'https://github.com/MiniProfiler/rack-mini-profiler/blob/v0.10.1/CHANGELOG.md', 'http://www.openwall.com/lists/oss-security/2016/06/10/2', 'https://nvd.nist.gov/vuln/detail/CVE-2016-4442'} | null | {'https://github.com/MiniProfiler/rack-mini-profiler/commit/4273771d65f1a7411e3ef5843329308d0e2d257c'} | {'https://github.com/MiniProfiler/rack-mini-profiler/commit/4273771d65f1a7411e3ef5843329308d0e2d257c'} |
RubyGems | GHSA-8jxj-9r5f-w3m2 | Low severity vulnerability that affects puppet | lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml, which allows local users to obtain sensitive configuration information by leveraging access to the puppet master server to read this file. | {'CVE-2012-3866'} | 2022-03-03T05:14:03.097740Z | 2017-10-24T18:33:37Z | LOW | null | null | {'http://www.debian.org/security/2012/dsa-2511', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3866', 'http://www.ubuntu.com/usn/USN-1506-1', 'https://github.com/advisories/GHSA-8jxj-9r5f-w3m2', 'https://bugzilla.redhat.com/show_bug.cgi?id=839135', 'https://github.com/puppetlabs/puppet/commit/fd44bf5e6d0d360f6a493d663b653c121fa83c3f', 'https://github.com/puppetlabs/puppet', 'http://secunia.com/advisories/50014', 'http://lists.opensuse.org/opensuse-updates/2012-07/msg00036.html', 'http://puppetlabs.com/security/cve/cve-2012-3866/'} | null | {'https://github.com/puppetlabs/puppet/commit/fd44bf5e6d0d360f6a493d663b653c121fa83c3f'} | {'https://github.com/puppetlabs/puppet/commit/fd44bf5e6d0d360f6a493d663b653c121fa83c3f'} |
RubyGems | GHSA-h29f-7f56-j8wh | Moderate severity vulnerability that affects sinatra | An issue was discovered in rack-protection/lib/rack/protection/path_traversal.rb in Sinatra 2.x before 2.0.1 on Windows. Path traversal is possible via backslash characters. | {'CVE-2018-7212'} | 2022-03-03T05:12:59.959481Z | 2018-02-20T19:23:20Z | MODERATE | null | {'CWE-22'} | {'https://github.com/sinatra/sinatra/commit/6ad721abcfe36334108dcdd05d046c361e1b7a9c', 'https://github.com/sinatra/sinatra', 'https://github.com/sinatra/sinatra/pull/1379', 'https://nvd.nist.gov/vuln/detail/CVE-2018-7212', 'https://github.com/advisories/GHSA-h29f-7f56-j8wh'} | null | {'https://github.com/sinatra/sinatra/commit/6ad721abcfe36334108dcdd05d046c361e1b7a9c'} | {'https://github.com/sinatra/sinatra/commit/6ad721abcfe36334108dcdd05d046c361e1b7a9c'} |
RubyGems | GHSA-2gw2-8q9w-cw8p | Ruby-ffi has a DLL loading issue | ruby-ffi version 1.9.23 and earlier has a DLL loading issue which can be hijacked on Windows OS, when a Symbol is used as DLL name instead of a String This vulnerability appears to have been fixed in v1.9.24 and later. | {'CVE-2018-1000201'} | 2022-04-26T18:33:00.711228Z | 2018-08-31T14:55:43Z | HIGH | null | {'CWE-426'} | {'https://github.com/advisories/GHSA-2gw2-8q9w-cw8p', 'https://github.com/ffi/ffi/commit/09e0c6076466b4383da7fa4e13f714311109945a', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000201', 'https://github.com/ffi/ffi/commit/e0fe486df0e117ed67b0282b6ada04b7214ca05c'} | null | {'https://github.com/ffi/ffi/commit/09e0c6076466b4383da7fa4e13f714311109945a', 'https://github.com/ffi/ffi/commit/e0fe486df0e117ed67b0282b6ada04b7214ca05c'} | {'https://github.com/ffi/ffi/commit/09e0c6076466b4383da7fa4e13f714311109945a', 'https://github.com/ffi/ffi/commit/e0fe486df0e117ed67b0282b6ada04b7214ca05c'} |
RubyGems | GHSA-j6w9-fv6q-3q52 | Percent-encoded cookies can be used to overwrite existing prefixed cookie names | A reliance on cookies without validation/integrity check security vulnerability exists in rack < 2.2.3, rack < 2.1.4 that makes it is possible for an attacker to forge a secure or host-only cookie prefix. | {'CVE-2020-8184'} | 2022-03-03T05:14:04.623248Z | 2020-06-24T17:15:00Z | HIGH | null | {'CWE-784'} | {'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2020-8184.yml', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00006.html', 'https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c', 'https://usn.ubuntu.com/4561-1/', 'https://groups.google.com/g/rubyonrails-security/c/OWtmozPH9Ak', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8184', 'https://hackerone.com/reports/895727'} | null | {'https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c'} | {'https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c'} |
RubyGems | GHSA-gwrj-88fp-5m36 | Code injection in Narou | Narou (aka Narou.rb) before 3.8.0 allows Ruby Code Injection via the title name or author name of a novel. | {'CVE-2021-35514'} | 2022-03-03T05:13:07.602213Z | 2021-07-02T18:36:01Z | HIGH | null | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-35514', 'https://github.com/whiteleaf7/narou/commit/d07720e855293182563b749431dfbf6c2d1cdb42', 'https://github.com/whiteleaf7/narou/blob/develop/ChangeLog.md#380-20210627', 'https://vuln.ryotak.me/advisories/51'} | null | {'https://github.com/whiteleaf7/narou/commit/d07720e855293182563b749431dfbf6c2d1cdb42'} | {'https://github.com/whiteleaf7/narou/commit/d07720e855293182563b749431dfbf6c2d1cdb42'} |
RubyGems | GHSA-c6qr-h5vq-59jc | Untrusted users can run pending migrations in production in Rails | There is a vulnerability in versions of Rails prior to 6.0.3.2 that allowed
an untrusted user to run any pending migrations on a Rails app running in
production.
This vulnerability has been assigned the CVE identifier CVE-2020-8185.
Versions Affected: 6.0.0 < rails < 6.0.3.2
Not affected: Applications with `config.action_dispatch.show_exceptions = false` (this is not a default setting in production)
Fixed Versions: rails >= 6.0.3.2
Impact
------
Using this issue, an attacker would be able to execute any migrations that
are pending for a Rails app running in production mode. It is important to
note that an attacker is limited to running migrations the application
developer has already defined in their application and ones that have not
already ran.
Workarounds
-----------
Until such time as the patch can be applied, application developers should
disable the ActionDispatch middleware in their production environment via
a line such as this one in their config/environment/production.rb:
`config.middleware.delete ActionDispatch::ActionableExceptions` | {'CVE-2020-8185'} | 2022-03-03T05:14:11.823792Z | 2020-06-24T17:40:33Z | MODERATE | null | {'CWE-400'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XJ7NUWXAEVRQCROIIBV4C6WXO6IR3KSB/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8185', 'https://github.com/rails/rails/commit/2121b9d20b60ed503aa041ef7b926d331ed79fc2', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2020-8185.yml', 'https://groups.google.com/g/rubyonrails-security/c/pAe9EV8gbM0', 'https://hackerone.com/reports/899069'} | null | {'https://github.com/rails/rails/commit/2121b9d20b60ed503aa041ef7b926d331ed79fc2'} | {'https://github.com/rails/rails/commit/2121b9d20b60ed503aa041ef7b926d331ed79fc2'} |
RubyGems | GHSA-p4x4-rw2p-8j8m | Cross-site Scripting in Sanitize | When HTML is sanitized using Sanitize's "relaxed" config or a custom config that allows certain elements, some content in a `<math>` or `<svg>` element may not be sanitized correctly even if `math` and `svg` are not in the allowlist.
You are likely to be vulnerable to this issue if you use Sanitize's relaxed config or a custom config that allows one or more of the following HTML elements:
- `iframe`
- `math`
- `noembed`
- `noframes`
- `noscript`
- `plaintext`
- `script`
- `style`
- `svg`
- `xmp`
### Impact
Using carefully crafted input, an attacker may be able to sneak arbitrary HTML through Sanitize, potentially resulting in XSS (cross-site scripting) or other undesired behavior when that HTML is rendered in a browser.
### Releases
This problem has been fixed in Sanitize 5.2.1.
### Workarounds
If upgrading is not possible, a workaround is to override the default value of Sanitize's `:remove_contents` config option with the following value, which ensures that the contents of `math` and `svg` elements (among others) are removed entirely when those elements are not in the allowlist:
```ruby
%w[iframe math noembed noframes noscript plaintext script style svg xmp]
```
For example, if you currently use Sanitize's relaxed config, you can create a custom config object that overrides the default value of `:remove_contents` like this:
```ruby
custom_config = Sanitize::Config.merge(
Sanitize::Config::RELAXED,
:remove_contents => %w[iframe math noembed noframes noscript plaintext script style svg xmp]
)
```
You would then pass this custom config to Sanitize when sanitizing HTML.
### For more information
If you have any questions or comments about this advisory:
- Open an issue in the [Sanitize repo](https://github.com/rgrove/sanitize).
- See Sanitize's [security policy](https://github.com/rgrove/sanitize/security/policy).
### Credits
Many thanks to Michal Bentkowski of Securitum for reporting this bug and helping to verify the fix.
### References
- [GHSA-p4x4-rw2p-8j8m](https://github.com/rgrove/sanitize/security/advisories/GHSA-p4x4-rw2p-8j8m)
- [CVE-2020-4054](https://nvd.nist.gov/vuln/detail/CVE-2020-4054)
- https://github.com/rgrove/sanitize/releases/tag/v5.2.1 | {'CVE-2020-4054'} | 2022-03-03T05:13:26.390326Z | 2020-06-16T22:08:06Z | HIGH | null | {'CWE-79'} | {'https://usn.ubuntu.com/4543-1/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-4054', 'https://github.com/rgrove/sanitize/security/advisories/GHSA-p4x4-rw2p-8j8m', 'https://www.debian.org/security/2020/dsa-4730', 'https://github.com/rgrove/sanitize/commit/a11498de9e283cd457b35ee252983662f7452aa9', 'https://github.com/rgrove/sanitize/releases/tag/v5.2.1'} | null | {'https://github.com/rgrove/sanitize/commit/a11498de9e283cd457b35ee252983662f7452aa9'} | {'https://github.com/rgrove/sanitize/commit/a11498de9e283cd457b35ee252983662f7452aa9'} |
RubyGems | GHSA-rprj-g6xc-p5gq | Moderate severity vulnerability that affects wicked | Directory traversal vulnerability in controller/concerns/render_redirect.rb in the Wicked gem before 1.0.1 for Ruby allows remote attackers to read arbitrary files via a %2E%2E%2F (encoded dot dot slash) in the step. | {'CVE-2013-4413'} | 2022-03-03T05:14:13.648715Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-22'} | {'http://seclists.org/oss-sec/2013/q4/43', 'https://github.com/advisories/GHSA-rprj-g6xc-p5gq', 'http://www.securityfocus.com/bid/62891', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4413', 'http://secunia.com/advisories/55151', 'https://github.com/schneems/wicked', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/87783', 'https://github.com/schneems/wicked/commit/fe31bb2533fffc9d098c69ebeb7afc3b80509f53'} | null | {'https://github.com/schneems/wicked/commit/fe31bb2533fffc9d098c69ebeb7afc3b80509f53'} | {'https://github.com/schneems/wicked/commit/fe31bb2533fffc9d098c69ebeb7afc3b80509f53'} |
RubyGems | GHSA-qphc-hf5q-v8fc | Open Redirect in actionpack | Specially crafted "X-Forwarded-Host" headers in combination with certain
"allowed host" formats can cause the Host Authorization middleware in Action
Pack to redirect users to a malicious website.
Impacted applications will have allowed hosts with a leading dot. For example,
configuration files that look like this:
```
config.hosts << '.EXAMPLE.com'
```
When an allowed host contains a leading dot, a specially crafted Host header
can be used to redirect to a malicious website.
This vulnerability is similar to CVE-2021-22881 and CVE-2021-22942.
Releases
--------
The fixed releases are available at the normal locations.
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.
* 6-0-host-authorzation-open-redirect.patch - Patch for 6.0 series
* 6-1-host-authorzation-open-redirect.patch - Patch for 6.1 series
* 7-0-host-authorzation-open-redirect.patch - Patch for 7.0 series
Please note that only the 6.1.Z, 6.0.Z, and 5.2.Z 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. | {'CVE-2021-44528'} | 2022-04-27T22:32:00.332117Z | 2021-12-14T21:19:08Z | MODERATE | null | {'CWE-601'} | {'https://github.com/rails/rails/commit/aecba3c301b80e9d5a63c30ea1b287bceaf2c107', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionpack/CVE-2021-44528.yml', 'https://nvd.nist.gov/vuln/detail/CVE-2021-44528', 'https://github.com/rails/rails', 'https://github.com/rails/rails/commit/0fccfb9a3097a9c4260c791f1a40b128517e7815', 'https://groups.google.com/g/ruby-security-ann/c/vG9gz3nk1pM/m/7-NU4MNrDAAJ', 'https://github.com/rails/rails/blob/v6.1.4.2/actionpack/CHANGELOG.md#rails-6142-december-14-2021', 'https://groups.google.com/g/ruby-security-ann/c/vG9gz3nk1pM/m/7-NU4MNrDAAJ?utm_medium=email&utm_source=footer'} | null | {'https://github.com/rails/rails/commit/aecba3c301b80e9d5a63c30ea1b287bceaf2c107', 'https://github.com/rails/rails/commit/0fccfb9a3097a9c4260c791f1a40b128517e7815'} | {'https://github.com/rails/rails/commit/aecba3c301b80e9d5a63c30ea1b287bceaf2c107', 'https://github.com/rails/rails/commit/0fccfb9a3097a9c4260c791f1a40b128517e7815'} |
RubyGems | GHSA-r5hc-9xx5-97rw | Moderate severity vulnerability that affects i18n | Cross-site scripting (XSS) vulnerability in exceptions.rb in the i18n gem before 0.6.6 for Ruby allows remote attackers to inject arbitrary web script or HTML via a crafted I18n::MissingTranslationData.new call. | {'CVE-2013-4492'} | 2022-03-03T05:13:54.902315Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-79'} | {'https://github.com/advisories/GHSA-r5hc-9xx5-97rw', 'http://lists.opensuse.org/opensuse-updates/2013-12/msg00093.html', 'https://github.com/svenfuchs/i18n/commit/92b57b1e4f84adcdcc3a375278f299274be62445', 'http://www.debian.org/security/2013/dsa-2830', 'https://github.com/svenfuchs/i18n', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4492', 'http://www.securityfocus.com/bid/64076', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/pLrh6DUw998/bLFEyIO4k_EJ', 'http://weblog.rubyonrails.org/2013/12/3/Rails_3_2_16_and_4_0_2_have_been_released/'} | null | {'https://github.com/svenfuchs/i18n/commit/92b57b1e4f84adcdcc3a375278f299274be62445'} | {'https://github.com/svenfuchs/i18n/commit/92b57b1e4f84adcdcc3a375278f299274be62445'} |
RubyGems | GHSA-j858-xp5v-f8xx | Remote code execution in Dragonfly | An argument injection vulnerability in the Dragonfly gem before 1.4.0 for Ruby allows remote attackers to read and write to arbitrary files via a crafted URL when the verify_url option is disabled. This may lead to code execution. The problem occurs because the generate and process features mishandle use of the ImageMagick convert utility. | {'CVE-2021-33564'} | 2022-03-03T05:13:58.950700Z | 2021-06-02T21:42:49Z | CRITICAL | null | {'CWE-94', 'CWE-88'} | {'https://github.com/markevans/dragonfly/commit/25399297bb457f7fcf8e3f91e85945b255b111b5', 'https://github.com/markevans/dragonfly/compare/v1.3.0...v1.4.0', 'https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/master/cves/2021/CVE-2021-33564.yaml', 'https://github.com/markevans/dragonfly/issues/513', 'https://nvd.nist.gov/vuln/detail/CVE-2021-33564', 'https://zxsecurity.co.nz/research/argunment-injection-ruby-dragonfly/', 'https://github.com/mlr0p/CVE-2021-33564'} | null | {'https://github.com/markevans/dragonfly/commit/25399297bb457f7fcf8e3f91e85945b255b111b5'} | {'https://github.com/markevans/dragonfly/commit/25399297bb457f7fcf8e3f91e85945b255b111b5'} |
RubyGems | GHSA-844m-cpr9-jcmh | Secure/signed cookies share secrets between sites in a multi-site application | ### Impact
This vulnerability impacts any Rails applications using `rails_multisite` alongside Rails' signed/encrypted cookies. Depending on how the application makes use of these cookies, it may be possible for an attacker to re-use cookies on different 'sites' within a multi-site Rails application.
### Patches
The issue has been patched in v4 of the `rails_multisite` gem. Note that this upgrade will invalidate all previous signed/encrypted cookies. The impact of this invalidation will vary based on the application architecture. | {'CVE-2021-41263'} | 2022-03-03T05:12:57.242829Z | 2021-11-15T17:54:01Z | MODERATE | null | {'CWE-200', 'CWE-565'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-41263', 'https://github.com/discourse/rails_multisite/security/advisories/GHSA-844m-cpr9-jcmh', 'https://github.com/discourse/rails_multisite/commit/c6785cdb5c9277dd2c5ac8d55180dd1ece440ed0', 'https://github.com/discourse/rails_multisite'} | null | {'https://github.com/discourse/rails_multisite/commit/c6785cdb5c9277dd2c5ac8d55180dd1ece440ed0'} | {'https://github.com/discourse/rails_multisite/commit/c6785cdb5c9277dd2c5ac8d55180dd1ece440ed0'} |
RubyGems | GHSA-5pm8-492c-92p5 | Prototype Pollution in chartkick | Affected versions of `@polymer/polymer` are vulnerable to prototype pollution. The package fails to prevent modification of object prototypes through chart options containing a payload such as `{"__proto__": {"polluted": true}}`. It is possible to achieve the same results if a chart loads data from a malicious server.
## Recommendation
Upgrade to version 3.2.0 or later. | {'CVE-2019-18841'} | 2022-03-03T05:12:51.639263Z | 2019-12-02T18:04:11Z | HIGH | null | null | {'https://github.com/ankane/chartkick/commits/master', 'https://github.com/ankane/chartkick/commit/b810936bbf687bc74c5b6dba72d2397a399885fa', 'https://nvd.nist.gov/vuln/detail/CVE-2019-18841', 'https://rubygems.org/gems/chartkick/', 'https://github.com/ankane/chartkick.js/issues/117', 'https://chartkick.com', 'https://www.npmjs.com/advisories/1312', 'https://github.com/ankane/chartkick/blob/master/CHANGELOG.md'} | null | {'https://github.com/ankane/chartkick/commit/b810936bbf687bc74c5b6dba72d2397a399885fa'} | {'https://github.com/ankane/chartkick/commit/b810936bbf687bc74c5b6dba72d2397a399885fa'} |
RubyGems | GHSA-r7j3-vvh2-xrpj | OS Command Injection in MiniMagick | In lib/mini_magick/image.rb in MiniMagick before 4.9.4, a fetched remote image filename could cause remote command execution because Image.open input is directly passed to Kernel#open, which accepts a '|' character followed by a command. | {'CVE-2019-13574'} | 2022-03-03T05:13:10.705994Z | 2019-07-18T13:19:22Z | HIGH | null | {'CWE-78'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-13574', 'https://seclists.org/bugtraq/2019/Jul/20', 'https://lists.debian.org/debian-lts-announce/2019/10/msg00007.html', 'https://github.com/minimagick/minimagick/commit/4cd5081e58810d3394d27a67219e8e4e0445d851', 'https://github.com/minimagick/minimagick/releases/tag/v4.9.4', 'https://benjamin-bouchet.com/blog/vulnerabilite-dans-la-gem-mini_magick-version-4-9-4/', 'https://www.debian.org/security/2019/dsa-4481', 'https://github.com/minimagick/minimagick/compare/d484786...293f9bb'} | null | {'https://github.com/minimagick/minimagick/commit/4cd5081e58810d3394d27a67219e8e4e0445d851'} | {'https://github.com/minimagick/minimagick/commit/4cd5081e58810d3394d27a67219e8e4e0445d851'} |
RubyGems | GHSA-x7p2-x2j6-mwhr | Moderate severity vulnerability that affects gemirro | Stored cross-site scripting (XSS) vulnerability in Gemirro before 0.16.0 allows attackers to inject arbitrary web script via a crafted javascript: URL in the "homepage" value of a ".gemspec" file. | {'CVE-2017-16833'} | 2022-03-03T05:13:32.757913Z | 2017-11-29T23:19:51Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2017-16833', 'https://github.com/PierreRambaud/gemirro/commit/9659f9b7ce15a723da8e361bd41b9203b19c97de', 'https://github.com/PierreRambaud/gemirro', 'https://github.com/advisories/GHSA-x7p2-x2j6-mwhr'} | null | {'https://github.com/PierreRambaud/gemirro/commit/9659f9b7ce15a723da8e361bd41b9203b19c97de'} | {'https://github.com/PierreRambaud/gemirro/commit/9659f9b7ce15a723da8e361bd41b9203b19c97de'} |
RubyGems | GHSA-73qw-ww62-m54x | Critical severity vulnerability that affects colorscore | The initialize method in the Histogram class in lib/colorscore/histogram.rb in the colorscore gem before 0.0.5 for Ruby allows context-dependent attackers to execute arbitrary code via shell metacharacters in the (1) image_path, (2) colors, or (3) depth variable. | {'CVE-2015-7541'} | 2022-03-03T05:12:47.605634Z | 2017-10-24T18:33:36Z | CRITICAL | null | {'CWE-77'} | {'https://github.com/quadule/colorscore/commit/570b5e854cecddd44d2047c44126aed951b61718', 'http://rubysec.com/advisories/CVE-2015-7541/', 'https://github.com/advisories/GHSA-73qw-ww62-m54x', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7541', 'http://www.openwall.com/lists/oss-security/2016/01/05/2'} | null | {'https://github.com/quadule/colorscore/commit/570b5e854cecddd44d2047c44126aed951b61718'} | {'https://github.com/quadule/colorscore/commit/570b5e854cecddd44d2047c44126aed951b61718'} |
RubyGems | GHSA-q3wr-qw3g-3p4h | Injection/XSS in Redcarpet | Redcarpet is a Ruby library for Markdown processing. In Redcarpet before version 3.5.1, there is an injection vulnerability which can enable a cross-site scripting attack. In affected versions no HTML escaping was being performed when processing quotes. This applies even when the `:escape_html` option was being used. This is fixed in version 3.5.1 by the referenced commit. | {'CVE-2020-26298'} | 2022-03-03T05:13:23.703389Z | 2021-01-11T19:06:10Z | MODERATE | null | {'CWE-79'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26298', 'https://rubygems.org/gems/redcarpet', 'https://lists.debian.org/debian-lts-announce/2021/01/msg00014.html', 'https://github.com/advisories/GHSA-q3wr-qw3g-3p4h', 'https://github.com/vmg/redcarpet/blob/master/CHANGELOG.md#version-351-security', 'https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793', 'https://www.debian.org/security/2021/dsa-4831'} | null | {'https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793'} | {'https://github.com/vmg/redcarpet/commit/a699c82292b17c8e6a62e1914d5eccc252272793'} |
RubyGems | GHSA-26xx-m4q2-xhq8 | Authentication Bypass by CSRF Weakness | ### Impact
CSRF vulnerability that allows user account takeover.
All applications using any version of the frontend component of `spree_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.
Thanks @waiting-for-dev for reporting and providing a patch 👏
### Patches
Spree 4.3 users should update to spree_auth_devise 4.4.1
Spree 4.2 users should update to spree_auth_devise 4.2.1
Spree 4.1 users should update to spree_auth_devise 4.1.1
Older Spree version users should update to spree_auth_devise 4.0.1
### Workarounds
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
```
### References
https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2
| {'CVE-2021-41275'} | 2022-03-03T05:12:54.592023Z | 2021-11-18T20:14:19Z | CRITICAL | null | {'CWE-352'} | {'https://github.com/solidusio/solidus_auth_devise/security/advisories/GHSA-xm34-v85h-9pg2', 'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63', 'https://github.com/spree/spree_auth_devise', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41275', 'https://github.com/spree/spree_auth_devise/security/advisories/GHSA-26xx-m4q2-xhq8'} | null | {'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63'} | {'https://github.com/spree/spree_auth_devise/commit/adf6ed4cd94d66091776b5febd4ff3767362de63'} |
RubyGems | GHSA-j24p-r6wx-r79w | High severity vulnerability that affects thin | lib/thin/connection.rb in Thin web server before 1.2.4 relies on the X-Forwarded-For header to determine the IP address of the client, which allows remote attackers to spoof the IP address and hide activities via a modified X-Forwarded-For header. | {'CVE-2009-3287'} | 2022-03-03T05:13:18.776632Z | 2017-10-24T18:33:38Z | HIGH | null | {'CWE-20'} | {'https://nvd.nist.gov/vuln/detail/CVE-2009-3287', 'http://github.com/macournoyer/thin/commit/7bd027914c5ffd36bb408ef47dc749de3b6e063a', 'http://www.openwall.com/lists/oss-security/2009/09/12/1', 'http://github.com/macournoyer/thin', 'http://github.com/macournoyer/thin/blob/master/CHANGELOG', 'https://github.com/advisories/GHSA-j24p-r6wx-r79w'} | null | {'http://github.com/macournoyer/thin/commit/7bd027914c5ffd36bb408ef47dc749de3b6e063a'} | {'http://github.com/macournoyer/thin/commit/7bd027914c5ffd36bb408ef47dc749de3b6e063a'} |
RubyGems | GHSA-x7jg-6pwg-fx5h | HTTP Smuggling via Transfer-Encoding Header in Puma | ### Impact
By using an invalid transfer-encoding header, an attacker could [smuggle an HTTP response.](https://portswigger.net/web-security/request-smuggling)
Originally reported by @ZeddYu, who has our thanks for the detailed report.
### Patches
The problem has been fixed in Puma 3.12.5 and Puma 4.3.4.
### 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-2020-11076'} | 2022-03-03T05:13:40.798691Z | 2020-05-22T14:55:05Z | HIGH | null | {'CWE-444'} | {'https://lists.debian.org/debian-lts-announce/2020/10/msg00009.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11076', 'https://github.com/puma/puma/security/advisories/GHSA-x7jg-6pwg-fx5h', 'https://github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00034.html', 'https://github.com/puma/puma/blob/master/History.md#434435-and-31253126--2020-05-22', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SKIY5H67GJIGJL6SMFWFLUQQQR3EMVPR/', 'http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00038.html'} | null | {'https://github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd'} | {'https://github.com/puma/puma/commit/f24d5521295a2152c286abb0a45a1e1e2bd275bd'} |
RubyGems | GHSA-qp49-3pvw-x4m5 | sinatra does not validate expanded path matches | Sinatra before 2.2.0 does not validate that the expanded path matches public_dir when serving static files. | {'CVE-2022-29970'} | 2022-05-03T21:02:03.543510Z | 2022-05-03T00:00:43Z | MODERATE | null | {'CWE-426'} | {'https://github.com/skylightio/skylight-ruby/pull/294', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29970', 'https://github.com/sinatra/sinatra/', 'https://github.com/sinatra/sinatra/pull/1683/commits/462c3ca1db53ed3cfc394cf5948e9c948ad1c10e'} | null | {'https://github.com/sinatra/sinatra/pull/1683/commits/462c3ca1db53ed3cfc394cf5948e9c948ad1c10e'} | {'https://github.com/sinatra/sinatra/pull/1683/commits/462c3ca1db53ed3cfc394cf5948e9c948ad1c10e'} |
RubyGems | GHSA-v6fx-752r-ccp2 | CSRF on PgHero gem | The PgHero gem through 2.6.0 for Ruby allows CSRF. | {'CVE-2020-16253'} | 2022-03-03T05:13:14.287515Z | 2020-08-05T14:53:43Z | HIGH | null | {'CWE-352'} | {'https://github.com/ankane/pghero/issues/330', 'https://rubygems.org/gems/pghero', 'https://github.com/ankane/pghero', 'https://github.com/ankane/pghero/commit/14b67b32fed19a30aaf9826ee72f2a29cda604e9', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/pghero/CVE-2020-16253.yml', 'https://github.com/ankane/pghero/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16253'} | null | {'https://github.com/ankane/pghero/commit/14b67b32fed19a30aaf9826ee72f2a29cda604e9'} | {'https://github.com/ankane/pghero/commit/14b67b32fed19a30aaf9826ee72f2a29cda604e9'} |
RubyGems | GHSA-h6w6-xmqv-7q78 | High severity vulnerability that affects activerecord | Multiple SQL injection vulnerabilities in the quote_table_name method in the ActiveRecord adapters in activerecord/lib/active_record/connection_adapters/ in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allow remote attackers to execute arbitrary SQL commands via a crafted column name. | {'CVE-2011-2930'} | 2022-03-03T05:14:21.566569Z | 2017-10-24T18:33:38Z | HIGH | null | {'CWE-89'} | {'http://groups.google.com/group/rubyonrails-security/msg/b1a85d36b0f9dd30?dmode=source&output=gplain', 'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'https://github.com/advisories/GHSA-h6w6-xmqv-7q78', 'https://bugzilla.redhat.com/show_bug.cgi?id=731438', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'http://www.debian.org/security/2011/dsa-2301', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'https://github.com/rails/rails', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'https://github.com/rails/rails/commit/8a39f411dc3c806422785b1f4d5c7c9d58e4bf85', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2930', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/8a39f411dc3c806422785b1f4d5c7c9d58e4bf85'} | {'https://github.com/rails/rails/commit/8a39f411dc3c806422785b1f4d5c7c9d58e4bf85'} |
RubyGems | GHSA-fxwv-953p-7qpf | Phusion Passenger allows remote attackers to spoof headers passed to applications by using an _ (underscore) character instead of a - (dash) character in an HTTP header | agent/Core/Controller/SendRequest.cpp in Phusion Passenger before 4.0.60 and 5.0.x before 5.0.22, when used in Apache integration mode or in standalone mode without a filtering proxy, allows remote attackers to spoof headers passed to applications by using an _ (underscore) character instead of a - (dash) character in an HTTP header, as demonstrated by an X_User header. | {'CVE-2015-7519'} | 2022-04-26T18:33:06.194040Z | 2018-10-10T17:29:13Z | LOW | null | {'CWE-20'} | {'http://www.openwall.com/lists/oss-security/2015/12/07/1', 'https://blog.phusion.nl/2015/12/07/cve-2015-7519/', 'http://lists.opensuse.org/opensuse-security-announce/2015-12/msg00024.html', 'https://github.com/phusion/passenger/commit/ddb8ecc4ebf260e4967f57f271d4f5761abeac3e', 'https://puppet.com/security/cve/passenger-dec-2015-security-fixes', 'https://github.com/advisories/GHSA-fxwv-953p-7qpf', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7519', 'https://github.com/phusion/passenger', 'https://bugzilla.suse.com/show_bug.cgi?id=956281', 'https://lists.debian.org/debian-lts-announce/2018/06/msg00007.html', 'http://www.openwall.com/lists/oss-security/2015/12/07/2'} | null | {'https://github.com/phusion/passenger/commit/ddb8ecc4ebf260e4967f57f271d4f5761abeac3e'} | {'https://github.com/phusion/passenger/commit/ddb8ecc4ebf260e4967f57f271d4f5761abeac3e'} |
RubyGems | GHSA-jj47-x69x-mxrm | Buffer Overflow in yajl-ruby | yajl-ruby is a streaming JSON parsing and encoding library for Ruby (C bindings to yajl) based on the YAJL library.
The 1.x branch and the 2.x branch of [yajl](https://github.com/lloyd/yajl) contain an integer overflow which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs.
### Details
The [reallocation logic at yajl_buf.c#L64](https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64) may result in the `need` 32bit integer wrapping to 0 when `need` approaches a value of 0x80000000 (i.e. ~2GB of data), which results in a reallocation of buf->alloc into a small heap chunk.
These integers are declared as `size_t` in the 2.x branch of `yajl`, which practically prevents the issue from triggering on 64bit platforms, however this does not preclude this issue triggering on 32bit builds on which `size_t` is a 32bit integer.
Subsequent population of this under-allocated heap chunk is based on the original buffer size, leading to heap memory corruption.
### Impact
We rate this as a moderate severity vulnerability which mostly impacts process availability as we believe exploitation for arbitrary code execution to be unlikely.
### Patches
Patched in yajl-ruby 1.4.2
### Workarounds
Avoid passing large inputs to YAJL
### References
https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [yajl-ruby](https://github.com/brianmario/yajl-ruby/issues)
| {'CVE-2022-24795'} | 2022-04-06T21:16:57.159918Z | 2022-04-05T15:55:51Z | MODERATE | null | {'CWE-190', 'CWE-122'} | {'https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6', 'https://github.com/brianmario/yajl-ruby/security/advisories/GHSA-jj47-x69x-mxrm', 'https://github.com/brianmario/yajl-ruby', 'https://github.com/brianmario/yajl-ruby/blob/7168bd79b888900aa94523301126f968a93eb3a6/ext/yajl/yajl_buf.c#L64', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24795'} | null | {'https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6'} | {'https://github.com/brianmario/yajl-ruby/commit/7168bd79b888900aa94523301126f968a93eb3a6'} |
RubyGems | GHSA-v5jg-558j-q67c | Moderate severity vulnerability that affects actionpack | Cross-site scripting (XSS) vulnerability in the strip_tags helper in actionpack/lib/action_controller/vendor/html-scanner/html/node.rb in Ruby on Rails before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a tag with an invalid name. | {'CVE-2011-2931'} | 2022-03-03T05:13:59.190408Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-79'} | {'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065137.html', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2931', 'http://www.debian.org/security/2011/dsa-2301', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'https://github.com/rails/rails/commit/586a944ddd4d03e66dea1093306147594748037a', 'https://github.com/advisories/GHSA-v5jg-558j-q67c', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'http://secunia.com/advisories/45921', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065109.html', 'https://github.com/rails/rails', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'http://groups.google.com/group/rubyonrails-security/msg/fd41ab62966e0fd1?dmode=source&output=gplain', 'https://bugzilla.redhat.com/show_bug.cgi?id=731436', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/586a944ddd4d03e66dea1093306147594748037a'} | {'https://github.com/rails/rails/commit/586a944ddd4d03e66dea1093306147594748037a'} |
RubyGems | GHSA-jmgf-p46x-982h | Moderate severity vulnerability that affects rails | CRLF injection vulnerability in Ruby on Rails before 2.0.5 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via a crafted URL to the redirect_to function. | {'CVE-2008-5189'} | 2022-03-03T05:13:26.680367Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-352'} | {'http://github.com/rails/rails/commit/7282ed863ca7e6f928bae9162c9a63a98775a19d', 'http://weblog.rubyonrails.org/2008/10/19/rails-2-0-5-redirect_to-and-offset-limit-sanitizing', 'https://github.com/advisories/GHSA-jmgf-p46x-982h', 'http://github.com/rails/rails', 'https://nvd.nist.gov/vuln/detail/CVE-2008-5189', 'http://lists.opensuse.org/opensuse-security-announce/2008-12/msg00002.html', 'http://www.securityfocus.com/bid/32359', 'http://weblog.rubyonrails.org/2008/10/19/response-splitting-risk'} | null | {'http://github.com/rails/rails/commit/7282ed863ca7e6f928bae9162c9a63a98775a19d'} | {'http://github.com/rails/rails/commit/7282ed863ca7e6f928bae9162c9a63a98775a19d'} |
RubyGems | GHSA-9fh3-vh3h-q4g3 | Moderate severity vulnerability that affects activesupport | Cross-site scripting (XSS) vulnerability in activesupport/lib/active_support/core_ext/string/output_safety.rb in Ruby on Rails 2.x before 2.3.13, 3.0.x before 3.0.10, and 3.1.x before 3.1.0.rc5 allows remote attackers to inject arbitrary web script or HTML via a malformed Unicode string, related to a "UTF-8 escaping vulnerability." | {'CVE-2011-2932'} | 2022-03-03T05:12:38.166203Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-79'} | {'https://github.com/rails/rails/commit/bfc432574d0b141fd7fe759edfe9b6771dd306bd', 'https://bugzilla.redhat.com/show_bug.cgi?id=731435', 'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://groups.google.com/group/rubyonrails-security/msg/f1d2749773db9f21?dmode=source&output=gplain', 'https://github.com/advisories/GHSA-9fh3-vh3h-q4g3', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065114.html', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'http://www.openwall.com/lists/oss-security/2011/08/17/1', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065189.html', 'https://github.com/rails/rails', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2932', 'http://secunia.com/advisories/45917'} | null | {'https://github.com/rails/rails/commit/bfc432574d0b141fd7fe759edfe9b6771dd306bd'} | {'https://github.com/rails/rails/commit/bfc432574d0b141fd7fe759edfe9b6771dd306bd'} |
RubyGems | GHSA-jppv-gw3r-w3q8 | OS Command Injection in Rake | There is an OS command injection vulnerability in Ruby Rake before 12.3.3 in Rake::FileList when supplying a filename that begins with the pipe character `|`. | {'CVE-2020-8130'} | 2022-03-03T05:13:45.803499Z | 2020-02-28T16:54:36Z | MODERATE | null | {'CWE-78'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/523CLQ62VRN3VVC52KMPTROCCKY4Z36B/', 'https://hackerone.com/reports/651518', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8130', 'https://usn.ubuntu.com/4295-1/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VXMX4ARNX2JLRJMSH4N3J3UBMUT5CI44/', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00041.html', 'https://github.com/ruby/rake/commit/5b8f8fc41a5d7d7d6a5d767e48464c60884d3aee', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00026.html'} | null | {'https://github.com/ruby/rake/commit/5b8f8fc41a5d7d7d6a5d767e48464c60884d3aee'} | {'https://github.com/ruby/rake/commit/5b8f8fc41a5d7d7d6a5d767e48464c60884d3aee'} |
RubyGems | GHSA-mgx3-27hr-mfgp | High severity vulnerability that affects httparty | The httparty gem 0.9.0 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for YAML type conversion, a similar vulnerability to CVE-2013-0156. | {'CVE-2013-1801'} | 2022-03-03T05:14:10.324559Z | 2017-10-24T18:33:37Z | HIGH | null | null | {'https://bugzilla.redhat.com/show_bug.cgi?id=917229', 'https://support.cloud.engineyard.com/entries/22915701-january-14-2013-security-vulnerabilities-httparty-extlib-crack-nori-update-these-gems-immediately', 'https://github.com/jnunemaker/httparty', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1801', 'https://github.com/advisories/GHSA-mgx3-27hr-mfgp', 'http://www.securityfocus.com/bid/58260', 'https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031'} | null | {'https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031'} | {'https://github.com/jnunemaker/httparty/commit/53a812426dd32108d6cba4272b493aa03bc8c031'} |
RubyGems | GHSA-cff7-6h4q-q5pj | Lacked element count during splitting of JWE string | The json-jwt gem before 1.11.0 for Ruby lacks an element count during the splitting of a JWE string. | {'CVE-2019-18848'} | 2022-05-04T02:05:31.585529Z | 2019-11-14T15:25:51Z | HIGH | null | {'CWE-20', 'CWE-287'} | {'https://nvd.nist.gov/vuln/detail/CVE-2019-18848', 'https://github.com/nov/json-jwt', 'https://lists.debian.org/debian-lts-announce/2020/10/msg00001.html', 'https://github.com/nov/json-jwt/compare/v1.10.2...v1.11.0', 'https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a'} | null | {'https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a'} | {'https://github.com/nov/json-jwt/commit/ada16e772906efdd035e3df49cb2ae372f0f948a'} |
RubyGems | GHSA-85r7-w5mv-c849 | Moderate severity vulnerability that affects rack | rack/file.rb (Rack::File) in Rack 1.5.x before 1.5.2 and 1.4.x before 1.4.5 allows attackers to access arbitrary files outside the intended root directory via a crafted PATH_INFO environment variable, probably a directory traversal vulnerability that is remotely exploitable, aka "symlink path traversals." | {'CVE-2013-0262'} | 2022-03-03T05:14:17.530513Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-22'} | {'http://secunia.com/advisories/52033', 'https://gist.github.com/rentzsch/4736940', 'https://github.com/advisories/GHSA-85r7-w5mv-c849', 'https://github.com/rack/rack', 'https://nvd.nist.gov/vuln/detail/CVE-2013-0262', 'https://bugzilla.redhat.com/show_bug.cgi?id=909071', 'http://rack.github.com/', 'https://github.com/rack/rack/blob/master/lib/rack/file.rb#L56', 'https://bugzilla.redhat.com/show_bug.cgi?id=909072', 'https://groups.google.com/forum/#!msg/rack-devel/bf937jPZxJM/1s6x95vIhmAJ', 'http://lists.opensuse.org/opensuse-updates/2013-03/msg00048.html', 'https://groups.google.com/forum/#!msg/rack-devel/mZsuRonD7G8/DpZIOmMLbOgJ', 'https://github.com/rack/rack/commit/6f237e4c9fab649d3750482514f0fde76c56ab30'} | null | {'https://github.com/rack/rack/commit/6f237e4c9fab649d3750482514f0fde76c56ab30'} | {'https://github.com/rack/rack/commit/6f237e4c9fab649d3750482514f0fde76c56ab30'} |
RubyGems | GHSA-wh98-p28r-vrc9 | Exposure of information in Action Pack | ### Impact
Under certain circumstances response bodies will not be closed, for example a [bug in a webserver](https://github.com/puma/puma/pull/2812) 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`.
Upgrading to the FIXED versions of Rails will ensure mitigation of this issue even in the context of a buggy webserver or middleware implementation.
### Patches
This has been fixed in Rails 7.0.2.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
### Workarounds
Upgrading is highly recommended, but to work around this problem the following middleware can be used:
```ruby
class GuardedExecutor < ActionDispatch::Executor
def call(env)
ensure_completed!
super
end
private
def ensure_completed!
@executor.new.complete! if @executor.active?
end
end
# Ensure the guard is inserted before ActionDispatch::Executor
Rails.application.configure do
config.middleware.swap ActionDispatch::Executor, GuardedExecutor, executor
end
``` | {'CVE-2022-23633'} | 2022-03-03T05:13:17.293702Z | 2022-02-11T20:49:14Z | HIGH | null | {'CWE-200'} | {'http://www.openwall.com/lists/oss-security/2022/02/11/5', 'https://github.com/rails/rails', 'https://discuss.rubyonrails.org/t/cve-2022-23633-possible-exposure-of-information-vulnerability-in-action-pack/80016', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23633', 'https://github.com/rails/rails/security/advisories/GHSA-wh98-p28r-vrc9', 'https://github.com/rails/rails/commit/f9a2ad03943d5c2ba54e1d45f155442b519c75da', 'https://rubyonrails.org/2022/2/11/Rails-7-0-2-2-6-1-4-6-6-0-4-6-and-5-2-6-2-have-been-released'} | null | {'https://github.com/rails/rails/commit/f9a2ad03943d5c2ba54e1d45f155442b519c75da'} | {'https://github.com/rails/rails/commit/f9a2ad03943d5c2ba54e1d45f155442b519c75da'} |
RubyGems | GHSA-84j7-475p-hp8v | HTTP Response Splitting in Puma | In Puma (RubyGem) before 4.3.2 and 3.12.3, if an application using Puma allows untrusted input in a response header,
an attacker can use newline characters (i.e. `CR`, `LF` or`/r`, `/n`) 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.
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-2019-16254, which fixed this vulnerability for the WEBrick Ruby web server.
This has been fixed in versions 4.3.2 and 3.12.3 by checking all headers for line endings and rejecting headers with those characters. | {'CVE-2020-5247'} | 2022-03-03T05:13:06.415138Z | 2020-02-28T16:53:55Z | MODERATE | null | {'CWE-113'} | {'https://owasp.org/www-community/attacks/HTTP_Response_Splitting', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5247', '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://github.com/puma/puma/commit/c36491756f68a9d6a8b3a49e7e5eb07fe6f1332f', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DIHVO3CQMU7BZC7FCTSRJ33YDNS3GFPK/', 'https://www.ruby-lang.org/en/news/2019/10/01/http-response-splitting-in-webrick-cve-2019-16254', 'https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v'} | null | {'https://github.com/puma/puma/commit/c36491756f68a9d6a8b3a49e7e5eb07fe6f1332f'} | {'https://github.com/puma/puma/commit/c36491756f68a9d6a8b3a49e7e5eb07fe6f1332f'} |
RubyGems | GHSA-c7j7-p5jq-26ff | Low severity vulnerability that affects passenger | Phusion Passenger before 4.0.38 allows local users to write to certain files and directories via a symlink attack on (1) control_process.pid or a (2) generation-* file. | {'CVE-2014-1831'} | 2022-03-03T05:13:06.506859Z | 2018-10-10T17:29:20Z | LOW | null | null | {'https://github.com/phusion/passenger/commit/34b1087870c2', 'https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736958', 'https://github.com/phusion/passenger', 'https://bugzilla.redhat.com/show_bug.cgi?id=1058992', 'http://openwall.com/lists/oss-security/2014/01/30/3', 'https://github.com/advisories/GHSA-c7j7-p5jq-26ff', 'http://lists.fedoraproject.org/pipermail/package-announce/2015-February/149032.html', 'https://nvd.nist.gov/vuln/detail/CVE-2014-1831', 'http://openwall.com/lists/oss-security/2014/01/28/8'} | null | {'https://github.com/phusion/passenger/commit/34b1087870c2'} | {'https://github.com/phusion/passenger/commit/34b1087870c2'} |
RubyGems | GHSA-w6rc-q387-vpgq | Moderate severity vulnerability that affects passenger | ext/common/ServerInstanceDir.h in Phusion Passenger gem before 4.0.6 for Ruby allows local users to gain privileges or possibly change the ownership of arbitrary directories via a symlink attack on a directory with a predictable name in /tmp/. | {'CVE-2013-4136'} | 2022-03-03T05:12:38.652146Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-59'} | {'https://github.com/advisories/GHSA-w6rc-q387-vpgq', 'https://github.com/phusion/passenger/blob/release-4.0.6/NEWS', 'https://code.google.com/p/phusion-passenger/issues/detail?id=910', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4136', 'https://github.com/phusion/passenger/commit/5483b3292cc2af1c83033eaaadec20dba4dcfd9b', 'https://github.com/phusion/passenger', 'http://rhn.redhat.com/errata/RHSA-2013-1136.html', 'http://www.openwall.com/lists/oss-security/2013/07/16/6'} | null | {'https://github.com/phusion/passenger/commit/5483b3292cc2af1c83033eaaadec20dba4dcfd9b'} | {'https://github.com/phusion/passenger/commit/5483b3292cc2af1c83033eaaadec20dba4dcfd9b'} |
RubyGems | GHSA-49r3-2549-3633 | omniauth-apple allows attacker to fake their email address during authentication | ### Impact
This vulnerability impacts applications using the [omniauth-apple](https://github.com/nhosoya/omniauth-apple) strategy of OmniAuth and using the `info.email` field of OmniAuth's [Auth Hash Schema](https://github.com/omniauth/omniauth/wiki/Auth-Hash-Schema) for any kind of identification. The value of this field may be set to any value of the attacker's choice including email addresses of other users.
For example, an application using omniauth-apple with the following code will be impacted:
```ruby
def omniauth_callback
auth_hash = request.env['omniauth.auth']
@authenticated_user = User.find_by(email: auth_hash.info.email)
end
```
Applications not using `info.email` for identification but are instead using the `uid` field are not impacted in the same manner. Note, these applications may still be negatively affected if the value of `info.email` is being used for other purposes.
### Patches
Applications using affected versions of omniauth-apple are advised to upgrade to omniauth-apple version 1.0.1 or later.
### Workarounds
If unable to upgrade to a patched version, monkey patching `OmniAuth::Strategies::Apple#email` as follows is advised as a workaround:
```ruby
module OmniAuth
module Strategies
class Apple
def email
id_info['email']
end
end
end
end
``` | {'CVE-2020-26254'} | 2022-03-03T05:13:18.653035Z | 2020-12-08T14:18:19Z | LOW | null | {'CWE-290'} | {'https://github.com/nhosoya/omniauth-apple/blob/master/CHANGELOG.md#101---2020-12-03', 'https://github.com/nhosoya/omniauth-apple/commit/b37d5409213adae2ca06a67fec14c8d3d07d9016', 'https://github.com/nhosoya/omniauth-apple/security/advisories/GHSA-49r3-2549-3633', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26254'} | null | {'https://github.com/nhosoya/omniauth-apple/commit/b37d5409213adae2ca06a67fec14c8d3d07d9016'} | {'https://github.com/nhosoya/omniauth-apple/commit/b37d5409213adae2ca06a67fec14c8d3d07d9016'} |
RubyGems | GHSA-688c-3x49-6rqj | Moderate severity vulnerability that affects rack-protection | Sinatra rack-protection versions 1.5.4 and 2.0.0.rc3 and earlier contains a timing attack vulnerability in the CSRF token checking that can result in signatures can be exposed. This attack appear to be exploitable via network connectivity to the ruby application. This vulnerability appears to have been fixed in 1.5.5 and 2.0.0. | {'CVE-2018-1000119'} | 2022-03-03T05:12:58.358411Z | 2018-03-07T22:22:22Z | MODERATE | null | {'CWE-203'} | {'https://nvd.nist.gov/vuln/detail/CVE-2018-1000119', 'https://github.com/sinatra/rack-protection', 'https://www.debian.org/security/2018/dsa-4247', 'https://github.com/sinatra/sinatra/commit/8aa6c42ef724f93ae309fb7c5668e19ad547eceb#commitcomment-27964109', 'https://github.com/advisories/GHSA-688c-3x49-6rqj', 'https://access.redhat.com/errata/RHSA-2018:1060', 'https://github.com/sinatra/rack-protection/pull/98'} | null | {'https://github.com/sinatra/sinatra/commit/8aa6c42ef724f93ae309fb7c5668e19ad547eceb'} | {'https://github.com/sinatra/sinatra/commit/8aa6c42ef724f93ae309fb7c5668e19ad547eceb'} |
RubyGems | GHSA-q97v-764g-r2rp | High severity vulnerability that affects gollum and gollum-lib | The gollum-grit_adapter Ruby gem dependency in gollum before 3.1.1 and the gollum-lib gem dependency in gollum-lib before 4.0.1 when the string "master" is in any of the wiki documents, allows remote authenticated users to execute arbitrary code via the -O or --open-files-in-pager flags. | {'CVE-2014-9489'} | 2022-03-03T05:13:49.192780Z | 2017-11-16T01:47:37Z | HIGH | null | {'CWE-284'} | {'https://github.com/gollum/grit_adapter/commit/4520d973c81fecfebbeacd2ef2f1849d763951c7', 'https://github.com/gollum/gollum/issues/913', 'https://github.com/advisories/GHSA-q97v-764g-r2rp', 'http://www.securityfocus.com/bid/71499', 'https://github.com/gollum/gollum', 'https://nvd.nist.gov/vuln/detail/CVE-2014-9489', 'http://www.openwall.com/lists/oss-security/2015/01/03/19'} | null | {'https://github.com/gollum/grit_adapter/commit/4520d973c81fecfebbeacd2ef2f1849d763951c7'} | {'https://github.com/gollum/grit_adapter/commit/4520d973c81fecfebbeacd2ef2f1849d763951c7'} |
RubyGems | GHSA-m2q3-53fq-7h66 | Moderate severity vulnerability that affects gollum | The Precious module in gollum before 4.0.1 allows remote attackers to read arbitrary files by leveraging the lack of a certain temporary-file check. | {'CVE-2015-7314'} | 2022-03-03T05:12:35.175360Z | 2018-08-28T22:33:51Z | MODERATE | null | {'CWE-200'} | {'https://nvd.nist.gov/vuln/detail/CVE-2015-7314', 'https://github.com/gollum/gollum/issues/1070', 'https://github.com/gollum/gollum/commit/ce68a88293ce3b18c261312392ad33a88bb69ea1', 'http://jvn.jp/en/jp/JVN27548431/index.html', 'https://github.com/advisories/GHSA-m2q3-53fq-7h66', 'http://jvndb.jvn.jp/jvndb/JVNDB-2015-000149', 'https://github.com/gollum/gollum', 'http://www.openwall.com/lists/oss-security/2015/09/22/12'} | null | {'https://github.com/gollum/gollum/commit/ce68a88293ce3b18c261312392ad33a88bb69ea1'} | {'https://github.com/gollum/gollum/commit/ce68a88293ce3b18c261312392ad33a88bb69ea1'} |
RubyGems | GHSA-cf36-985g-v73c | Moderate severity vulnerability that affects omniauth-facebook | The omniauth-facebook gem 1.4.1 before 1.5.0 does not properly store the session parameter, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks via the state parameter. | {'CVE-2013-4562'} | 2022-03-03T05:13:58.524578Z | 2017-10-24T18:33:37Z | MODERATE | null | {'CWE-352'} | {'https://groups.google.com/d/msg/ruby-security-ann/-tJHNlTiPh4/9SJxdEWLIawJ', 'http://seclists.org/oss-sec/2013/q4/267', 'http://www.osvdb.org/99693', 'https://github.com/mkdynamic/omniauth-facebook/commit/ccfcc26fe7e34acbd75ad4a095fd01ce5ff48ee7', 'http://osvdb.org/ref/99/omniauth-facebook_gem.txt', 'https://github.com/advisories/GHSA-cf36-985g-v73c', 'https://nvd.nist.gov/vuln/detail/CVE-2013-4562', 'https://github.com/mkdynamic/omniauth-faceboo', 'http://seclists.org/oss-sec/2013/q4/264'} | null | {'https://github.com/mkdynamic/omniauth-facebook/commit/ccfcc26fe7e34acbd75ad4a095fd01ce5ff48ee7'} | {'https://github.com/mkdynamic/omniauth-facebook/commit/ccfcc26fe7e34acbd75ad4a095fd01ce5ff48ee7'} |
RubyGems | GHSA-m7fq-cf8q-35q7 | High severity vulnerability that affects crack | The crack gem 0.3.1 and earlier for Ruby does not properly restrict casts of string values, which might allow remote attackers to conduct object-injection attacks and execute arbitrary code, or cause a denial of service (memory and CPU consumption) by leveraging Action Pack support for (1) YAML type conversion or (2) Symbol type conversion, a similar vulnerability to CVE-2013-0156. | {'CVE-2013-1800'} | 2022-03-03T05:12:56.495744Z | 2017-10-24T18:33:37Z | HIGH | null | null | {'https://github.com/jnunemaker/crack/commit/e3da1212a1f84a898ee3601336d1dbbf118fb5f6', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1800', 'https://support.cloud.engineyard.com/entries/22915701-january-14-2013-security-vulnerabilities-httparty-extlib-crack-nori-update-these-gems-immediately', 'http://lists.opensuse.org/opensuse-security-announce/2013-04/msg00003.html', 'https://bugzilla.redhat.com/show_bug.cgi?id=917236', 'https://bugzilla.novell.com/show_bug.cgi?id=804721', 'https://github.com/advisories/GHSA-m7fq-cf8q-35q7', 'http://secunia.com/advisories/52897'} | null | {'https://github.com/jnunemaker/crack/commit/e3da1212a1f84a898ee3601336d1dbbf118fb5f6'} | {'https://github.com/jnunemaker/crack/commit/e3da1212a1f84a898ee3601336d1dbbf118fb5f6'} |
RubyGems | GHSA-3j95-fjv2-3m4p | CSS Injection in Chartkick gem | The Chartkick gem through 3.3.2 for Ruby allows Cascading Style Sheets (CSS) Injection (without attribute). | {'CVE-2020-16254'} | 2022-03-03T05:13:43.419894Z | 2020-08-12T14:29:15Z | MODERATE | null | {'CWE-74'} | {'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/chartkick/CVE-2020-16254.yml', 'https://github.com/ankane/chartkick/issues/546', 'https://github.com/ankane/chartkick', 'https://nvd.nist.gov/vuln/detail/CVE-2020-16254', 'https://github.com/ankane/chartkick/commit/ba67ab5e603de4d94676790fdac425f8199f1c4f'} | null | {'https://github.com/ankane/chartkick/commit/ba67ab5e603de4d94676790fdac425f8199f1c4f'} | {'https://github.com/ankane/chartkick/commit/ba67ab5e603de4d94676790fdac425f8199f1c4f'} |
RubyGems | GHSA-mq35-wqvf-r23c | Sinatra has XSS via 400 Bad Request page via params parser exception | Sinatra before 2.0.2 has XSS via the 400 Bad Request page that occurs upon a params parser exception. | {'CVE-2018-11627'} | 2022-04-26T18:17:15.940159Z | 2018-06-05T21:32:06Z | MODERATE | null | {'CWE-79'} | {'https://github.com/sinatra/sinatra', 'https://github.com/sinatra/sinatra/issues/1428', 'https://access.redhat.com/errata/RHSA-2019:0315', 'https://nvd.nist.gov/vuln/detail/CVE-2018-11627', 'https://github.com/sinatra/sinatra/commit/12786867d6faaceaec62c7c2cb5b0e2dc074d71a', 'https://github.com/advisories/GHSA-mq35-wqvf-r23c', 'https://access.redhat.com/errata/RHSA-2019:0212'} | null | {'https://github.com/sinatra/sinatra/commit/12786867d6faaceaec62c7c2cb5b0e2dc074d71a'} | {'https://github.com/sinatra/sinatra/commit/12786867d6faaceaec62c7c2cb5b0e2dc074d71a'} |
RubyGems | GHSA-58r4-h6v8-jcvm | Regression in JWT Signature Validation | ### Overview
Versions after and including `2.3.0` are improperly validating the JWT token signature when using the `JWTValidator.verify` method. Improper validation of the JWT token signature when not using the default Authorization Code Flow can allow an attacker to bypass authentication and authorization.
### Am I affected?
You are affected by this vulnerability if all of the following conditions apply:
- You are using `omniauth-auth0`.
- You are using `JWTValidator.verify` method directly OR you are not authenticating using the SDK’s default Authorization Code Flow.
### How to fix that?
Upgrade to version `2.4.1`.
### Will this update impact my users?
The fix provided in this version will not affect your users. | {'CVE-2020-15240'} | 2022-03-03T05:14:16.039069Z | 2020-11-03T02:31:38Z | HIGH | null | {'CWE-347', 'CWE-287'} | {'https://github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a', 'https://rubygems.org/gems/omniauth-auth0', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15240', 'https://github.com/auth0/omniauth-auth0/security/advisories/GHSA-58r4-h6v8-jcvm', 'https://github.com/auth0/omniauth-auth0'} | null | {'https://github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a'} | {'https://github.com/auth0/omniauth-auth0/commit/fd3a14f4ccdfbc515d1121d6378ff88bf55a7a7a'} |
RubyGems | GHSA-fcqf-h4h4-695m | Moderate severity vulnerability that affects actionpack | CRLF injection vulnerability in actionpack/lib/action_controller/response.rb in Ruby on Rails 2.3.x before 2.3.13 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the Content-Type header. | {'CVE-2011-3186'} | 2022-03-03T05:12:52.686804Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-94'} | {'https://nvd.nist.gov/vuln/detail/CVE-2011-3186', 'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'https://github.com/rails/rails/commit/11dafeaa7533be26441a63618be93a03869c83a9', 'http://secunia.com/advisories/45921', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065137.html', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'http://www.debian.org/security/2011/dsa-2301', 'http://groups.google.com/group/rubyonrails-security/msg/bbe342e43abaa78c?dmode=source&output=gplain', 'https://bugzilla.redhat.com/show_bug.cgi?id=732156', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'https://github.com/advisories/GHSA-fcqf-h4h4-695m', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/11dafeaa7533be26441a63618be93a03869c83a9'} | {'https://github.com/rails/rails/commit/11dafeaa7533be26441a63618be93a03869c83a9'} |
RubyGems | GHSA-jrfj-98qg-qjgv | Denial of service in sidekiq | In api.rb in Sidekiq before 6.4.0 and 5.2.10, there is no limit on the number of days when requesting stats for the graph. This overloads the system, affecting the Web UI, and makes it unavailable to users. | {'CVE-2022-23837'} | 2022-03-11T20:16:49.892671Z | 2022-01-27T14:42:37Z | HIGH | null | {'CWE-400', 'CWE-770'} | {'https://github.com/mperham/sidekiq', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23837', 'https://github.com/rubysec/ruby-advisory-db/pull/495', 'https://github.com/mperham/sidekiq/commit/7785ac1399f1b28992adb56055f6acd88fd1d956', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00015.html', 'https://github.com/TUTUMSPACE/exploits/blob/main/sidekiq.md'} | null | {'https://github.com/mperham/sidekiq/commit/7785ac1399f1b28992adb56055f6acd88fd1d956'} | {'https://github.com/mperham/sidekiq/commit/7785ac1399f1b28992adb56055f6acd88fd1d956'} |
RubyGems | GHSA-7vxr-6cxg-j3x8 | OS Command Injection in ftpd | The ftpd gem 0.2.1 for Ruby allows remote attackers to execute arbitrary OS commands via shell metacharacters in a LIST or NLST command argument within FTP protocol traffic. | {'CVE-2013-2512'} | 2022-03-03T05:13:15.551362Z | 2021-10-12T22:33:59Z | CRITICAL | null | {'CWE-78'} | {'https://github.com/wconrad/ftpd/commit/828064f1a0ab69b2642c59cab8292a67bb44182c', 'http://vapidlabs.com/advisory.php?v=34', 'https://nvd.nist.gov/vuln/detail/CVE-2013-2512', 'https://github.com/wconrad/ftpd'} | null | {'https://github.com/wconrad/ftpd/commit/828064f1a0ab69b2642c59cab8292a67bb44182c'} | {'https://github.com/wconrad/ftpd/commit/828064f1a0ab69b2642c59cab8292a67bb44182c'} |
RubyGems | GHSA-j5rj-g695-342r | Moderate severity vulnerability that affects fat_free_crm | FatFreeCRM version <=0.14.1, >=0.15.0 <=0.15.1, >=0.16.0 <=0.16.3, >=0.17.0 <=0.17.2, ==0.18.0 contains a Cross Site Scripting (XSS) vulnerability in commit 6d60bc8ed010c4eda05d6645c64849f415f68d65 that can result in Javascript execution. This attack appear to be exploitable via Content with Javascript payload will be executed on end user browsers when they visit the page. This vulnerability appears to have been fixed in 0.18.1, 0.17.3, 0.16.4, 0.15.2, 0.14.2. | {'CVE-2018-1000842'} | 2022-03-03T05:13:50.305320Z | 2018-12-20T22:01:54Z | MODERATE | null | {'CWE-79'} | {'https://github.com/asteinhauser/fat_free_crm/commit/306f940b26ccf3f406665f07bece1229a7a5dcfa', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000842', 'https://groups.google.com/forum/#!topic/fat-free-crm-users/TxsdZXSe7Jc', 'https://github.com/advisories/GHSA-j5rj-g695-342r', 'https://github.com/asteinhauser/fat_free_crm/issues/1', 'https://github.com/asteinhauser/fat_free_crm/', 'https://github.com/fatfreecrm/fat_free_crm/wiki/XSS-Vulnerability-%282018-10-27%29'} | null | {'https://github.com/asteinhauser/fat_free_crm/commit/306f940b26ccf3f406665f07bece1229a7a5dcfa'} | {'https://github.com/asteinhauser/fat_free_crm/commit/306f940b26ccf3f406665f07bece1229a7a5dcfa'} |
RubyGems | GHSA-r53w-g4xm-3gc6 | Cross-site scripting in Haml | In haml versions prior to version 5.0.0.beta.2, when using user input to perform tasks on the server, characters like < > " ' must be escaped properly. In this case, the ' character was missed. An attacker can manipulate the input to introduce additional attributes, potentially executing code. | {'CVE-2017-1002201'} | 2022-03-03T05:14:02.155160Z | 2019-10-21T21:59:13Z | MODERATE | null | {'CWE-79'} | {'https://lists.debian.org/debian-lts-announce/2019/11/msg00007.html', 'https://snyk.io/vuln/SNYK-RUBY-HAML-20362', 'https://security.gentoo.org/glsa/202007-27', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1002201', 'https://github.com/haml/haml/commit/18576ae6e9bdcb4303fdbe6b3199869d289d67c2', 'https://github.com/haml/haml/', 'https://lists.debian.org/debian-lts-announce/2021/12/msg00028.html'} | null | {'https://github.com/haml/haml/commit/18576ae6e9bdcb4303fdbe6b3199869d289d67c2'} | {'https://github.com/haml/haml/commit/18576ae6e9bdcb4303fdbe6b3199869d289d67c2'} |
RubyGems | GHSA-pr3h-jjhj-573x | High severity vulnerability that affects sprockets | Specially crafted requests can be used to access files that exist on the filesystem that is outside an application's root directory, when the Sprockets server is used in production.
All users running an affected release should either upgrade or use one of the work arounds immediately.
Workaround:
In Rails applications, work around this issue, set `config.assets.compile = false` and `config.public_file_server.enabled = true` in an initializer and precompile the assets.
This work around will not be possible in all hosting environments and upgrading is advised. | {'CVE-2018-3760'} | 2022-03-03T05:12:55.724463Z | 2018-06-20T22:18:58Z | HIGH | null | {'CWE-22', 'CWE-200'} | {'https://github.com/rails/sprockets/commit/9c34fa05900b968d74f08ccf40917848a7be9441', 'https://www.debian.org/security/2018/dsa-4242', 'https://access.redhat.com/errata/RHSA-2018:2561', 'https://access.redhat.com/errata/RHSA-2018:2244', 'https://github.com/rails/sprockets/commit/18b8a7f07a50c245e9aee7854ecdbe606bbd8bb5', 'https://access.redhat.com/errata/RHSA-2018:2245', 'https://access.redhat.com/errata/RHSA-2018:2745', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3760', 'https://github.com/advisories/GHSA-pr3h-jjhj-573x', 'https://', 'https://github.com/rails/sprockets', 'https://github.com/rails/sprockets/commit/c09131cf5b2c479263939c8582e22b98ed616c5f', 'https://groups.google.com/d/msg/rubyonrails-security/ft_J--l55fM/7roDfQ50BwAJ'} | null | {'https://github.com/rails/sprockets/commit/c09131cf5b2c479263939c8582e22b98ed616c5f', 'https://github.com/rails/sprockets/commit/18b8a7f07a50c245e9aee7854ecdbe606bbd8bb5', 'https://github.com/rails/sprockets/commit/9c34fa05900b968d74f08ccf40917848a7be9441'} | {'https://github.com/rails/sprockets/commit/9c34fa05900b968d74f08ccf40917848a7be9441', 'https://github.com/rails/sprockets/commit/18b8a7f07a50c245e9aee7854ecdbe606bbd8bb5', 'https://github.com/rails/sprockets/commit/c09131cf5b2c479263939c8582e22b98ed616c5f'} |
RubyGems | GHSA-xmgj-5fh3-xjmm | Path traversal when MessageBus::Diagnostics is enabled | ### Impact
Users who deployed message bus with diagnostics features enabled (default off) were vulnerable to a path traversal bug, which could lead to disclosure of secret information on a machine if an unintended user were to gain access to the diagnostic route. The impact is also greater if there is no proxy for your web application as the number of steps up the directories is not bounded. For deployments which uses a proxy, the impact varies. For example, If a request goes through a proxy like Nginx with `merge_slashes` enabled, the number of steps up the directories that can be read is limited to 3 levels.
### Patches
Patched in 3.3.7.
### Workarounds
Disable MessageBus::Diagnostics in production like environments.
| {'CVE-2021-43840'} | 2022-03-03T05:13:02.780448Z | 2021-12-17T19:59:13Z | MODERATE | null | {'CWE-22'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-43840', 'https://github.com/discourse/message_bus', 'https://github.com/discourse/message_bus/security/advisories/GHSA-xmgj-5fh3-xjmm', 'https://github.com/discourse/message_bus/commit/9b6deee01ed474c7e9b5ff65a06bb0447b4db2ba'} | null | {'https://github.com/discourse/message_bus/commit/9b6deee01ed474c7e9b5ff65a06bb0447b4db2ba'} | {'https://github.com/discourse/message_bus/commit/9b6deee01ed474c7e9b5ff65a06bb0447b4db2ba'} |
RubyGems | GHSA-w3j4-76qw-wwjm | Older releases of better_errors open to Cross-Site Request Forgery attack | ### Impact
better_errors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct "Content-Type" header for these requests, which allowed a cross-origin "simple request" to be made without CORS protection. These together left an application with better_errors enabled open to cross-origin attacks.
_As a developer tool, better_errors documentation strongly recommends addition only to the `development` bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits better_errors to the `development` group (or the non-Rails equivalent)._
### Patches
Starting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to "~> 2.8.3".
### Workarounds
There are no known workarounds to mitigate the risk of using older releases of better_errors.
### References
- Chris Moberly provided [an example attack that uses a now-patched vulnerability of webpack-dev-server in conjunction with Better Errors](https://about.gitlab.com/blog/2021/09/07/why-are-developers-vulnerable-to-driveby-attacks/)
### For more information
If you have any questions or comments about this advisory, please
- Add to the [discussion in better_errors](https://github.com/BetterErrors/better_errors/discussions/507)
- Open an issue in [better_errors](https://github.com/BetterErrors/better_errors)
| {'CVE-2021-39197'} | 2022-03-03T05:14:16.248141Z | 2021-09-07T23:08:24Z | MODERATE | null | {'CWE-352'} | {'https://github.com/BetterErrors/better_errors/commit/8e8e796bfbde4aa088741823c8a3fc6df2089bb0', 'https://github.com/BetterErrors/better_errors', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39197', 'https://github.com/BetterErrors/better_errors/security/advisories/GHSA-w3j4-76qw-wwjm', 'https://github.com/BetterErrors/better_errors/pull/474', 'https://github.com/BetterErrors/better_errors/discussions/507'} | null | {'https://github.com/BetterErrors/better_errors/commit/8e8e796bfbde4aa088741823c8a3fc6df2089bb0'} | {'https://github.com/BetterErrors/better_errors/commit/8e8e796bfbde4aa088741823c8a3fc6df2089bb0'} |
RubyGems | GHSA-2xvj-j3qh-x8c3 | High severity vulnerability that affects private_address_check | private_address_check ruby gem before 0.5.0 is vulnerable to a time-of-check time-of-use (TOCTOU) race condition due to the address the socket uses not being checked. DNS entries with a TTL of 0 can trigger this case where the initial resolution is a public address but the subsequent resolution is a private address. | {'CVE-2018-3759'} | 2022-03-03T05:12:45.204597Z | 2018-07-31T18:13:05Z | HIGH | null | {'CWE-362'} | {'https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3759', 'https://github.com/advisories/GHSA-2xvj-j3qh-x8c3'} | null | {'https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147'} | {'https://github.com/jtdowney/private_address_check/commit/4068228187db87fea7577f7020099399772bb147'} |
RubyGems | GHSA-23f7-99jx-m54r | Remote code execution in dependabot-core branch names when cloning | ### Impact
Remote code execution vulnerability in `dependabot-common` and `dependabot-go_modules` when a source branch name contains malicious injectable bash code.
For example, if Dependabot is configured to use the following source branch name: `"/$({curl,127.0.0.1})"`, Dependabot will make a HTTP request to the following URL: 127.0.0.1 when cloning the source repository.
When Dependabot is configured to clone the source repository during an update, Dependabot runs a shell command to git clone the repository:
```bash
git clone --no-tags --no-recurse-submodules --depth=1 --branch=<BRANCH> --single-branch <GITHUB_REPO_URL> repo/contents/path
```
Dependabot will always clone the source repository for `go_modules` during the file fetching step and can be configured to clone the repository for other package managers using the `FileFetcher` class from `dependabot-common`.
```ruby
source = Dependabot::Source.new(
provider: "github",
repo: "repo/name",
directory: "/",
branch: "/$({curl,127.0.0.1})",
)
repo_contents_path = "./file/path"
fetcher = Dependabot::FileFetchers.for_package_manager("bundler").
new(source: source, credentials: [],
repo_contents_path: repo_contents_path)
fetcher.clone_repo_contents
```
### Patches
The fix was applied to version `0.125.1`: https://github.com/dependabot/dependabot-core/pull/2727
### Workarounds
Escape the branch name prior to passing it to the `Dependabot::Source` class.
For example using `shellwords`:
```ruby
require "shellwords"
branch = Shellwords.escape("/$({curl,127.0.0.1})")
source = Dependabot::Source.new(
provider: "github",
repo: "repo/name",
directory: "/",
branch: branch,
)
``` | {'CVE-2020-26222'} | 2022-03-03T05:13:27.535302Z | 2020-11-13T15:47:50Z | LOW | null | {'CWE-74'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26222', 'https://rubygems.org/gems/dependabot-common', 'https://github.com/dependabot/dependabot-core/security/advisories/GHSA-23f7-99jx-m54r', 'https://rubygems.org/gems/dependabot-omnibus', 'https://github.com/dependabot/dependabot-core/pull/2727', 'https://github.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5'} | null | {'https://github.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5'} | {'https://github.com/dependabot/dependabot-core/commit/e089116abbe284425b976f7920e502b8e83a61b5'} |
RubyGems | GHSA-vr8q-g5c7-m54m | XXE in Nokogiri | ### Severity
Nokogiri maintainers have evaluated this as [__Low Severity__ (CVSS3 2.6)](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N).
### Description
In Nokogiri versions <= 1.11.0.rc3, XML Schemas parsed by `Nokogiri::XML::Schema` are **trusted** by default, allowing external resources to be accessed over the network, potentially enabling XXE or SSRF attacks.
This behavior is counter to the security policy followed by Nokogiri maintainers, which is to treat all input as **untrusted** by default whenever possible.
Please note that this security fix was pushed into a new minor version, 1.11.x, rather than a patch release to the 1.10.x branch, because it is a breaking change for some schemas and the risk was assessed to be "Low Severity".
### Affected Versions
Nokogiri `<= 1.10.10` as well as prereleases `1.11.0.rc1`, `1.11.0.rc2`, and `1.11.0.rc3`
### Mitigation
There are no known workarounds for affected versions. Upgrade to Nokogiri `1.11.0.rc4` or later.
If, after upgrading to `1.11.0.rc4` or later, you wish to re-enable network access for resolution of external resources (i.e., return to the previous behavior):
1. Ensure the input is trusted. Do not enable this option for untrusted input.
2. When invoking the `Nokogiri::XML::Schema` constructor, pass as the second parameter an instance of `Nokogiri::XML::ParseOptions` with the `NONET` flag turned off.
So if your previous code was:
``` ruby
# in v1.11.0.rc3 and earlier, this call allows resources to be accessed over the network
# but in v1.11.0.rc4 and later, this call will disallow network access for external resources
schema = Nokogiri::XML::Schema.new(schema)
# in v1.11.0.rc4 and later, the following is equivalent to the code above
# (the second parameter is optional, and this demonstrates its default value)
schema = Nokogiri::XML::Schema.new(schema, Nokogiri::XML::ParseOptions::DEFAULT_SCHEMA)
```
Then you can add the second parameter to indicate that the input is trusted by changing it to:
``` ruby
# in v1.11.0.rc3 and earlier, this would raise an ArgumentError
# but in v1.11.0.rc4 and later, this allows resources to be accessed over the network
schema = Nokogiri::XML::Schema.new(trusted_schema, Nokogiri::XML::ParseOptions.new.nononet)
```
### References
- [This issue's public advisory](https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vr8q-g5c7-m54m)
- [Original Hackerone report (private)](https://hackerone.com/reports/747489)
- [OWASP description of XXE attack](https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing)
- [OWASP description of SSRF attack](https://www.owasp.org/index.php/Server_Side_Request_Forgery)
### Credit
This vulnerability was independently reported by @eric-therond and @gucki.
The Nokogiri maintainers would like to thank [HackerOne](https://hackerone.com/nokogiri) for providing a secure, responsible mechanism for reporting, and for providing their fantastic service to us. | {'CVE-2020-26247'} | 2022-03-03T05:14:07.122463Z | 2020-12-30T18:35:06Z | MODERATE | null | {'CWE-611'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-26247', 'https://lists.debian.org/debian-lts-announce/2021/06/msg00007.html', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-vr8q-g5c7-m54m', 'https://rubygems.org/gems/nokogiri', 'https://github.com/sparklemotion/nokogiri/blob/main/CHANGELOG.md#v1110--2021-01-03', 'https://hackerone.com/reports/747489', 'https://github.com/sparklemotion/nokogiri/releases/tag/v1.11.0.rc4', 'https://github.com/sparklemotion/nokogiri/commit/9c87439d9afa14a365ff13e73adc809cb2c3d97b'} | null | {'https://github.com/sparklemotion/nokogiri/commit/9c87439d9afa14a365ff13e73adc809cb2c3d97b'} | {'https://github.com/sparklemotion/nokogiri/commit/9c87439d9afa14a365ff13e73adc809cb2c3d97b'} |
RubyGems | GHSA-cf3w-g86h-35x4 | Code Injection vulnerability in CarrierWave::RMagick | ### Impact
[CarrierWave::RMagick](https://github.com/carrierwaveuploader/carrierwave/blob/master/lib/carrierwave/processing/rmagick.rb) has a Code Injection vulnerability. Its `#manipulate!` method inappropriately evals the content of mutation option(`:read`/`:write`), allowing attackers to craft a string that can be executed as a Ruby code.
If an application developer supplies untrusted inputs to the option, it will lead to remote code execution(RCE).
(But supplying untrusted input to the option itself is dangerous even in absence of this vulnerability, since is prone to DoS vulnerability - attackers can try to consume massive amounts of memory by resizing to a very large dimension)
### Proof of Concept
```ruby
class MyUploader < CarrierWave::Uploader::Base
include CarrierWave::RMagick
end
MyUploader.new.manipulate!({ read: { density: "1 }; p 'Hacked'; {" }}) # => shows "Hacked"
```
### Patches
Upgrade to [2.1.1](https://rubygems.org/gems/carrierwave/versions/2.1.1) or [1.3.2](https://rubygems.org/gems/carrierwave/versions/1.3.2).
### Workarounds
Stop supplying untrusted input to `#manipulate!`'s mutation option.
### References
[Code Injection Software Attack](https://owasp.org/www-community/attacks/Code_Injection)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [CarrierWave repo](https://github.com/carrierwaveuploader/carrierwave)
* Email me at [mit.shibuya@gmail.com](mailto:mit.shibuya@gmail.com) | {'CVE-2021-21305'} | 2022-04-27T20:00:06.549782Z | 2021-02-08T19:16:39Z | HIGH | null | {'CWE-94', 'CWE-74'} | {'https://github.com/carrierwaveuploader/carrierwave/blob/master/CHANGELOG.md#211---2021-02-08', 'https://github.com/carrierwaveuploader/carrierwave', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21305', 'https://github.com/carrierwaveuploader/carrierwave/commit/387116f5c72efa42bc3938d946b4c8d2f22181b7', 'https://github.com/carrierwaveuploader/carrierwave/blob/master/CHANGELOG.md#132---2021-02-08', 'https://github.com/carrierwaveuploader/carrierwave/security/advisories/GHSA-cf3w-g86h-35x4', 'https://rubygems.org/gems/carrierwave'} | null | {'https://github.com/carrierwaveuploader/carrierwave/commit/387116f5c72efa42bc3938d946b4c8d2f22181b7'} | {'https://github.com/carrierwaveuploader/carrierwave/commit/387116f5c72efa42bc3938d946b4c8d2f22181b7'} |
RubyGems | GHSA-cxf7-qrc5-9446 | Remote shell execution vulnerability in image_processing | ### Impact
When using the `#apply` method from image_processing to apply a series of operations that are coming from unsanitized user input, this allows the attacker to execute shell commands:
```rb
ImageProcessing::Vips.apply({ system: "echo EXECUTED" })
#>> EXECUTED
```
This method is called internally by Active Storage variants, so Active Storage is vulnerable as well.
### Patches
The vulnerability has been fixed in version 1.12.2 of image_processing.
### Workarounds
If you're processing based on user input, it's highly recommended that you always sanitize the user input, by allowing only a constrained set of operations. For example:
```rb
operations = params[:operations]
.map { |operation| [operation[:name], *operation[:value]] }
.select { |name, *| name.to_s.include? %w[resize_to_limit strip ...] } # sanitization
ImageProcessing::Vips.apply(operations)
``` | {'CVE-2022-24720'} | 2022-03-10T16:02:30.163279Z | 2022-03-01T22:22:26Z | CRITICAL | null | {'CWE-20', 'CWE-78'} | {'https://github.com/janko/image_processing/security/advisories/GHSA-cxf7-qrc5-9446', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24720', 'https://github.com/janko/image_processing', 'https://github.com/janko/image_processing/commit/038e4574e8f4f4b636a62394e09983c71980dada'} | null | {'https://github.com/janko/image_processing/commit/038e4574e8f4f4b636a62394e09983c71980dada'} | {'https://github.com/janko/image_processing/commit/038e4574e8f4f4b636a62394e09983c71980dada'} |
RubyGems | GHSA-cqxw-3p7v-p9gr | Phusion Passenger uses a known /tmp filename | In Phusion Passenger before 5.1.0, a known /tmp filename was used during passenger-install-nginx-module execution, which could allow local attackers to gain the privileges of the passenger user | {'CVE-2016-10345'} | 2022-04-26T20:45:11.460991Z | 2018-08-21T17:08:03Z | HIGH | null | null | {'https://github.com/phusion/passenger/commit/e5b4b0824d6b648525b4bf63d9fa37e5beeae441', 'https://github.com/phusion/passenger/blob/stable-5.1/CHANGELOG', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10345', 'https://github.com/phusion/passenger/', 'https://github.com/advisories/GHSA-cqxw-3p7v-p9gr'} | null | {'https://github.com/phusion/passenger/commit/e5b4b0824d6b648525b4bf63d9fa37e5beeae441'} | {'https://github.com/phusion/passenger/commit/e5b4b0824d6b648525b4bf63d9fa37e5beeae441'} |
RubyGems | GHSA-r74q-gxcg-73hx | High severity vulnerability that affects simple_form | ## Incorrect Access Control in `file_method?` in `lib/simple_form/form_builder.rb`; a user-supplied string is invoked as a method call
### Impact
For pages that build a form using user input, it is possible for an attacker to manipulate the input and send any method present in the form object. For example:
```erb
<%= simple_form_for @user do |f| %>
<%= f.label @user_supplied_string %>
...
<% end %>
```
The string provided in the variable `@user_supplied_string` would be invoked as a method call inside the `@user` object (unless the string contains any of the following: `password`, `time_zone`, `country`, `email`, `phone` and `url`).
By manipulation that input, an attacker could do any of the following:
- Code execution (call actions like `#destroy`)
- Denial of Service (by executing a computation intensive method)
- Information Disclosure (check the presence of methods, leak user information)
### Patches
The problem was fixed in version `5.0`. Although it's a major version, there should be no issues with upgrading for `4.x`. The reason it was released in a major version is that the configuration `SimpleForm.file_methods` was deprecated in order to fix the problem.
### Workarounds
The issue only happens with pages that build forms based on user-provided input. If your application doesn't do that, you're not affected.
A workaround is to explicitly pass which type you want for an input since the issue lies on Simple Form's automatically discovery of input types. This can be done using the `as` option, like the following:
```erb
<%= form.input :avatar, as: :file %>
```
### References
[TDB]
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/plataformatec/simple_form](https://github.com/plataformatec/simple_form)
* Email us at [opensource@plataformatec.com.br](mailto:opensource@plataformatec.com.br) | {'CVE-2019-16676'} | 2022-03-03T05:11:44.264367Z | 2019-09-30T19:41:15Z | CRITICAL | null | {'CWE-20'} | {'https://github.com/plataformatec/simple_form/security/advisories/GHSA-r74q-gxcg-73hx', 'https://github.com/advisories/GHSA-r74q-gxcg-73hx', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16676', 'https://github.com/plataformatec/simple_form/commits/master', 'http://blog.plataformatec.com.br/2019/09/incorrect-access-control-in-simple-form-cve-2019-16676/'} | null | {'https://github.com/plataformatec/simple_form/commits/master'} | {'https://github.com/plataformatec/simple_form/commits/master'} |
RubyGems | GHSA-x24j-87x9-jvv5 | Improper Authorization in Publify | In Publify, 9.0.0.pre1 to 9.2.4 are vulnerable to Improper Access Control. “guest” role users can self-register even when the admin does not allow. This happens due to front-end restriction only. | {'CVE-2021-25973'} | 2022-03-07T20:47:49.397012Z | 2021-11-03T17:34:22Z | MODERATE | null | {'CWE-285', 'CWE-863'} | {'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25973', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25973', 'https://github.com/publify/publify/', 'https://github.com/publify/publify/commit/3447e0241e921b65f6eb1090453d8ea73e98387e'} | null | {'https://github.com/publify/publify/commit/3447e0241e921b65f6eb1090453d8ea73e98387e'} | {'https://github.com/publify/publify/commit/3447e0241e921b65f6eb1090453d8ea73e98387e'} |
RubyGems | GHSA-r7q2-5gqg-6c7q | Moderate severity vulnerability that affects actionpack | The template selection functionality in actionpack/lib/action_view/template/resolver.rb in Ruby on Rails 3.0.x before 3.0.10 and 3.1.x before 3.1.0.rc6 does not properly handle glob characters, which allows remote attackers to render arbitrary views via a crafted URL, related to a "filter skipping vulnerability." | {'CVE-2011-2929'} | 2022-03-03T05:13:11.142719Z | 2017-10-24T18:33:38Z | MODERATE | null | {'CWE-20'} | {'http://www.openwall.com/lists/oss-security/2011/08/19/11', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065212.html', 'https://github.com/advisories/GHSA-r7q2-5gqg-6c7q', 'http://www.openwall.com/lists/oss-security/2011/08/20/1', 'https://bugzilla.redhat.com/show_bug.cgi?id=731432', 'http://weblog.rubyonrails.org/2011/8/16/ann-rails-3-1-0-rc6', 'https://nvd.nist.gov/vuln/detail/CVE-2011-2929', 'https://github.com/rails/rails/commit/5f94b93279f6d0682fafb237c301302c107a9552', 'http://www.openwall.com/lists/oss-security/2011/08/22/5', 'http://www.openwall.com/lists/oss-security/2011/08/22/13', 'http://lists.fedoraproject.org/pipermail/package-announce/2011-September/065109.html', 'http://www.openwall.com/lists/oss-security/2011/08/22/14', 'https://github.com/rails/rails', 'http://groups.google.com/group/rubyonrails-security/msg/cbbbba6e4f7eaf61?dmode=source&output=gplain', 'http://www.openwall.com/lists/oss-security/2011/08/17/1'} | null | {'https://github.com/rails/rails/commit/5f94b93279f6d0682fafb237c301302c107a9552'} | {'https://github.com/rails/rails/commit/5f94b93279f6d0682fafb237c301302c107a9552'} |
RubyGems | GHSA-ghqm-pgxj-37gq | Moderate severity vulnerability that affects rails-html-sanitizer | Cross-site scripting (XSS) vulnerability in lib/rails/html/scrubbers.rb in the rails-html-sanitizer gem before 1.0.3 for Ruby on Rails 4.2.x and 5.x allows remote attackers to inject arbitrary web script or HTML via a crafted CDATA node. | {'CVE-2015-7580'} | 2022-03-03T05:13:29.804586Z | 2017-10-24T18:33:36Z | MODERATE | null | {'CWE-79'} | {'http://www.securitytracker.com/id/1034816', 'https://groups.google.com/forum/message/raw?msg=rubyonrails-security/uh--W4TDwmI/m_CVZtdbFQAJ', 'http://lists.opensuse.org/opensuse-security-announce/2016-04/msg00053.html', 'https://nvd.nist.gov/vuln/detail/CVE-2015-7580', 'https://github.com/rails/rails-html-sanitizer/commit/63903b0eaa6d2a4e1c91bc86008256c4c8335e78', 'https://github.com/advisories/GHSA-ghqm-pgxj-37gq', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00024.html', 'http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00014.html', 'https://github.com/rails/rails-html-sanitizer/', 'http://www.openwall.com/lists/oss-security/2016/01/25/15'} | null | {'https://github.com/rails/rails-html-sanitizer/commit/63903b0eaa6d2a4e1c91bc86008256c4c8335e78'} | {'https://github.com/rails/rails-html-sanitizer/commit/63903b0eaa6d2a4e1c91bc86008256c4c8335e78'} |
crates.io | GHSA-qc36-q22q-cjw3 | SMTP command injection in lettre | ### Impact
Affected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.
### Fix
The flaw is fixed by correctly handling consecutive CRLF sequences.
### References
* [RUSTSEC-2021-0069](https://rustsec.org/advisories/RUSTSEC-2021-0069.html)
| {'CVE-2021-38189'} | 2021-08-18T18:52:26Z | 2021-07-12T17:03:27Z | CRITICAL | null | {'CWE-147'} | {'https://github.com/lettre/lettre/security/advisories/GHSA-qc36-q22q-cjw3', 'https://github.com/lettre/lettre', 'https://rustsec.org/advisories/RUSTSEC-2021-0069.html', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2', 'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce'} | null | {'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'} | {'https://github.com/lettre/lettre/commit/8bfc20506cc5e098fe6eb3d1cafe3bea791215ce', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'} |
crates.io | GHSA-r626-fc64-3q28 | Data race in abox | An issue was discovered in the abox crate before 0.4.1 for Rust.
Affected versions of this crate implements `Send`/`Sync` for `AtomicBox<T>` without requiring `T: Send`/`T: Sync`. This allows to create data races to `T: !Sync` and send `T: !Send` to another thread.
Such behavior breaks the compile-time thread safety guarantees of Rust, and allows users to incur undefined behavior using safe Rust (e.g. memory corruption from data race).
The flaw was corrected in commit 34c2b9e by adding trait bound `T: Send` to `Send` impl for `AtomicBox<T>` and trait bound `T: Sync` to `Sync` impl for `AtomicBox<T>`. | {'CVE-2020-36441'} | 2021-08-24T19:15:13Z | 2021-08-25T20:59:06Z | HIGH | null | {'CWE-119', 'CWE-362'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0121.html', 'https://github.com/SonicFrog/abox/commit/34c2b9e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36441', 'https://github.com/SonicFrog/abox/pull/2', 'https://github.com/SonicFrog/abox/issues/1', 'https://github.com/SonicFrog/abox'} | null | {'https://github.com/SonicFrog/abox/commit/34c2b9e'} | {'https://github.com/SonicFrog/abox/commit/34c2b9e'} |
crates.io | GHSA-4873-36h9-wv49 | Out-of-bounds read/write and invalid free with `externref`s and GC safepoints in Wasmtime | ### Impact
There was an invalid free and out-of-bounds read and write bug when running Wasm that uses `externref`s in Wasmtime.
To trigger this bug, Wasmtime needs to be running Wasm that uses `externref`s, the host creates non-null `externrefs`, Wasmtime performs a garbage collection (GC), and there has to be a Wasm frame on the stack that is at a GC safepoint where
* there are no live references at this safepoint, and
* there is a safepoint with live references earlier in this frame's function.
Under this scenario, Wasmtime would incorrectly use the GC stack map for the safepoint from earlier in the function instead of the empty safepoint. This would result in Wasmtime treating arbitrary stack slots as `externref`s that needed to be rooted for GC. At the *next* GC, it would be determined that nothing was referencing these bogus `externref`s (because nothing could ever reference them, because they are not really `externref`s) and then Wasmtime would deallocate them and run `<ExternRef as Drop>::drop` on them. This results in a free of memory that is not necessarily on the heap (and shouldn't be freed at this moment even if it was), as well as potential out-of-bounds reads and writes.
Even though support for `externref`s (via the reference types proposal) is enabled by default, unless you are creating non-null `externref`s in your host code or explicitly triggering GCs, you cannot be affected by this bug.
We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.
### Patches
This bug has been patched and users should upgrade to Wasmtime version 0.30.0.
Additionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.
### Workarounds
If you cannot upgrade Wasmtime at this time, you can avoid this bug by disabling the reference types proposal by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types)
### References
* [The Wasm reference types proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/) | {'CVE-2021-39218'} | 2021-09-17T20:05:58Z | 2021-09-20T19:54:16Z | MODERATE | null | {'CWE-590', 'CWE-125', 'CWE-787'} | {'https://crates.io/crates/wasmtime', 'https://github.com/bytecodealliance/wasmtime/commit/398a73f0dd862dbe703212ebae8e34036a18c11c', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/', 'https://github.com/bytecodealliance/wasmtime', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39218', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4873-36h9-wv49'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/398a73f0dd862dbe703212ebae8e34036a18c11c'} | {'https://github.com/bytecodealliance/wasmtime/commit/398a73f0dd862dbe703212ebae8e34036a18c11c'} |
crates.io | GHSA-vc2p-r46x-m3vx | Argument injection in lettre | ### Impact
Affected versions of lettre allowed argument injection to the sendmail command. It was possible, using forged to addresses, to pass arbitrary arguments to the sendmail executable.
Depending on the implementation (original sendmail, postfix, exim, etc.) it could be possible in some cases to write email data into abritrary files (using sendmail's logging features).
*NOTE*: This vulnerability only affects the sendmail transport. Others, including smtp, are not affected.
### Fix
The flaw is corrected by modifying the executed command to stop parsing arguments before passing the destination addresses.
### References
* [RUSTSEC-2020-0069](https://rustsec.org/advisories/RUSTSEC-2020-0069.html)
* [CVE-2020-28247](https://nvd.nist.gov/vuln/detail/CVE-2020-28247) | {'CVE-2020-28247'} | 2021-08-18T20:59:57Z | 2021-08-25T20:56:48Z | MODERATE | null | {'CWE-77'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0069.html', 'https://github.com/lettre/lettre', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28247', 'https://github.com/RustSec/advisory-db/pull/478/files', 'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b', 'https://github.com/lettre/lettre/security/advisories/GHSA-vc2p-r46x-m3vx'} | null | {'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b'} | {'https://github.com/lettre/lettre/pull/508/commits/bbe7cc5381c5380b54fb8bbb4f77a3725917ff0b'} |
crates.io | GHSA-88xq-w8cq-xfg7 | Invalid drop of partially-initialized instances in the pooling instance allocator for modules with defined `externref` globals | ### Impact
There exists a bug in the pooling instance allocator in Wasmtime's runtime where a failure to instantiate an instance for a module that defines an `externref` global will result in an invalid drop of a `VMExternRef` via an uninitialized pointer.
As instance slots may be reused between consecutive instantiations, the value of the uninitialized pointer may be from a previous instantiation and therefore under the control of an attacker via a module's initial values for its globals. If the attacker can somehow determine an address under their control inside the mapped memory representing the instance pool, it is possible to trick the runtime to call `drop_in_place` on a trait object under the attacker's control and therefore cause remote code execution.
Exploiting the bug to cause remote code execution would be very difficult as attackers cannot determine the addresses of globals from code executing within the WebAssembly VM and the memory space for the instance pool cannot be statically determined. Operating system mitigations, such as [address space layout randomization](https://en.wikipedia.org/wiki/Address_space_layout_randomization), would additionally increase the difficulty for attackers to determine useful executable code to target with an exploit. It is also very unlikely that attackers will be able to directly influence the conditions that trigger the bug as described below.
When the conditions to trigger the bug are met, however, it is much easier to exploit this bug to cause a denial of service by crashing the host with an invalid memory read.
The following engine configuration (via [Config](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Config.html)) is required to be impacted by this bug:
* support for the reference types proposal must be enabled (this is the default for `Config`).
* a pooling allocation strategy must be configured via [Config::allocation_strategy](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Config.html#method.allocation_strategy), which is **not the default allocation strategy**.
A module must be instantiated with **all the following characteristics**:
* The module defines at least one table or memory.
* The module defines at least one `externref` global.
During instantiation, **one of the following** must occur to cause the instantiation to fail:
* a call to `mprotect` or `VirtualAlloc` fails (e.g. out-of-memory conditions).
* a resource limiter was configured in the associated `Store` (via [Store::limiter](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Store.html#method.limiter) or [Store::limiter_async](https://docs.rs/wasmtime/0.34.0/wasmtime/struct.Store.html#method.limiter_async)) and the limiter returns `false` from the initial call to `memory_growing` or `table_growing`. **Stores do not have a resource limiter set by default**.
This results in a partially-initialized instance being dropped and that attempts to drop the uninitialized `VMExternRef` representing the defined `externref` global.
We have reason to believe that the effective impact of this bug is relatively small because the usage of `externref` is still uncommon and without a resource limiter configured on the `Store`, which is not the default configuration, it is only possible to trigger the bug from an error returned by `mprotect` or `VirtualAlloc`.
Note that on Linux with the `uffd` feature enabled, it is only possible to trigger the bug from a resource limiter as the call to `mprotect` is skipped; if no resource limiter is used, then this configuration is not vulnerable.
### Patches
The bug has been fixed in 0.34.1 and 0.33.1; users are encouraged to upgrade as soon as possible.
### Workarounds
If it is not possible to upgrade to 0.34.1 or 0.33.1 of the `wasmtime` crate, it is recommend that support for the reference types proposal be disabled by passing `false` to [Config::wasm_reference_types](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_reference_types).
Doing so will prevent modules that use `externref` from being loaded entirely.
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/) | {'CVE-2022-23636'} | 2022-02-16T22:35:03Z | 2022-02-16T22:35:03Z | MODERATE | null | {'CWE-824'} | {'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-88xq-w8cq-xfg7', 'https://github.com/bytecodealliance/wasmtime', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23636', 'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a'} | {'https://github.com/bytecodealliance/wasmtime/commit/886ecc562040bef61faf19438c22285c2d62403a'} |
crates.io | GHSA-2wc6-2rcj-8v76 | scalarmult() vulnerable to degenerate public keys | The `scalarmult()` function included in previous versions of this crate
accepted all-zero public keys, for which the resulting Diffie-Hellman shared
secret will always be zero regardless of the private key used.
This issue was fixed by checking for this class of keys and rejecting them
if they are used.
| {'CVE-2017-1000168'} | 2021-08-05T21:10:47Z | 2021-08-25T21:00:41Z | MODERATE | null | {'CWE-1240'} | {'https://github.com/sodiumoxide/sodiumoxide', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1000168', 'https://rustsec.org/advisories/RUSTSEC-2017-0001.html', 'https://github.com/dnaq/sodiumoxide/issues/154', 'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'} | null | {'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'} | {'https://github.com/sodiumoxide/sodiumoxide/commit/24c7a5550807ac8a09648b5878f19d14c3a69135'} |
crates.io | GHSA-q3cc-7p7g-392c | Use after free in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated because sessions.rs has a use-after-free. | {'CVE-2020-35873'} | 2021-08-19T21:08:56Z | 2021-08-25T20:47:43Z | CRITICAL | null | {'CWE-416'} | {'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35873', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'} | null | {'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'} | {'https://github.com/rusqlite/rusqlite/commit/ac30e169ae51b262bc8cf7026469851ce39b23c6'} |
crates.io | GHSA-m296-j53x-xv95 | Data races in tiny_future | `tiny_future` contains a light-weight implementation of `Future`s. The `Future`
type it has lacked bound on its `Send` and `Sync` traits.
This allows for a bug where non-thread safe types such as `Cell` can be used in
`Future`s and cause data races in concurrent programs.
The flaw was corrected in commit `c791919` by adding trait bounds to `Future`'s
`Send` and `Sync`.
| null | 2021-08-18T23:36:06Z | 2021-08-25T21:00:32Z | MODERATE | null | {'CWE-362'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0118.html', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39', 'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/issues/1', 'https://github.com/KizzyCode/tiny_future'} | null | {'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39'} | {'https://github.com/KizzyCode/tiny_future/commit/c7919199a0f6d1ce0e3c33499d1b37f862c990e4', 'https://github.com/KizzyCode/tiny_future/commit/7ab8a264980d23c2ed64e72f4636f38b7381eb39'} |
crates.io | GHSA-8h4j-vm3r-vcq3 | Use after free in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via an Auxdata API use-after-free. | {'CVE-2020-35870'} | 2021-08-19T21:08:47Z | 2021-08-25T20:47:48Z | CRITICAL | null | {'CWE-416'} | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35870'} | null | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'} | {'https://github.com/rusqlite/rusqlite/commit/2ef3628dac35aeba0a97d5fb3a57746b4e1d62b3'} |
crates.io | GHSA-gq4h-f254-7cw9 | Data races in ticketed_lock | Affected versions of this crate unconditionally implemented `Send` for `ReadTicket<T>` & `WriteTicket<T>`.
This allows to send non-Send `T` to other threads.
This can allows creating data races by cloning types with internal mutability and sending them to other threads (as `T` of `ReadTicket<T>`/`WriteTicket<T>`). Such data races can cause memory corruption or other undefined behavior.
The flaw was corrected in commit a986a93 by adding `T: Send` bounds to `Send` impls of `ReadTicket<T>`/`WriteTicket<T>`.
| null | 2021-08-18T23:35:09Z | 2021-08-25T21:00:34Z | MODERATE | null | {'CWE-362'} | {'https://rustsec.org/advisories/RUSTSEC-2020-0119.html', 'https://github.com/kvark/ticketed_lock/issues/7', 'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f'} | null | {'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f'} | {'https://github.com/kvark/ticketed_lock/pull/8/commits/a986a9335d591fa5c826157d1674d47aa525357f'} |
crates.io | GHSA-p24j-h477-76q3 | Uncontrolled Search Path Element in sharkdp/bat | bat on windows before 0.18.2 executes programs named less.exe from the current working directory. This can lead to unintended code execution. | {'CVE-2021-36753'} | 2021-09-09T16:57:53Z | 2021-08-25T21:01:37Z | HIGH | null | {'CWE-427'} | {'https://github.com/sharkdp/bat', 'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956', 'https://github.com/sharkdp/bat/releases/tag/v0.18.2', 'https://github.com/sharkdp/bat/pull/1724', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36753', 'https://vuln.ryotak.me/advisories/53'} | null | {'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956'} | {'https://github.com/sharkdp/bat/commit/bf2b2df9c9e218e35e5a38ce3d03cffb7c363956'} |
crates.io | GHSA-f6g6-54hm-fhxv | Data races in libsbc | Affected versions of this crate implements `Send` for `Decoder<R>` for any `R: Read`. This allows `Decoder<R>` to contain `R: !Send` and carry (move) it to another thread.
This can result in undefined behavior such as memory corruption from data race on `R`, or dropping `R = MutexGuard<_>` from a thread that didn't lock the mutex.
The flaw was corrected in commit a34d6e1 by adding trait bound `R: Send` to the `Send` impl for `Decoder<R>`. | {'CVE-2020-36440'} | 2021-08-18T19:58:56Z | 2021-08-25T20:59:02Z | HIGH | null | {'CWE-119', 'CWE-362'} | {'https://github.com/mvertescher/libsbc-rs/commit/a34d6e1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36440', 'https://rustsec.org/advisories/RUSTSEC-2020-0120.html', 'https://github.com/mvertescher/libsbc-rs'} | null | {'https://github.com/mvertescher/libsbc-rs/commit/a34d6e1'} | {'https://github.com/mvertescher/libsbc-rs/commit/a34d6e1'} |
crates.io | GHSA-hpqh-2wqx-7qp5 | Memory access due to code generation flaw in Cranelift module | There is a bug in 0.73.0 of the Cranelift x64 backend that can create a scenario that could result in a potential sandbox escape in a WebAssembly module. Users of versions 0.73.0 of Cranelift should upgrade to either 0.73.1 or 0.74 to remediate this vulnerability. Users of Cranelift prior to 0.73.0 should update to 0.73.1 or 0.74 if they were not using the old default backend.
### Description
This bug was introduced in the new backend on 2020-09-08 and first included in a release on 2020-09-30, but the new backend was not the default prior to 0.73.0. The recently-released version 0.73.0 with default settings, and prior versions with an explicit build flag to select the new backend, are vulnerable. The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack, under a specific set of circumstances. If those circumstances occur, the bug could allow access to memory addresses up to 2GiB before the start of the heap allocated for the WebAssembly module.
If the heap bound is larger than 2GiB, then it would be possible to read memory from a computable range dependent on the size of the heap's bound.
The impact of this bug is highly dependent on heap implementation; specifically:
* if the heap has bounds checks, and
* does not rely exclusively on guard pages, and
* the heap bound is 2GiB or smaller
then this bug cannot be used to reach memory from another WebAssembly module heap.
The impact of the vulnerability is mitigated if there is no memory mapped in the range accessible using this bug, for example, if there is a 2 GiB guard region before the WebAssembly module heap.
The bug in question performs a sign-extend instead of a zero-extend on a value loaded from the stack when the register allocator reloads a spilled integer value narrower than 64 bits. This interacts poorly with another optimization: the instruction selector elides a 32-to-64-bit zero-extend operator when we know that an instruction producing a 32-bit value actually zeros the upper 32 bits of its destination register. Hence, we rely on these zeroed bits, but the type of the value is still i32, and the spill/reload reconstitutes those bits as the sign extension of the i32’s MSB.
The issue would thus occur when:
* An i32 value is greater than or equal to 0x8000_0000;
* The value is spilled and reloaded by the register allocator due to high register pressure in the program between the value’s definition and its use;
* The value is produced by an instruction that we know to be "special" in that it zeroes the upper 32 bits of its destination: add, sub, mul, and, or;
* The value is then zero-extended to 64 bits;
* The resulting 64-bit value is used.
Under these circumstances there is a potential sandbox escape when the i32 value is a pointer. The usual code emitted for heap accesses zero-extends the WebAssembly heap address, adds it to a 64-bit heap base, and accesses the resulting address. If the zero-extend becomes a sign-extend, the module could reach backward and access memory up to 2GiB before the start of its heap.
This bug was identified by developers at Fastly following a report from Javier Cabrera Arteaga, KTH Royal Institute of Technology, with support from project Trustful of Stiftelsen för Strategisk Forskning. In addition to supporting the analysis and remediation of this vulnerability, Fastly will publish a related Fastly Security Advisory at [https://www.fastly.com/security-advisories](https://www.fastly.com/security-advisories).
In addition to assessing the nature of the code generation bug in Cranelift, we have also determined that under specific circumstances, both Lucet and Wasmtime using this version of Cranelift may be exploitable.
### General Impact to Lucet
Lucet inherits the heap address computation and bounds-checks of Cranelift, which it uses as its backend code generator. Of particular importance specifically is the address-space layout used by Lucet. In the default configuration for Lucet, only a single module is running, and therefore it is not possible to access memory from another module.
By default, the open source implementation of Lucet uses a maximum heap size of 4 GiB, and an instance slot size of 8 GiB, when invoking an instance from the lucet-wasi command-line tool. These settings are within the range of vulnerability described above, but only a single instance is running, so there is no other instance to read. When embedding the runtime (for example, in a long-running daemon), the default for the heap size as described in the source is 1MB; with this setting, the runtime is not vulnerable.
Lucet allocates its WebAssembly module instances into "instance slots", which are contiguous zones of virtual address space that contain the VM context at the bottom, the WebAssembly heap in the next page after that, a guard region in the middle, and other data at the top: the stack and the globals.
If the instance slot size is less than (max heap) + 2GiB, then the lowest accessible address using the bug will overlap with the prior instance’s heap. If the size of VM context + stack + globals is greater than (4GiB - heap limit), then the highest accessible address using the bug will overlap with this critical data. If neither of these conditions are true, the bug should only result in an access to the prior instance’s guard region.
Generally, if the limit is between 2GiB and 4GiB - ~1MB (depending on stack/global size) and the instance slot size is less than 6GiB, the configuration is vulnerable. If the limit is greater than 4GiB - ~1MB, the configuration is vulnerable regardless of instance slot size. Otherwise, the configuration is not vulnerable.
### General Impact on Wasmtime
In Wasmtime, the same Cranelift heap address computations and heap types are used as above. The memory layout, however, is slightly different, with different outcomes:
* With the mmap implementation impact is mitigated probabilistically if ASLR is enabled.
* With the pooling allocator, the vulnerability only exists if a memory reservation size lower than the default of 6GB is used.
With the default mmap-based instance memory implementation, Wasmtime uses mmap() to allocate a block of memory large enough for the heap and guard region, as specified in its configuration. If the underlying OS implements ASLR (modern Linux, macOS and Windows do) then this address will be randomized, and the region below it will (probabilistically) be free. Hence, the bug is mitigated probabilistically in the default configuration if ASLR is enabled.
If using the pooling allocator, the vulnerability exists if instance memory size (`memory_reservation_size` in InstanceLimit) is strictly less than 6GiB (4 GiB + 2 GiB of guard pages). The default is 6GiB, so the vulnerability is masked in the default pooling allocator configuration.
| {'CVE-2021-32629'} | 2022-04-26T18:11:37Z | 2021-08-25T21:01:55Z | HIGH | null | {'CWE-125'} | {'https://github.com/RustSec/advisory-db/blob/main/crates/cranelift-codegen/RUSTSEC-2021-0067.md', 'https://www.fastly.com/security-advisories/memory-access-due-to-code-generation-flaw-in-cranelift-module', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32629', 'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0', 'https://github.com/bytecodealliance/wasmtime/tree/main/cranelift', 'https://crates.io/crates/cranelift-codegen', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hpqh-2wqx-7qp5'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0'} | {'https://github.com/bytecodealliance/wasmtime/commit/95559c01aaa7c061088a433040f31e8291fb09d0'} |
crates.io | GHSA-686f-ch3r-xwmh | Data races in unicycle | Affected versions of this crate unconditionally implemented `Send` & `Sync` for types `PinSlab<T>` & `Unordered<T, S>`. This allows sending non-Send types to other threads and concurrently accessing non-Sync types from multiple threads.
This can result in a data race & memory corruption when types that provide internal mutability without synchronization are contained within `PinSlab<T>` or `Unordered<T, S>` and accessed concurrently from multiple threads.
The flaw was corrected in commits 92f40b4 & 6a6c367 by adding trait bound `T: Send` to `Send` impls for `PinSlab<T>` & `Unordered<T, S>` and adding `T: Sync` to `Sync` impls for `PinSlab<T>` & `Unordered<T, S>`. | {'CVE-2020-36436'} | 2021-08-24T17:47:59Z | 2021-08-25T20:58:17Z | HIGH | null | {'CWE-119', 'CWE-362'} | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5', 'https://rustsec.org/advisories/RUSTSEC-2020-0116.html', 'https://github.com/udoprog/unicycle/issues/8', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36436', 'https://github.com/udoprog/unicycle'} | null | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5'} | {'https://github.com/udoprog/unicycle/commit/6a6c367a0c25f86f998fa315ea90c328f685b194', 'https://github.com/udoprog/unicycle/commit/92f40b4a2c671553dfa96feacff0265206c44ce5'} |
crates.io | RUSTSEC-2018-0014 | chan is end-of-life; use crossbeam-channel instead | **`chan` has reached its end-of-life and is now deprecated.**
The intended successor of this crate is
[`crossbeam-channel`](https://github.com/crossbeam-rs/crossbeam/tree/master/crossbeam-channel).
Its API is strikingly similar, but comes with a much better `select!` macro,
better performance, a better test suite and an all-around better
implementation. | null | 2020-10-02T01:29:11Z | 2018-07-31T12:00:00Z | null | null | null | {'https://crates.io/crates/chan', 'https://github.com/BurntSushi/chan/commit/0a5c0d4ad4adc90a54ee04a427389acf2e157275', 'https://rustsec.org/advisories/RUSTSEC-2018-0014.html'} | null | {'https://github.com/BurntSushi/chan/commit/0a5c0d4ad4adc90a54ee04a427389acf2e157275'} | {'https://github.com/BurntSushi/chan/commit/0a5c0d4ad4adc90a54ee04a427389acf2e157275'} |
crates.io | RUSTSEC-2021-0069 | SMTP command injection in body | Affected versions of lettre allowed SMTP command injection through an attacker's controlled message body. The module for escaping lines starting with a period wouldn't catch a period that was placed after a double CRLF sequence, allowing the attacker to end the current message and write arbitrary SMTP commands after it.
The flaw is fixed by correctly handling consecutive CRLF sequences. | {'GHSA-qc36-q22q-cjw3', 'CVE-2021-38189'} | 2021-10-19T19:56:47Z | 2021-05-22T12:00:00Z | null | null | null | {'https://rustsec.org/advisories/RUSTSEC-2021-0069.html', 'https://crates.io/crates/lettre', 'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'} | null | {'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'} | {'https://github.com/lettre/lettre/pull/627/commits/93458d01fed0ec81c0e7b4e98e6f35961356fae2'} |
crates.io | GHSA-hf79-8hjp-rrvq | Use After Free in lucet | ### Impact
There is a bug in the main branch of Lucet's `lucet-runtime` that allows a use-after-free in an `Instance` object that could result in memory corruption, data race, or other related issues. This bug was introduced early in the development of Lucet and is present in all releases. As a result of this bug, and dependent on the memory backing for the `Instance` objects, it is possible to trigger a use-after-free when the `Instance` is dropped.
### Patches
Users should upgrade to the `main` branch of the Lucet repository. Lucet does not provide versioned releases on crates.io.
### Workarounds
There is no way to remediate this vulnerability without upgrading.
### Description
Lucet uses a "pool" allocator for new WebAssembly instances that are created. This pool allocator manages everything from the linear memory of the wasm instance, the runtime stack for async switching, as well as the memory behind the Instance itself. `Instances` are referred to via an `InstanceHandle` type which will, on drop, release the memory backing the Instance back to the pool.
When an Instance is dropped, the fields of the `Instance` are destructed top-to-bottom, however when the `alloc: Alloc` field is destructed, the memory backing the `Instance` is released back to the pool before the destructors of the remaining fields are run. If another thread allocates the same memory from the pool while these destructors are still running, a race condition occurs that can lead to use-after-free errors.
The bug was corrected by changing how the `InstanceHandle` destructor operates to ensure that the memory backing an Instance is only returned to the pool once the `Instance` has been completely destroyed.
This security advisory has been assigned CVE-2021-43790.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [lucet repository](https://github.com/bytecodealliance/lucet)
* Email [the lucet team](mailto:lucet@fastly.com)
* See the [Bytecode Alliance security policy](https://bytecodealliance.org/security)
| {'CVE-2021-43790'} | 2021-11-30T22:05:58Z | 2021-11-30T22:20:36Z | HIGH | null | {'CWE-416'} | {'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8', 'https://crates.io/crates/lucet-runtime', 'https://github.com/bytecodealliance/lucet', 'https://github.com/bytecodealliance/lucet/security/advisories/GHSA-hf79-8hjp-rrvq', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43790'} | null | {'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8'} | {'https://github.com/bytecodealliance/lucet/commit/7c7757c772fb709c61b1442bcc1e1fbee97bf4a8'} |
crates.io | GHSA-gx5w-rrhp-f436 | XSS in mdBook | > This is a cross-post of [the official security advisory][ml]. The official post contains a signed version with our PGP key, as well.
[ml]: https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0
The Rust Security Response Working Group was recently notified of a security issue affecting the search feature of mdBook, which could allow an attacker to execute arbitrary JavaScript code on the page.
The CVE for this vulnerability is [CVE-2020-26297](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26297).
## Overview
The search feature of mdBook (introduced in version 0.1.4) was affected by a cross site scripting vulnerability that allowed an attacker to execute arbitrary JavaScript code on an user's browser by tricking the user into typing a malicious search query, or tricking the user into clicking a link to the search page with the malicious search query prefilled.
mdBook 0.4.5 fixes the vulnerability by properly escaping the search query.
## Mitigations
Owners of websites built with mdBook have to upgrade to mdBook 0.4.5 or greater and rebuild their website contents with it. It's possible to install mdBook 0.4.5 on the local system with:
```
cargo install mdbook --version 0.4.5 --force
```
## Acknowledgements
Thanks to Kamil Vavra for responsibly disclosing the vulnerability to us according to [our security policy](https://www.rust-lang.org/policies/security).
## Timeline of events
All times are listed in UTC.
- 2020-12-30 20:14 - The issue is reported to the Rust Security Response WG
- 2020-12-30 20:32 - The issue is acknowledged and the investigation began
- 2020-12-30 21:21 - Found the cause of the vulnerability and prepared the patch
- 2021-01-04 15:00 - Patched version released and vulnerability disclosed | {'CVE-2020-26297'} | 2021-08-18T21:06:53Z | 2021-08-25T20:56:20Z | HIGH | null | {'CWE-79'} | {'https://github.com/rust-lang/mdBook/blob/master/CHANGELOG.md#mdbook-045', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26297', 'https://groups.google.com/g/rustlang-security-announcements/c/3-sO6of29O0', 'https://rustsec.org/advisories/RUSTSEC-2021-0001.html', 'https://github.com/rust-lang/mdBook', 'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b', 'https://github.com/rust-lang/mdBook/security/advisories/GHSA-gx5w-rrhp-f436'} | null | {'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b'} | {'https://github.com/rust-lang/mdBook/commit/32abeef088e98327ca0dfccdad92e84afa9d2e9b'} |
crates.io | GHSA-fqq2-xp7m-xvm8 | Data race in ruspiro-singleton | `Singleton<T>` is meant to be a static object that can be initialized lazily. In
order to satisfy the requirement that `static` items must implement `Sync`,
`Singleton` implemented both `Sync` and `Send` unconditionally.
This allows for a bug where non-`Sync` types such as `Cell` can be used in
singletons and cause data races in concurrent programs.
The flaw was corrected in commit `b0d2bd20e` by adding trait bounds, requiring
the contaiend type to implement `Sync`.
| {'CVE-2020-36435'} | 2021-08-24T17:45:32Z | 2021-08-25T20:58:19Z | HIGH | null | {'CWE-119', 'CWE-362'} | {'https://github.com/RusPiRo/ruspiro-singleton', 'https://rustsec.org/advisories/RUSTSEC-2020-0115.html', 'https://github.com/RusPiRo/ruspiro-singleton/pull/11', 'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36435', 'https://github.com/RusPiRo/ruspiro-singleton/issues/10'} | null | {'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e'} | {'https://github.com/RusPiRo/ruspiro-singleton/commit/b0d2bd20eb40b9cbc2958b981ba2dcd9e6f9396e'} |
crates.io | RUSTSEC-2020-0025 | bigint is unmaintained, use uint instead | The `bigint` crate is not maintained any more and contains several known bugs (including a soundness bug);
use [`uint`](https://crates.io/crates/uint) instead. | {'CVE-2020-35880'} | 2021-10-19T22:14:35Z | 2020-05-07T12:00:00Z | null | null | null | {'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42', 'https://rustsec.org/advisories/RUSTSEC-2020-0025.html', 'https://crates.io/crates/bigint'} | null | {'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42'} | {'https://github.com/paritytech/bigint/commit/7e71521a61b009afc94c91135353102658550d42'} |
crates.io | GHSA-f3pg-qwvg-p99c | Lenient Parsing of Content-Length Header When Prefixed with Plus Sign | ### Summary
hyper's HTTP/1 server code had a flaw that incorrectly parses and accepts requests with a `Content-Length` header with a prefixed plus sign, when it should have been rejected as illegal. This combined with an upstream HTTP proxy that doesn't parse such `Content-Length` headers, but forwards them, can result in "request smuggling" or "desync attacks".
### Vulnerability
The flaw exists in all prior versions of hyper, if built with [`rustc` v1.5.0 or newer](https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739).
Example:
```
GET / HTTP/1.1
Host: example.com
Content-Length: +3
abc
```
This request gets accepted and hyper reads the body as abc. The request _should_ be rejected, according to RFC 7230, since the ABNF for `Content-Length` only allows for `DIGIT`s. This is due to using the `FromStr` implementation for `u64` in the standard library. By differing from the spec, it is possible to send requests like these to endpoints that have different HTTP implementations, with different interpretations of the payload semantics, and cause "desync attacks".
In this particular case, an upstream proxy would need to error when parsing the `Content-Length`, but _not_ reject the request (swallowing its own error), and forwarding the request as-is with the `Content-Length` still included. _Then_ the upstream proxy and hyper would disagree on the length of the request body. The combination of these factors would be extremely rare.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### Impact
To determine if vulnerable, all these things must be true:
- **Using hyper as an HTTP server**. While the lenient decoder also exists in the client, a vulnerability does not exist around _responses_.
- **Using HTTP/1**. The HTTP/2 code uses a stricter parser.
- **Using a vulnerable HTTP proxy upstream to hyper**. If an upstream proxy correctly rejects the illegal `Content-Length` header, *OR* can parse the length with the plus sign, the desync attack cannot succeed.
### Patches
We have released the following patch versions:
- v0.14.10 (to be released when this advisor is published)
### Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests manually that contain a plus sign prefix in the `Content-Length` header.
- Ensure any upstream proxy handles `Content-Length` headers with a plus sign prefix.
### Credits
This issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson. | {'CVE-2021-32715'} | 2021-09-07T21:49:21Z | 2021-07-12T16:54:20Z | LOW | null | {'CWE-444'} | {'https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32715', 'https://rustsec.org/advisories/RUSTSEC-2021-0078.html', 'https://github.com/hyperium/hyper', 'https://github.com/hyperium/hyper/security/advisories/GHSA-f3pg-qwvg-p99c'} | null | {'https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739'} | {'https://github.com/rust-lang/rust/pull/28826/commits/123a83326fb95366e94a3be1a74775df4db97739'} |
crates.io | GHSA-rmff-f8w9-c9rm | Data races in max7301 | The `ImmediateIO` and `TransactionalIO` types implement `Sync` for all contained
`Expander<EI>` types regardless of if the `Expander` itself is safe to use
across threads.
As the `IO` types allow retrieving the `Expander`, this can lead to non-thread
safe types being sent across threads as part of the `Expander` leading to data
races.
| {'CVE-2020-36472'} | 2021-08-18T19:14:45Z | 2021-08-25T20:59:22Z | MODERATE | null | {'CWE-362'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-36472', 'https://github.com/edarc/max7301', 'https://github.com/edarc/max7301/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2020-0152.html', 'https://github.com/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52'} | null | {'https://github.com/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52'} | {'https://github.com/edarc/max7301/commit/0a1da873ddb29bca926bad8301f8d7ab8aa97c52'} |
crates.io | GHSA-hpcx-3pw8-g3j2 | Free of uninitialized memory in telemetry | An issue was discovered in the telemetry crate through 0.1.2 for Rust. There is a drop of uninitialized memory if a value.clone() call panics within misc::vec_with_size(). | {'CVE-2021-29937'} | 2021-08-19T17:09:26Z | 2021-08-25T20:54:22Z | CRITICAL | null | {'CWE-908'} | {'https://nvd.nist.gov/vuln/detail/CVE-2021-29937', 'https://github.com/Yoric/telemetry.rs/issues/45', 'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81', 'https://rustsec.org/advisories/RUSTSEC-2021-0046.html', 'https://github.com/Yoric/telemetry.rs'} | null | {'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81'} | {'https://github.com/Yoric/telemetry.rs/commit/2820cf12f2e08645fd6d1f15b4a90a54d6082a81'} |
crates.io | GHSA-g4w7-3qr8-5623 | Improper type usage in rusqlite | An issue was discovered in the rusqlite crate before 0.23.0 for Rust. Memory safety can be violated via the repr(Rust) type. | {'CVE-2020-35872'} | 2021-08-19T21:18:44Z | 2021-08-25T20:47:01Z | CRITICAL | null | {'CWE-351'} | {'https://nvd.nist.gov/vuln/detail/CVE-2020-35872', 'https://github.com/rusqlite/rusqlite/releases/tag/0.23.0', 'https://github.com/rusqlite/rusqlite', 'https://github.com/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0', 'https://rustsec.org/advisories/RUSTSEC-2020-0014.html'} | null | {'https://github.com/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0'} | {'https://github.com/rusqlite/rusqlite/commit/71b2f5187b0cbace3f8b6ff53432ff2ca0defcf0'} |
crates.io | GHSA-v4cp-h94r-m7xf | Use after free passing `externref`s to Wasm in Wasmtime | ### Impact
There was a use-after-free bug when passing `externref`s from the host to guest Wasm content.
To trigger the bug, you have to explicitly pass multiple `externref`s from the host to a Wasm instance at the same time, either by
* passing multiple `externref`s as arguments from host code to a Wasm function,
* or returning multiple `externref`s to Wasm from a multi-value return function defined in the host.
If you do not have host code that matches one of these shapes, then you are not impacted.
If Wasmtime's [`VMExternRefActivationsTable`](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/crates/runtime/src/externref.rs#L493) became filled to capacity after passing the first `externref` in, then passing in the second `externref` could trigger a garbage collection. However the first `externref` is not rooted until we pass control to Wasm, and therefore could be reclaimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control was passed to Wasm after the garbage collection, Wasm could use the first `externref`, which at this point has already been freed.
We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare.
### Patches
The bug has been fixed, and users should upgrade to Wasmtime 0.30.0.
Additionally, we have updated [our primary `externref` fuzz target](https://github.com/bytecodealliance/wasmtime/blob/37c094faf53f1b356aab3c79d451395e4f7edb34/fuzz/fuzz_targets/table_ops.rs) such that it better exercises these code paths and we can have greater confidence in their correctness going forward.
### Workarounds
If you cannot upgrade Wasmtime yet, you can avoid the bug by disabling reference types support in Wasmtime by passing `false` to [`wasmtime::Config::wasm_reference_types`](https://docs.rs/wasmtime/0.29.0/wasmtime/struct.Config.html#method.wasm_reference_types).
### References
* [The reference types Wasm proposal, which introduces `externref`](https://github.com/WebAssembly/reference-types/)
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the `bytecodealliance/wasmtime` repository](https://github.com/bytecodealliance/wasmtime/) | {'CVE-2021-39216'} | 2021-09-17T20:05:21Z | 2021-09-20T19:54:05Z | MODERATE | null | {'CWE-416'} | {'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAVBRYDDUIY2ZR3K3FO4BVYJKIMJ5TP7/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2Z33FTXFQ6EOINVEQIP4DFBG53G5XIY/', 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-v4cp-h94r-m7xf', 'https://github.com/bytecodealliance/wasmtime', 'https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3', 'https://crates.io/crates/wasmtime', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39216'} | null | {'https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3'} | {'https://github.com/bytecodealliance/wasmtime/commit/101998733b74624cbd348a2366d05760b40181f3'} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.