File _patchinfo of Package patchinfo.16827

Overview Repositories Revisions Requests Users Attributes Meta

File _patchinfo of Package patchinfo.16827

<patchinfo incident="16827">
  <issue tracker="cve" id="2020-5249"/>
  <issue tracker="cve" id="2020-8185"/>
  <issue tracker="cve" id="2020-8167"/>
  <issue tracker="cve" id="2020-11077"/>
  <issue tracker="cve" id="2020-5247"/>
  <issue tracker="cve" id="2019-16770"/>
  <issue tracker="cve" id="2019-5419"/>
  <issue tracker="cve" id="2019-5420"/>
  <issue tracker="cve" id="2020-15169"/>
  <issue tracker="cve" id="2020-8164"/>
  <issue tracker="cve" id="2020-8184"/>
  <issue tracker="cve" id="2020-11076"/>
  <issue tracker="cve" id="2020-8166"/>
  <issue tracker="cve" id="2020-8165"/>
  <issue tracker="cve" id="2019-5418"/>
  <issue tracker="cve" id="2020-5267"/>
  <issue tracker="bnc" id="1172184">VUL-0: CVE-2020-8167: rubygem-actionview-5_1, rubygem-actionpack-5_1: CSRF Vulnerability in rails-ujs</issue>
  <issue tracker="bnc" id="1172186">VUL-0: CVE-2020-8165: rubygem-activesupport-4_2,rubygem-activesupport-5_1 possibility of untrusted Ruby objects injection into a web application</issue>
  <issue tracker="bnc" id="1173351">VUL-0: CVE-2020-8184: rubygem-rack-1_4,rubygem-rack: rubygem-rack: percent-encoded cookies can be used to overwrite existing prefixed cookie names</issue>
  <issue tracker="bnc" id="1168554">RMT doesn't support 'partner' type subscriptions</issue>
  <issue tracker="bnc" id="1172182">VUL-1: CVE-2020-8166: rubygem-rails-4_2,rubygem-rails-5_1: Ability to forge per-form CSRF tokens given a global CSRF token</issue>
  <issue tracker="bnc" id="1172177">VUL-0: CVE-2020-8164: rubygem-actionpack-2,rubygem-actionpack-5_1,rubygem-actionpack-5.2: Possible Strong Parameters Bypass leading to untrusted user input</issue>
  <issue tracker="bnc" id="1165548">VUL-0: rmt-server: rmt-cli is using a fixed file path in /tmp/rmt.lock</issue>
  <packager>tmuntan1</packager>
  <rating>important</rating>
  <category>security</category>
  <summary>Security update for rmt-server</summary>
  <description>This update for rmt-server fixes the following issues:

Update to version 2.6.5:
- Solved potential bug of SCC repository URLs changing over time. RMT
  now self heals by removing the previous invalid repository and
  creating the correct one.
- Add web server settings to /etc/rmt.conf:
  Now it's possible to configure the minimum and maximum threads count as well
  the number of web server workers to be booted through /etc/rmt.conf.
- Instead of using an MD5 of URLs for custom repository friendly_ids,
  RMT now builds an ID from the name.
- Fix RMT file caching based on timestamps:
  Previously, RMT sent GET requests with the header 'If-Modified-Since' to a
  repository server and if the response had a 304 (Not Modified), it would copy
  a file from the local cache instead of downloading. However, if the local file
  timestamp accidentally changed to a date newer than the one on the repository
  server, RMT would have an outdated file, which caused some errors.
  Now, RMT makes HEAD requests to the repositories servers and inspect the
  'Last-Modified' header to decide whether to download a file or copy it from
  cache, by comparing the equalness of timestamps.
- Fixed an issue where relative paths supplied to `rmt-cli import repos`
  caused the command to fail.
- Friendlier IDs for custom repositories:
  In an effort to simplify the handling of SCC and custom repositories,
  RMT now has friendly IDs. For SCC repositories, it's the same SCC ID
  as before. For custom repositories, it can either be user provided
  or RMT generated (MD5 of the provided URL).
  Benefits:
  * `rmt-cli mirror repositories` now works for custom repositories.
  * Custom repository IDs can be the same across RMT instances.
  * No more confusing "SCC ID" vs "ID" in `rmt-cli` output.
  Deprecation Warnings:
  * RMT now uses a different ID for custom repositories than before.
    RMT still supports that old ID, but it's recommended to start
    using the new ID to ensure future compatibility.
- Updated rails and puma dependencies for security fixes.
</description>
</patchinfo>

Places

File _patchinfo of Package patchinfo.16827

Places