{"id":"CVE-2019-5419","aliases":["DEBIAN-CVE-2019-5419","DLA-1739-1","EUVD-2019-0386","GHSA-m63j-wh5w-c252","RHSA-2019:0796","RHSA-2019:1147","RHSA-2019:1149","RHSA-2019:1289","SUSE-SU-2019:0915-1","SUSE-SU-2019:1381-1","SUSE-SU-2019:1973-1","SUSE-SU-2020:3036-1","SUSE-SU-2020:3147-1","SUSE-SU-2020:3160-1","UBUNTU-CVE-2019-5419","openSUSE-SU-2019:1344-1","openSUSE-SU-2019:1527-1","openSUSE-SU-2019:1824-1","openSUSE-SU-2020:1993-1","openSUSE-SU-2020:2000-1","openSUSE-SU-2024:10589-1"],"status":"published","title":"Denial of Service Vulnerability in Action View","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.0844,"percentile":0.9504,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-400","CWE-770"],"published":"2019-03-13T17:25:55Z","modified":"2026-10-24T10:30:25Z","fixes":[{"ecosystem":"RubyGems","package":"actionview","fixed_in":["5.1.6.2","5.0.7.2","4.2.11.1","5.2.2.1","6.0.0.beta3"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:12","package":"rails","fixed_in":["2:5.2.2.1+dfsg-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"rails","fixed_in":["2:5.2.2.1+dfsg-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"rails","fixed_in":["2:5.2.2.1+dfsg-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"last_affected":"5.1.6.1"},{"fixed":"5.1.6.2"}]}]},{"source":"ghsa","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"last_affected":"5.0.7.1"},{"fixed":"5.0.7.2"}]}]},{"source":"ghsa","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"last_affected":"4.2.11.0"},{"fixed":"4.2.11.1"}]}]},{"source":"ghsa","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.2.0"},{"last_affected":"5.2.2.0"},{"fixed":"5.2.2.1"}]}]},{"source":"ghsa","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0.beta1"},{"fixed":"6.0.0.beta3"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"rails","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:5.2.2.1+dfsg-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"rails","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:5.2.2.1+dfsg-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"rails","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:5.2.2.1+dfsg-1"}]}]},{"source":"osv","ecosystem":"Debian:8","package":"rails","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:4.1.8-1+deb8u5"}]}],"versions":["2:4.1.8-1","2:4.1.8-1+deb8u1","2:4.1.8-1+deb8u2","2:4.1.8-1+deb8u3","2:4.1.8-1+deb8u4"],"bundled":2},{"source":"osv","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"4.2.11.1"}]}],"versions":["4.1.0","4.1.0.beta1","4.1.0.beta2","4.1.0.rc1","4.1.0.rc2","4.1.1","4.1.10","4.1.10.rc1","4.1.10.rc2","4.1.10.rc3","4.1.10.rc4","4.1.11","4.1.12","4.1.12.rc1","4.1.13","4.1.13.rc1","4.1.14","4.1.14.1","4.1.14.2","4.1.14.rc1","4.1.14.rc2","4.1.15","4.1.15.rc1","4.1.16","4.1.16.rc1","4.1.2","4.1.2.rc1","4.1.2.rc2","4.1.2.rc3","4.1.3","4.1.4","4.1.5","4.1.6","4.1.6.rc1","4.1.6.rc2","4.1.7","4.1.7.1","4.1.8","4.1.9","4.1.9.rc1","4.2.0","4.2.0.beta1","4.2.0.beta2","4.2.0.beta3","4.2.0.beta4","4.2.0.rc1","4.2.0.rc2","4.2.0.rc3","4.2.1","4.2.1.rc1","4.2.1.rc2","4.2.1.rc3","4.2.1.rc4","4.2.10","4.2.10.rc1","4.2.11","4.2.2","4.2.3","4.2.3.rc1","4.2.4","4.2.4.rc1","4.2.5","4.2.5.1","4.2.5.2","4.2.5.rc1","4.2.5.rc2","4.2.6","4.2.6.rc1","4.2.7","4.2.7.1","4.2.7.rc1","4.2.8","4.2.8.rc1","4.2.9","4.2.9.rc1","4.2.9.rc2"]},{"source":"osv","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.2.0"},{"fixed":"5.2.2.1"}]}],"versions":["5.2.0","5.2.1","5.2.1.1","5.2.1.rc1","5.2.2","5.2.2.rc1"]},{"source":"osv","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"fixed":"5.1.6.2"}]}],"versions":["5.1.0","5.1.1","5.1.2","5.1.2.rc1","5.1.3","5.1.3.rc1","5.1.3.rc2","5.1.3.rc3","5.1.4","5.1.4.rc1","5.1.5","5.1.5.rc1","5.1.6","5.1.6.1"]},{"source":"osv","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.0.7.2"}]}],"versions":["5.0.0","5.0.0.1","5.0.1","5.0.1.rc1","5.0.1.rc2","5.0.2","5.0.2.rc1","5.0.3","5.0.4","5.0.4.rc1","5.0.5","5.0.5.rc1","5.0.5.rc2","5.0.6","5.0.6.rc1","5.0.7","5.0.7.1"]},{"source":"osv","ecosystem":"RubyGems","package":"actionview","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0.beta1"},{"fixed":"6.0.0.beta3"}]}],"versions":["6.0.0.beta1","6.0.0.beta2"]},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"ansible-tower","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.4.3-1.el7at"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"ansible-tower-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.4.3-1.el7at"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"ansible-tower-setup","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.4.3-1.el7at"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"ansible-tower-ui","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.4.3-1.el7at"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"ansible-tower-venv-ansible","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.4.3-1.el7at"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"ansible-tower-venv-tower","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:3.4.3-1.el7at"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-amazon-smartstate","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-appliance","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-appliance-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-appliance-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-appliance-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-gemset","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.10::el7","package":"cfme-gemset-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.10.3.3-1.el7cf"}]}],"bundled":3},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"rh-ror50-rubygem-actionpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:5.0.1-2.el6"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"rh-ror50-rubygem-actionpack-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:5.0.1-2.el6"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"rh-ror50-rubygem-actionpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:5.0.1-2.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"rh-ror50-rubygem-actionpack-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:5.0.1-2.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"rh-ror42-rubygem-actionpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:4.2.6-5.el6"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"rh-ror42-rubygem-actionpack-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:4.2.6-5.el6"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"rh-ror42-rubygem-actionpack","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:4.2.6-5.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"rh-ror42-rubygem-actionpack-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:4.2.6-5.el7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-amazon-smartstate","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-appliance","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-appliance-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-appliance-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-appliance-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-gemset","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:cloudforms_managementengine:5.9::el7","package":"cfme-gemset-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:5.9.9.3-1.el7cf"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 7","package":"rubygem-actionpack-4_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.9-7.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud Crowbar 8","package":"rubygem-actionpack-4_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.9-7.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 4","package":"rubygem-actionpack-4_2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.9-7.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.4-3.17.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP1","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-3.3.3"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP1","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-3.3.3"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP2","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.3.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP2","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.3.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-ESPOS","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.34.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-LTSS","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.34.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15-LTSS","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.34.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.34.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP1","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.18.1"}]}],"bundled":16},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP1","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-3.18.1"}]}],"bundled":16},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"rails","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2:4.1.10-1","2:4.2.5-1","2:4.2.5.1-1","2:4.2.5.2-2","2:4.2.6-1","2:4.2.6-1ubuntu0.1~esm1","2:4.2.6-1ubuntu0.1~esm2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"rails","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2:4.2.9-2","2:4.2.9-4","2:4.2.10-0ubuntu4","2:4.2.10-0ubuntu4+esm1","2:4.2.10-0ubuntu4+esm2"]},{"source":"osv","ecosystem":"openSUSE:Leap 15.0","package":"rubygem-actionpack-5_1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.4-lp150.2.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.0","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.4-lp150.2.16.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-lp151.2.3.1"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-lp152.2.3.1"}]}],"bundled":16},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.5-lp151.2.18.2"}]}],"bundled":16},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"rmt-server","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.13-1.1"}]}],"bundled":16}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"fedoraproject","product":"fedora"},{"vendor":"opensuse","product":"leap"},{"vendor":"rails","product":"https://github.com/rails/rails"},{"vendor":"redhat","product":"cloudforms"},{"vendor":"redhat","product":"software_collections"},{"vendor":"rubyonrails","product":"rails"}],"references":[{"url":"http://www.openwall.com/lists/oss-security/2019/03/22/1","tags":["mailing-list","x_refsource_MLIST","x_transferred","Exploit","Mailing List","Mitigation","Patch","Third Party Advisory","fix","web"]},{"url":"https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/","tags":["x_refsource_CONFIRM","x_transferred","Patch","Third Party Advisory","fix"]},{"url":"https://groups.google.com/forum/#%21topic/rubyonrails-security/GN7w9fFAQeI","tags":["x_refsource_CONFIRM","x_transferred","web"]},{"url":"https://lists.debian.org/debian-lts-announce/2019/03/msg00042.html","tags":["mailing-list","x_refsource_MLIST","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://access.redhat.com/errata/RHSA-2019:0796","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory","web"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00011.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y43636TH4D6T46IC6N2RQVJTRFJAAYGA/","tags":["vendor-advisory","x_refsource_FEDORA","x_transferred","web"]},{"url":"https://access.redhat.com/errata/RHSA-2019:1149","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://access.redhat.com/errata/RHSA-2019:1147","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://access.redhat.com/errata/RHSA-2019:1289","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","Third Party Advisory","advisory","web"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00025.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00001.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-5419","tags":["advisory"]},{"url":"https://groups.google.com/forum/#!topic/rubyonrails-security/GN7w9fFAQeI","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y43636TH4D6T46IC6N2RQVJTRFJAAYGA/"},{"url":"https://github.com/rubysec/ruby-advisory-db/blob/master/gems/actionview/CVE-2019-5419.yml","tags":["web"]},{"url":"https://github.com/rails/rails/pull/35708","tags":["web"]},{"url":"https://github.com/rails/rails/commit/f4c70c2222180b8d9d924f00af0c7fd632e26715","tags":["web"]},{"url":"https://github.com/advisories/GHSA-m63j-wh5w-c252"},{"url":"https://security-tracker.debian.org/tracker/CVE-2019-5419","tags":["advisory"]},{"url":"https://github.com/rails/rails","tags":["package"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Y43636TH4D6T46IC6N2RQVJTRFJAAYGA","tags":["web"]},{"url":"https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released","tags":["web"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.7/html/release_notes","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1678385","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1680959","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1686045","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1686902","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1688937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1689159","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1689160","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693714","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693718","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693719","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693720","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693721","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693722","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693727","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693728","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693729","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693730","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693731","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693740","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693741","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693743","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693745","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693746","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693747","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693748","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693749","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693817","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1694190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1694798","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695626","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695627","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695629","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695631","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695897","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696362","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696419","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696421","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696422","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696456","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696841","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1698586","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_0796.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-3869","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1688508","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-3869","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-3869","tags":["advisory"]},{"url":"https://github.com/ansible/awx/pull/3505","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-5418","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-5418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-5418","tags":["advisory"]},{"url":"https://github.com/mpgn/CVE-2019-5418","tags":["article"]},{"url":"https://groups.google.com/forum/#!msg/rubyonrails-security/pFRKI96Sm8Q/IhpRq9D2CgAJ","tags":["article"]},{"url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-5419","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-5419","tags":["advisory","report"]},{"url":"https://groups.google.com/forum/#!msg/rubyonrails-security/GN7w9fFAQeI/0iQIiLP2CgAJ","tags":["article"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_1147.json","tags":["advisory"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_1149.json","tags":["advisory"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/release_notes","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1688871","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1695655","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1696363","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1704340","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_1289.json","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190915-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1129271","tags":["report"]},{"url":"https://bugzilla.suse.com/1129272","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5419","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20191381-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1107806","tags":["report"]},{"url":"https://bugzilla.suse.com/1117722","tags":["report"]},{"url":"https://bugzilla.suse.com/1118745","tags":["report"]},{"url":"https://bugzilla.suse.com/1125770","tags":["report"]},{"url":"https://bugzilla.suse.com/1128858","tags":["report"]},{"url":"https://bugzilla.suse.com/1129392","tags":["report"]},{"url":"https://bugzilla.suse.com/1132160","tags":["report"]},{"url":"https://bugzilla.suse.com/1132690","tags":["report"]},{"url":"https://bugzilla.suse.com/1134190","tags":["report"]},{"url":"https://bugzilla.suse.com/1134428","tags":["report"]},{"url":"https://bugzilla.suse.com/1135222","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11068","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20191973-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1136020","tags":["report"]},{"url":"https://bugzilla.suse.com/1136081","tags":["report"]},{"url":"https://bugzilla.suse.com/1138316","tags":["report"]},{"url":"https://bugzilla.suse.com/1140492","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20203036-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1165548","tags":["report"]},{"url":"https://bugzilla.suse.com/1168554","tags":["report"]},{"url":"https://bugzilla.suse.com/1172177","tags":["report"]},{"url":"https://bugzilla.suse.com/1172182","tags":["report"]},{"url":"https://bugzilla.suse.com/1172184","tags":["report"]},{"url":"https://bugzilla.suse.com/1172186","tags":["report"]},{"url":"https://bugzilla.suse.com/1173351","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-16770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-5247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-5249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-5267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8185","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20203147-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20203160-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2019-5419","tags":["report"]},{"url":"https://www.openwall.com/lists/oss-security/2019/03/13/4","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/FTKJM3ODEL4P7JHON6OYNBT5XQLAHCBS/#FTKJM3ODEL4P7JHON6OYNBT5XQLAHCBS","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/6IH56YOTZGFXNOIR75H2UYJCQOA2UAJA/#6IH56YOTZGFXNOIR75H2UYJCQOA2UAJA","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/NM2KMIISZ2FSHQKYLFT4WOLDJMPLTJJ7/#NM2KMIISZ2FSHQKYLFT4WOLDJMPLTJJ7","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/2W26GJJ7QXIADWB6ZCQWC2BUZD2ALYVT/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/7MCDUWQEXA3XGI7X2XPATA7YTNVDYTSF/","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-18904","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2019-5419","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","status":"published","published":"2019-03-27T13:43:19Z","modified":"2024-08-04T19:54:53.468Z","cwes":["CWE-400"],"updated_at":"2026-11-02T14:20:18.411291Z"}],"euvd":[{"id":"EUVD-2019-0386","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","status":"published","published":"2019-03-27T13:43:19Z","modified":"2024-08-04T19:54:53Z","updated_at":"2026-11-03T03:06:52.999682Z"}],"ghsa":[{"id":"GHSA-m63j-wh5w-c252","title":"Denial of Service Vulnerability in Action View","description":"# Denial of Service Vulnerability in Action View\n\nImpact \n------ \nSpecially crafted accept headers can cause the Action View template location code to consume 100% CPU, causing the server unable to process requests.  This impacts all Rails applications that render views. \n\nAll users running an affected release should either upgrade or use one of the workarounds immediately. \n\nReleases \n-------- \nThe 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations. \n\nWorkarounds \n----------- \nThis vulnerability can be mitigated by wrapping `render` calls with `respond_to` blocks.  For example, the following example is vulnerable: \n\n``` ruby\nclass UserController \u003c ApplicationController \n  def index \n    render \"index\" \n  end \nend \n``` \n\nBut the following code is not vulnerable: \n\n```ruby \nclass UserController \u003c ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n``` \n\nImplicit rendering is impacted, so this code is vulnerable: \n\n```ruby \nclass UserController \u003c ApplicationController \n  def index \n  end \nend \n``` \n\nBut can be changed this this: \n\n```ruby \nclass UserController \u003c ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n``` \n\nAlternatively to specifying the format, the following monkey patch can be applied in an initializer: \n\n``` \n$ cat config/initializers/formats_filter.rb \n# frozen_string_literal: true \n\nActionDispatch::Request.prepend(Module.new do \n  def formats \n    super().select do |format| \n      format.symbol || format.ref == \"*/*\" \n    end \n  end \nend) \n``` \n\nPlease note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x 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. \n\nAlso note that the patches for this vulnerability are the same as CVE-2019-5418. \n\nCredits \n------- \nThanks to John Hawthorn \u003cjohn@hawthorn.email\u003e of GitHub ","status":"published","published":"2019-03-13T17:25:55Z","modified":"2023-11-09T05:05:49Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:37:18.40412Z"}],"nvd":[{"id":"CVE-2019-5419","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","status":"published","published":"2019-03-27T14:29:01.657Z","modified":"2026-06-17T02:37:39.337Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":7.8,"vector":"AV:N/AC:L/Au:N/C:N/I:N/A:C","level":"high","assessor":"primary"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:05:09.523883Z"}],"osv":[{"id":"CVE-2019-5419","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","status":"published","published":"2019-03-27T14:29:01.657Z","modified":"2026-10-24T10:30:25.660524378Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:12.675558Z"},{"id":"DEBIAN-CVE-2019-5419","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","status":"published","published":"2019-03-27T14:29:01.657Z","modified":"2026-09-21T07:03:19.121259631Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:32.221385Z"},{"id":"GHSA-m63j-wh5w-c252","title":"Denial of Service Vulnerability in Action View","description":"# Denial of Service Vulnerability in Action View\n\nImpact \n------ \nSpecially crafted accept headers can cause the Action View template location code to consume 100% CPU, causing the server unable to process requests.  This impacts all Rails applications that render views. \n\nAll users running an affected release should either upgrade or use one of the workarounds immediately. \n\nReleases \n-------- \nThe 6.0.0.beta3, 5.2.2.1, 5.1.6.2, 5.0.7.2, and 4.2.11.1 releases are available at the normal locations. \n\nWorkarounds \n----------- \nThis vulnerability can be mitigated by wrapping `render` calls with `respond_to` blocks.  For example, the following example is vulnerable: \n\n``` ruby\nclass UserController \u003c ApplicationController \n  def index \n    render \"index\" \n  end \nend \n``` \n\nBut the following code is not vulnerable: \n\n```ruby \nclass UserController \u003c ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n``` \n\nImplicit rendering is impacted, so this code is vulnerable: \n\n```ruby \nclass UserController \u003c ApplicationController \n  def index \n  end \nend \n``` \n\nBut can be changed this this: \n\n```ruby \nclass UserController \u003c ApplicationController \n  def index \n    respond_to |format| \n      format.html { render \"index\" } \n    end \n  end \nend \n``` \n\nAlternatively to specifying the format, the following monkey patch can be applied in an initializer: \n\n``` \n$ cat config/initializers/formats_filter.rb \n# frozen_string_literal: true \n\nActionDispatch::Request.prepend(Module.new do \n  def formats \n    super().select do |format| \n      format.symbol || format.ref == \"*/*\" \n    end \n  end \nend) \n``` \n\nPlease note that only the 5.2.x, 5.1.x, 5.0.x, and 4.2.x 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. \n\nAlso note that the patches for this vulnerability are the same as CVE-2019-5418. \n\nCredits \n------- \nThanks to John Hawthorn \u003cjohn@hawthorn.email\u003e of GitHub ","status":"published","published":"2019-03-13T17:25:55Z","modified":"2024-02-16T08:18:12.796915Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T15:46:51.463834Z"},{"id":"RHSA-2019:0796","title":"Red Hat Security Advisory: CloudForms 4.7.3 security, bug fix and enhancement update","status":"published","published":"2024-09-13T14:07:54Z","modified":"2026-06-28T10:29:00Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:05.383061Z"},{"id":"RHSA-2019:1147","title":"Red Hat Security Advisory: rh-ror50-rubygem-actionpack security update","status":"published","published":"2024-09-13T14:08:07Z","modified":"2026-06-28T10:29:18Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:05.383061Z"},{"id":"RHSA-2019:1149","title":"Red Hat Security Advisory: rh-ror42-rubygem-actionpack security update","status":"published","published":"2024-09-13T14:07:58Z","modified":"2026-06-28T10:29:19Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:05.383061Z"},{"id":"RHSA-2019:1289","title":"Red Hat Security Advisory: CloudForms 4.6.9 security, bug fix and enhancement update","status":"published","published":"2024-09-13T14:10:05Z","modified":"2026-06-28T10:29:59Z","cvss":[{"version":"3.0","score":8.1,"vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:06.0195Z"},{"id":"UBUNTU-CVE-2019-5419","description":"There is a possible denial of service vulnerability in Action View (Rails) \u003c5.2.2.1, \u003c5.1.6.2, \u003c5.0.7.2, \u003c4.2.11.1 where specially crafted accept headers can cause action view to consume 100% cpu and make the server unresponsive.","status":"published","published":"2019-03-27T14:29:00Z","modified":"2025-09-08T16:45:15Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:21.741399Z"},{"id":"DLA-1739-1","title":"rails - security update","status":"published","published":"2019-03-30T00:00:00Z","modified":"2026-03-09T01:20:32.074198Z","updated_at":"2026-11-02T15:46:09.777694Z"},{"id":"openSUSE-SU-2019:1344-1","title":"Security update for rubygem-actionpack-5_1","description":"This update for rubygem-actionpack-5_1 fixes the following issues:\n\nSecurity issues fixed: \n\n- CVE-2019-5418: Fixed a file content disclosure vulnerability in Action View which\n  could be exploited via specially crafted accept headers in combination with calls\n  to render file (bsc#1129272).\n- CVE-2019-5419: Fixed a resource exhaustion issue in Action View which could make\n  the server unable to process requests (bsc#1129271).\n\nThis update was imported from the SUSE:SLE-15:Update update project.","status":"published","published":"2019-05-08T07:43:33Z","modified":"2026-02-04T02:41:06.709084Z","updated_at":"2026-11-02T16:58:30.784344Z"},{"id":"openSUSE-SU-2019:1527-1","title":"Security update for rmt-server","description":"This update for rmt-server to version 2.1.4 fixes the following issues:\n\n- Fix duplicate nginx location in rmt-server-pubcloud (bsc#1135222)\n- Mirror additional repos that were enabled during mirroring (bsc#1132690)\n- Make service IDs consistent across different RMT instances (bsc#1134428)\n- Make SMT data import scripts faster (bsc#1134190)\n- Fix incorrect triggering of registration sharing (bsc#1129392)\n- Fix license mirroring issue in some non-SUSE repositories (bsc#1128858)\n- Set CURLOPT_LOW_SPEED_LIMIT to prevent downloads from getting stuck (bsc#1107806)\n- Truncate the RMT lockfile when writing a new PID (bsc#1125770)\n- Fix missing trailing slashes on custom repository import from SMT (bsc#1118745)\n- Zypper authentication plugin (fate#326629)\n- Instance verification plugin in rmt-server-pubcloud (fate#326629)\n- Update dependencies to fix vulnerabilities in rails (CVE-2019-5419, bsc#1129271) and nokogiri (CVE-2019-11068, bsc#1132160)\n- Allow RMT registration to work under HTTP as well as HTTPS.\n- Offline migration from SLE 15 to SLE 15 SP1 will add Python2 module \n- Online migrations will automatically add additional modules to the client systems depending on the base product\n- Supply log severity to journald\n- Breaking Change: Added headers to generated CSV files\n\nThis update was imported from the SUSE:SLE-15:Update update project.","status":"published","published":"2019-06-07T15:13:07Z","modified":"2026-02-04T04:13:43.970671Z","updated_at":"2026-11-02T16:58:30.784344Z"},{"id":"openSUSE-SU-2019:1824-1","title":"Security update for rmt-server","description":"This update for rmt-server to version 2.3.1 fixes the following issues:\n\n- Fix mirroring logic when errors are encountered (bsc#1140492)\n- Refactor RMT::Mirror to download metadata/licenses in parallel\n- Check repo metadata GPG signatures during mirroring (bsc#1132690)\n- Add rmt-server-config subpackage with nginx configs (fate#327816, bsc#1136081)\n- Fix dependency to removed boot_cli_i18n file (bsc#1136020) \n- Add `rmt-cli systems list` command to list registered systems\n- Fix create UUID when system_uuid file empty (bsc#1138316)\n- Fix duplicate nginx location in rmt-server-pubcloud (bsc#1135222)\n- Mirror additional repos that were enabled during mirroring (bsc#1132690)\n- Make service IDs consistent across different RMT instances (bsc#1134428)\n- Make SMT data import scripts faster (bsc#1134190)\n- Fix incorrect triggering of registration sharing (bsc#1129392)\n- Fix license mirroring issue in some non-SUSE repositories (bsc#1128858)\n- Update dependencies to fix vulnerabilities in rails (CVE-2019-5419, bsc#1129271) and nokogiri (CVE-2019-11068, bsc#1132160)\n- Allow RMT registration to work under HTTP as well as HTTPS.\n- Offline migration from SLE 15 to SLE 15 SP1 will add Python2 module \n- Online migrations will automatically add additional modules to the client systems depending on the base product\n- Supply log severity to journald\n- Breaking Change: Added headers to generated CSV files\n\nThis update was imported from the SUSE:SLE-15-SP1:Update update project.","status":"published","published":"2019-08-01T15:21:22Z","modified":"2026-02-04T02:18:10.977939Z","updated_at":"2026-11-02T16:58:30.784344Z"},{"id":"openSUSE-SU-2020:1993-1","title":"Security update for rmt-server","description":"This update for rmt-server fixes the following issues:\n\nUpdate to version 2.6.5:\n- Solved potential bug of SCC repository URLs changing over time. RMT\n  now self heals by removing the previous invalid repository and\n  creating the correct one.\n- Add web server settings to /etc/rmt.conf:\n  Now it's possible to configure the minimum and maximum threads count as well\n  the number of web server workers to be booted through /etc/rmt.conf.\n- Instead of using an MD5 of URLs for custom repository friendly_ids,\n  RMT now builds an ID from the name.\n- Fix RMT file caching based on timestamps:\n  Previously, RMT sent GET requests with the header 'If-Modified-Since' to a\n  repository server and if the response had a 304 (Not Modified), it would copy\n  a file from the local cache instead of downloading. However, if the local file\n  timestamp accidentally changed to a date newer than the one on the repository\n  server, RMT would have an outdated file, which caused some errors.\n  Now, RMT makes HEAD requests to the repositories servers and inspect the\n  'Last-Modified' header to decide whether to download a file or copy it from\n  cache, by comparing the equalness of timestamps.\n- Fixed an issue where relative paths supplied to `rmt-cli import repos`\n  caused the command to fail.\n- Friendlier IDs for custom repositories:\n  In an effort to simplify the handling of SCC and custom repositories,\n  RMT now has friendly IDs. For SCC repositories, it's the same SCC ID\n  as before. For custom repositories, it can either be user provided\n  or RMT generated (MD5 of the provided URL).\n  Benefits:\n  * `rmt-cli mirror repositories` now works for custom repositories.\n  * Custom repository IDs can be the same across RMT instances.\n  * No more confusing 'SCC ID' vs 'ID' in `rmt-cli` output.\n  Deprecation Warnings:\n  * RMT now uses a different ID for custom repositories than before.\n    RMT still supports that old ID, but it's recommended to start\n    using the new ID to ensure future compatibility.\n- Updated rails and puma dependencies for security fixes.\n\nThis update was imported from the SUSE:SLE-15-SP2:Update update project.","status":"published","published":"2020-11-21T11:23:05Z","modified":"2026-02-04T04:06:02.22454Z","updated_at":"2026-11-02T16:58:31.517538Z"},{"id":"openSUSE-SU-2020:2000-1","title":"Security update for rmt-server","description":"This update for rmt-server fixes the following issues:\n\n- Version 2.6.5\n- Solved potential bug of SCC repository URLs changing over time. RMT\n  now self heals by removing the previous invalid repository and\n  creating the correct one.\n\n- Version 2.6.4\n- Add web server settings to /etc/rmt.conf:\n  Now it's possible to configure the minimum and maximum threads count as well\n  the number of web server workers to be booted through /etc/rmt.conf.\n\n- Version 2.6.3\n- Instead of using an MD5 of URLs for custom repository friendly_ids,\n  RMT now builds an ID from the name.\n\n- Version 2.6.2\n- Fix RMT file caching based on timestamps:\n  Previously, RMT sent GET requests with the header 'If-Modified-Since' to a\n  repository server and if the response had a 304 (Not Modified), it would copy\n  a file from the local cache instead of downloading. However, if the local file\n  timestamp accidentally changed to a date newer than the one on the repository\n  server, RMT would have an outdated file, which caused some errors.\n  Now, RMT makes HEAD requests to the repositories servers and inspect the\n  'Last-Modified' header to decide whether to download a file or copy it from\n  cache, by comparing the equalness of timestamps.\n  \n\n- Version 2.6.1\n- Fixed an issue where relative paths supplied to `rmt-cli import repos`\n  caused the command to fail.\n\n- Version 2.6.0\n- Friendlier IDs for custom repositories:\n  In an effort to simplify the handling of SCC and custom repositories,\n  RMT now has friendly IDs. For SCC repositories, it's the same SCC ID\n  as before. For custom repositories, it can either be user provided\n  or RMT generated (MD5 of the provided URL).\n  Benefits:\n  * `rmt-cli mirror repositories` now works for custom repositories.\n  * Custom repository IDs can be the same across RMT instances.\n  * No more confusing 'SCC ID' vs 'ID' in `rmt-cli` output.\n  Deprecation Warnings:\n  * RMT now uses a different ID for custom repositories than before.\n    RMT still supports that old ID, but it's recommended to start\n    using the new ID to ensure future compatibility.\n\n- Version 2.5.20\n- Updated rails from 6.0.3.2 to 6.0.3.3:\n  - actionview (CVE-2020-15169)\n\n- Version 2.5.19\n- RMT now has the ability to remove local systems with the command\n  `rmt-cli systems remove`.\n\n- Version 2.5.18\n- Fixed exit code for `rmt-cli mirror` and its subcommands. Now it exits with 1\n  whenever an error occurs during mirroring\n- Improved message logging for `rtm-cli mirror`. Instead of logging an error\n  when it occurs, the command summarize all errors at the end of execution. Now\n  log messages have colors to better identify failure/success.\n\n- Version 2.5.17\n- RMT no longer provides the installer updates repository to systems via its\n  zypper service. This repository is used during the installation process, as\n  it provides an up-to-date installation experience, but it has no use on an\n  already installed system.\n\n- Version 2.5.16\n- Updated RMT's rails and puma dependencies.\n  - puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247\n    CVE-2019-16770)\n  - actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)\n  - actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)\n  - activesupport (CVE-2020-8165)\n  - railties (CVE-2019-5420)\n\n- Version 2.5.15\n- RMT now checks if repositories are fully mirrored during the\n  activation process. Previously, RMT only checked if the repositories\n  were enabled to be mirrored, but not that they were actually mirrored.\n  In this case, RMTs were not able to provide the repository data which\n  systems assumed it had.\n\n- Version 2.5.14\n- Enable 'Installer-Updates' repositories by default\n\n- Fixed deprecation warning when thor encountered an error. Also,\n  instead of returning 0 for thor errors, rmt-cli will return 1\n  instead.\n\n- Version 2.5.13\n- Added `rmt-cli repos clean` command to remove locally mirrored files\n  of repositories which are not marked to be mirrored.\n- Previously, RMT didn't track deduplicated files in its database. Now,\n  to accommodate `rmt-cli repos clean`, RMT will track all mirrored\n  files.\n\n- Move the nginx reload to the configuration package which contain\n  nginx config files, don't reload nginx unconditionally from main\n  package.\n\n- Version 2.5.12\n- Update rack to version 2.2.3 (CVE-2020-8184: bsc#1173351)\n- Update Rails to version 5.2.4.3:\n  - actionpack (CVE-2020-8164: bsc#1172177)\n  - actionpack (CVE-2020-8166: bsc#1172182)\n  - activesupport (CVE-2020-8165: bsc#1172186)\n  - actionview (CVE-2020-8167: bsc#1172184)\n\n- Version 2.5.11\n- rmt-server-pubcloud:\n  - SLES11 EOL\n  - Extension activation verification based on the available subscriptions\n  - Added a manual instance verification script\n\n- Version 2.5.10\n- Support rmt-server to run with Ruby 2.7 (Factory/Tumbleweed):\n  - Bump gem 'config' version from 1.7.2 to 2.2.1 to fix incompatibility Ruby\n    2.7 OpenStruct class;\n  - Bump gem 'typhoeus' version from 1.3.1 to 1.4.0 in order to also bump gem\n    'ethon' version, which caused a 'rb_safe_level' warning on Ruby 2.7;\n  - Fix 'last arg as keyword arg' Ruby 2.7 warning on source code;\n  - Disable 'deprecated' warnings from Ruby 2.7; Rails 5.1 generates a lot of\n    warnings with Ruby 2.7, mainly due to 'capturing the given block with\n    Proc.new', which is deprecated;\n  - Improve RPM spec to consider only the distribution default Ruby version\n    configured in OBS;\n  - Improve RPM spec to remove Ruby 2.7 warnings regarding 'bundler.\n\n- Move nginx/vhosts.d directory to correct sub-package. They\n  are needed together with nginx, not rmt-server.\n- Fix dependencies especially for containerized usage:\n  - mariadb and nginx are not hard requires, could run on another host\n- Fix generic dependencies:\n  - systemd ordering was missing\n  - shadow is required for pre-install\n\n- Version 2.5.9\n- rmt-server-pubcloud: enforce strict authentication\n\n- Version 2.5.8\n- Use repomd_parser gem to remove repository metadata parsing code.\n\nThis update was imported from the SUSE:SLE-15-SP1:Update update project.","status":"published","published":"2020-11-23T09:30:24Z","modified":"2026-02-04T02:41:28.780194Z","updated_at":"2026-11-02T16:58:31.517538Z"},{"id":"openSUSE-SU-2024:10589-1","title":"rmt-server-2.6.13-1.1 on GA media","description":"These are all security issues fixed in the rmt-server-2.6.13-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:28:48.695963Z","updated_at":"2026-11-02T16:58:34.487567Z"},{"id":"SUSE-SU-2019:0915-1","title":"Security update for rubygem-actionpack-4_2","description":"This update for rubygem-actionpack-4_2 fixes the following issues:\n\nSecurity issues fixed: \t  \n\n- CVE-2019-5418: Fixed a file content disclosure vulnerability in Action View which \n  could be exploited via specially crafted accept headers in combination with calls \n  to render file (bsc#1129272).\n- CVE-2019-5419: Fixed a resource exhaustion issue in Action View which could make\n  the server unable to process requests (bsc#1129271). \n","status":"published","published":"2019-04-09T09:21:14Z","modified":"2026-02-04T03:37:36.533631Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:1381-1","title":"Security update for rmt-server","description":"This update for rmt-server to version 2.1.4 fixes the following issues:\n\n- Fix duplicate nginx location in rmt-server-pubcloud (bsc#1135222)\n- Mirror additional repos that were enabled during mirroring (bsc#1132690)\n- Make service IDs consistent across different RMT instances (bsc#1134428)\n- Make SMT data import scripts faster (bsc#1134190)\n- Fix incorrect triggering of registration sharing (bsc#1129392)\n- Fix license mirroring issue in some non-SUSE repositories (bsc#1128858)\n- Set CURLOPT_LOW_SPEED_LIMIT to prevent downloads from getting stuck (bsc#1107806)\n- Truncate the RMT lockfile when writing a new PID (bsc#1125770)\n- Fix missing trailing slashes on custom repository import from SMT (bsc#1118745)\n- Zypper authentication plugin (fate#326629)\n- Instance verification plugin in rmt-server-pubcloud (fate#326629)\n- Update dependencies to fix vulnerabilities in rails (CVE-2019-5419, bsc#1129271) and nokogiri (CVE-2019-11068, bsc#1132160)\n- Allow RMT registration to work under HTTP as well as HTTPS.\n- Offline migration from SLE 15 to SLE 15 SP1 will add Python2 module \n- Online migrations will automatically add additional modules to the client systems depending on the base product\n- Supply log severity to journald\n- Breaking Change: Added headers to generated CSV files\n","status":"published","published":"2019-05-30T06:11:02Z","modified":"2026-02-04T02:24:47.04631Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:1973-1","title":"Security update for rmt-server","description":"This update for rmt-server to version 2.3.1 fixes the following issues:\n\n- Fix mirroring logic when errors are encountered (bsc#1140492)\n- Refactor RMT::Mirror to download metadata/licenses in parallel\n- Check repo metadata GPG signatures during mirroring (bsc#1132690)\n- Add rmt-server-config subpackage with nginx configs (fate#327816, bsc#1136081)\n- Fix dependency to removed boot_cli_i18n file (bsc#1136020) \n- Add `rmt-cli systems list` command to list registered systems\n- Fix create UUID when system_uuid file empty (bsc#1138316)\n- Fix duplicate nginx location in rmt-server-pubcloud (bsc#1135222)\n- Mirror additional repos that were enabled during mirroring (bsc#1132690)\n- Make service IDs consistent across different RMT instances (bsc#1134428)\n- Make SMT data import scripts faster (bsc#1134190)\n- Fix incorrect triggering of registration sharing (bsc#1129392)\n- Fix license mirroring issue in some non-SUSE repositories (bsc#1128858)\n- Update dependencies to fix vulnerabilities in rails (CVE-2019-5419, bsc#1129271) and nokogiri (CVE-2019-11068, bsc#1132160)\n- Allow RMT registration to work under HTTP as well as HTTPS.\n- Offline migration from SLE 15 to SLE 15 SP1 will add Python2 module \n- Online migrations will automatically add additional modules to the client systems depending on the base product\n- Supply log severity to journald\n- Breaking Change: Added headers to generated CSV files\n","status":"published","published":"2019-07-25T14:54:53Z","modified":"2026-02-04T03:13:00.246322Z","updated_at":"2026-11-02T15:53:46.44301Z"},{"id":"SUSE-SU-2020:3036-1","title":"Security update for rmt-server","description":"This update for rmt-server fixes the following issues:\n\nUpdate to version 2.6.5:\n- Solved potential bug of SCC repository URLs changing over time. RMT\n  now self heals by removing the previous invalid repository and\n  creating the correct one.\n- Add web server settings to /etc/rmt.conf:\n  Now it's possible to configure the minimum and maximum threads count as well\n  the number of web server workers to be booted through /etc/rmt.conf.\n- Instead of using an MD5 of URLs for custom repository friendly_ids,\n  RMT now builds an ID from the name.\n- Fix RMT file caching based on timestamps:\n  Previously, RMT sent GET requests with the header 'If-Modified-Since' to a\n  repository server and if the response had a 304 (Not Modified), it would copy\n  a file from the local cache instead of downloading. However, if the local file\n  timestamp accidentally changed to a date newer than the one on the repository\n  server, RMT would have an outdated file, which caused some errors.\n  Now, RMT makes HEAD requests to the repositories servers and inspect the\n  'Last-Modified' header to decide whether to download a file or copy it from\n  cache, by comparing the equalness of timestamps.\n- Fixed an issue where relative paths supplied to `rmt-cli import repos`\n  caused the command to fail.\n- Friendlier IDs for custom repositories:\n  In an effort to simplify the handling of SCC and custom repositories,\n  RMT now has friendly IDs. For SCC repositories, it's the same SCC ID\n  as before. For custom repositories, it can either be user provided\n  or RMT generated (MD5 of the provided URL).\n  Benefits:\n  * `rmt-cli mirror repositories` now works for custom repositories.\n  * Custom repository IDs can be the same across RMT instances.\n  * No more confusing 'SCC ID' vs 'ID' in `rmt-cli` output.\n  Deprecation Warnings:\n  * RMT now uses a different ID for custom repositories than before.\n    RMT still supports that old ID, but it's recommended to start\n    using the new ID to ensure future compatibility.\n- Updated rails and puma dependencies for security fixes.\n","status":"published","published":"2020-10-26T11:11:15Z","modified":"2026-02-04T02:46:56.057405Z","updated_at":"2026-11-02T15:53:48.11786Z"},{"id":"SUSE-SU-2020:3147-1","title":"Security update for rmt-server","description":"This update for rmt-server fixes the following issues:\n\n- Version 2.6.5\n- Solved potential bug of SCC repository URLs changing over time. RMT\n  now self heals by removing the previous invalid repository and\n  creating the correct one.\n\n- Version 2.6.4\n- Add web server settings to /etc/rmt.conf:\n  Now it's possible to configure the minimum and maximum threads count as well\n  the number of web server workers to be booted through /etc/rmt.conf.\n\n- Version 2.6.3\n- Instead of using an MD5 of URLs for custom repository friendly_ids,\n  RMT now builds an ID from the name.\n\n- Version 2.6.2\n- Fix RMT file caching based on timestamps:\n  Previously, RMT sent GET requests with the header 'If-Modified-Since' to a\n  repository server and if the response had a 304 (Not Modified), it would copy\n  a file from the local cache instead of downloading. However, if the local file\n  timestamp accidentally changed to a date newer than the one on the repository\n  server, RMT would have an outdated file, which caused some errors.\n  Now, RMT makes HEAD requests to the repositories servers and inspect the\n  'Last-Modified' header to decide whether to download a file or copy it from\n  cache, by comparing the equalness of timestamps.\n  \n\n- Version 2.6.1\n- Fixed an issue where relative paths supplied to `rmt-cli import repos`\n  caused the command to fail.\n\n- Version 2.6.0\n- Friendlier IDs for custom repositories:\n  In an effort to simplify the handling of SCC and custom repositories,\n  RMT now has friendly IDs. For SCC repositories, it's the same SCC ID\n  as before. For custom repositories, it can either be user provided\n  or RMT generated (MD5 of the provided URL).\n  Benefits:\n  * `rmt-cli mirror repositories` now works for custom repositories.\n  * Custom repository IDs can be the same across RMT instances.\n  * No more confusing 'SCC ID' vs 'ID' in `rmt-cli` output.\n  Deprecation Warnings:\n  * RMT now uses a different ID for custom repositories than before.\n    RMT still supports that old ID, but it's recommended to start\n    using the new ID to ensure future compatibility.\n\n- Version 2.5.20\n- Updated rails from 6.0.3.2 to 6.0.3.3:\n  - actionview (CVE-2020-15169)\n\n- Version 2.5.19\n- RMT now has the ability to remove local systems with the command\n  `rmt-cli systems remove`.\n\n- Version 2.5.18\n- Fixed exit code for `rmt-cli mirror` and its subcommands. Now it exits with 1\n  whenever an error occurrs during mirroring\n- Improved message logging for `rtm-cli mirror`. Instead of logging an error\n  when it occurs, the command summarize all errors at the end of execution. Now\n  log messages have colors to better identify failure/success.\n\n- Version 2.5.17\n- RMT no longer provides the installer updates repository to systems via its\n  zypper service. This repository is used during the installation process, as\n  it provides an up-to-date installation experience, but it has no use on an\n  already installed system.\n\n- Version 2.5.16\n- Updated RMT's rails and puma dependencies.\n  - puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247\n    CVE-2019-16770)\n  - actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)\n  - actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)\n  - activesupport (CVE-2020-8165)\n  - railties (CVE-2019-5420)\n\n- Version 2.5.15\n- RMT now checks if repositories are fully mirrored during the\n  activation process. Previously, RMT only checked if the repositories\n  were enabled to be mirrored, but not that they were actually mirrored.\n  In this case, RMTs were not able to provide the repository data which\n  systems assumed it had.\n\n- Version 2.5.14\n- Enable 'Installer-Updates' repositories by default\n\n- Fixed deprecation warning when thor encountered an error. Also,\n  instead of returning 0 for thor errors, rmt-cli will return 1\n  instead.\n\n- Version 2.5.13\n- Added `rmt-cli repos clean` command to remove locally mirrored files\n  of repositories which are not marked to be mirrored.\n- Previously, RMT didn't track deduplicated files in its database. Now,\n  to accommodate `rmt-cli repos clean`, RMT will track all mirrored\n  files.\n\n- Move the nginx reload to the configuration package which contain\n  nginx config files, don't reload nginx unconditionally from main\n  package.\n\n- Version 2.5.12\n- Update rack to version 2.2.3 (CVE-2020-8184: bsc#1173351)\n- Update Rails to version 5.2.4.3:\n  - actionpack (CVE-2020-8164: bsc#1172177)\n  - actionpack (CVE-2020-8166: bsc#1172182)\n  - activesupport (CVE-2020-8165: bsc#1172186)\n  - actionview (CVE-2020-8167: bsc#1172184)\n\n- Version 2.5.11\n- rmt-server-pubcloud:\n  - SLES11 EOL\n  - Extension activation verification based on the available subscriptions\n  - Added a manual instance verification script\n\n- Version 2.5.10\n- Support rmt-server to run with Ruby 2.7 (Factory/Tumbleweed):\n  - Bump gem 'config' version from 1.7.2 to 2.2.1 to fix incompatibility Ruby\n    2.7 OpenStruct class;\n  - Bump gem 'typhoeus' version from 1.3.1 to 1.4.0 in order to also bump gem\n    'ethon' version, which caused a 'rb_safe_level' warning on Ruby 2.7;\n  - Fix 'last arg as keyword arg' Ruby 2.7 warning on source code;\n  - Disable 'deprecated' warnings from Ruby 2.7; Rails 5.1 generates a lot of\n    warnings with Ruby 2.7, mainly due to 'capturing the given block with\n    Proc.new', which is deprecated;\n  - Improve RPM spec to consider only the distribution default Ruby version\n    configured in OBS;\n  - Improve RPM spec to remove Ruby 2.7 warnings regarding 'bundler.\n\n- Move nginx/vhosts.d directory to correct sub-package. They\n  are needed together with nginx, not rmt-server.\n- Fix dependencies especially for containerized usage:\n  - mariadb and nginx are not hard requires, could run on another host\n- Fix generic dependencies:\n  - systemd ordering was missing\n  - shadow is required for pre-install\n\n- Version 2.5.9\n- rmt-server-pubcloud: enforce strict authentication\n\n- Version 2.5.8\n- Use repomd_parser gem to remove repository metadata parsing code.\n","status":"published","published":"2020-11-04T10:02:46Z","modified":"2026-02-04T02:41:44.175135Z","updated_at":"2026-11-02T15:53:48.11786Z"},{"id":"SUSE-SU-2020:3160-1","title":"Security update for rmt-server","description":"This update for rmt-server fixes the following issues:\n\n- Version 2.6.5\n- Solved potential bug of SCC repository URLs changing over time. RMT\n  now self heals by removing the previous invalid repository and\n  creating the correct one.\n\n- Version 2.6.4\n- Add web server settings to /etc/rmt.conf:\n  Now it's possible to configure the minimum and maximum threads count as well\n  the number of web server workers to be booted through /etc/rmt.conf.\n\n- Version 2.6.3\n- Instead of using an MD5 of URLs for custom repository friendly_ids,\n  RMT now builds an ID from the name.\n\n- Version 2.6.2\n- Fix RMT file caching based on timestamps:\n  Previously, RMT sent GET requests with the header 'If-Modified-Since' to a\n  repository server and if the response had a 304 (Not Modified), it would copy\n  a file from the local cache instead of downloading. However, if the local file\n  timestamp accidentally changed to a date newer than the one on the repository\n  server, RMT would have an outdated file, which caused some errors.\n  Now, RMT makes HEAD requests to the repositories servers and inspect the\n  'Last-Modified' header to decide whether to download a file or copy it from\n  cache, by comparing the equalness of timestamps.\n  \n\n- Version 2.6.1\n- Fixed an issue where relative paths supplied to `rmt-cli import repos`\n  caused the command to fail.\n\n- Version 2.6.0\n- Friendlier IDs for custom repositories:\n  In an effort to simplify the handling of SCC and custom repositories,\n  RMT now has friendly IDs. For SCC repositories, it's the same SCC ID\n  as before. For custom repositories, it can either be user provided\n  or RMT generated (MD5 of the provided URL).\n  Benefits:\n  * `rmt-cli mirror repositories` now works for custom repositories.\n  * Custom repository IDs can be the same across RMT instances.\n  * No more confusing 'SCC ID' vs 'ID' in `rmt-cli` output.\n  Deprecation Warnings:\n  * RMT now uses a different ID for custom repositories than before.\n    RMT still supports that old ID, but it's recommended to start\n    using the new ID to ensure future compatibility.\n\n- Version 2.5.20\n- Updated rails from 6.0.3.2 to 6.0.3.3:\n  - actionview (CVE-2020-15169)\n\n- Version 2.5.19\n- RMT now has the ability to remove local systems with the command\n  `rmt-cli systems remove`.\n\n- Version 2.5.18\n- Fixed exit code for `rmt-cli mirror` and its subcommands. Now it exits with 1\n  whenever an error occurs during mirroring\n- Improved message logging for `rtm-cli mirror`. Instead of logging an error\n  when it occurs, the command summarize all errors at the end of execution. Now\n  log messages have colors to better identify failure/success.\n\n- Version 2.5.17\n- RMT no longer provides the installer updates repository to systems via its\n  zypper service. This repository is used during the installation process, as\n  it provides an up-to-date installation experience, but it has no use on an\n  already installed system.\n\n- Version 2.5.16\n- Updated RMT's rails and puma dependencies.\n  - puma (CVE-2020-11076, CVE-2020-11077, CVE-2020-5249, CVE-2020-5247\n    CVE-2019-16770)\n  - actionpack (CVE-2020-8185, CVE-2020-8164, CVE-2020-8166)\n  - actionview (CVE-2020-8167, CVE-2020-5267, CVE-2019-5418, CVE-2019-5419)\n  - activesupport (CVE-2020-8165)\n  - railties (CVE-2019-5420)\n\n- Version 2.5.15\n- RMT now checks if repositories are fully mirrored during the\n  activation process. Previously, RMT only checked if the repositories\n  were enabled to be mirrored, but not that they were actually mirrored.\n  In this case, RMTs were not able to provide the repository data which\n  systems assumed it had.\n\n- Version 2.5.14\n- Enable 'Installer-Updates' repositories by default\n\n- Fixed deprecation warning when thor encountered an error. Also,\n  instead of returning 0 for thor errors, rmt-cli will return 1\n  instead.\n\n- Version 2.5.13\n- Added `rmt-cli repos clean` command to remove locally mirrored files\n  of repositories which are not marked to be mirrored.\n- Previously, RMT didn't track deduplicated files in its database. Now,\n  to accommodate `rmt-cli repos clean`, RMT will track all mirrored\n  files.\n\n- Move the nginx reload to the configuration package which contain\n  nginx config files, don't reload nginx unconditionally from main\n  package.\n\n- Version 2.5.12\n- Update rack to version 2.2.3 (CVE-2020-8184: bsc#1173351)\n- Update Rails to version 5.2.4.3:\n  - actionpack (CVE-2020-8164: bsc#1172177)\n  - actionpack (CVE-2020-8166: bsc#1172182)\n  - activesupport (CVE-2020-8165: bsc#1172186)\n  - actionview (CVE-2020-8167: bsc#1172184)\n\n- Version 2.5.11\n- rmt-server-pubcloud:\n  - SLES11 EOL\n  - Extension activation verification based on the available subscriptions\n  - Added a manual instance verification script\n\n- Version 2.5.10\n- Support rmt-server to run with Ruby 2.7 (Factory/Tumbleweed):\n  - Bump gem 'config' version from 1.7.2 to 2.2.1 to fix incompatibility Ruby\n    2.7 OpenStruct class;\n  - Bump gem 'typhoeus' version from 1.3.1 to 1.4.0 in order to also bump gem\n    'ethon' version, which caused a 'rb_safe_level' warning on Ruby 2.7;\n  - Fix 'last arg as keyword arg' Ruby 2.7 warning on source code;\n  - Disable 'deprecated' warnings from Ruby 2.7; Rails 5.1 generates a lot of\n    warnings with Ruby 2.7, mainly due to 'capturing the given block with\n    Proc.new', which is deprecated;\n  - Improve RPM spec to consider only the distribution default Ruby version\n    configured in OBS;\n  - Improve RPM spec to remove Ruby 2.7 warnings regarding 'bundler.\n\n- Move nginx/vhosts.d directory to correct sub-package. They\n  are needed together with nginx, not rmt-server.\n- Fix dependencies especially for containerized usage:\n  - mariadb and nginx are not hard requires, could run on another host\n- Fix generic dependencies:\n  - systemd ordering was missing\n  - shadow is required for pre-install\n\n- Version 2.5.9\n- rmt-server-pubcloud: enforce strict authentication\n\n- Version 2.5.8\n- Use repomd_parser gem to remove repository metadata parsing code.\n","status":"published","published":"2020-11-05T09:33:25Z","modified":"2026-02-04T04:11:11.152927Z","updated_at":"2026-11-02T15:53:48.11786Z"}]}}