CVE-2018-3760

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.

There is an information leak vulnerability in Sprockets. Versions Affected: 4.0.0.beta7 and lower, 3.7.1 and lower, 2.12.4 and lower. Specially crafted requests can be used to access files that exists 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.

These are all security issues fixed in the ruby2.7-rubygem-sprockets-4.0.2-1.7 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby2.7-rubygem-sprockets-3.7-3.7.2-1.10 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.1-rubygem-sprockets-4.0.3-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.2-rubygem-sprockets-4.1.1-1.6 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.2-rubygem-sprockets-3.7-3.7.2-1.20 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.3-rubygem-sprockets-3.7-3.7.3-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.3-rubygem-sprockets-4.2.1-1.5 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.4-rubygem-sprockets-4.2.1-1.7 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby3.4-rubygem-sprockets-3.7-3.7.5-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby4.0-rubygem-sprockets-4.2.1-1.9 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the ruby4.0-rubygem-sprockets-3.7-3.7.5-1.5 package on the GA media of openSUSE Tumbleweed.

This update for rubygem-sprockets fixes the following issues:

The following security vulnerability was addressed:

• CVE-2018-3760: Fixed a path traversal issue in sprockets/server.rb:forbidden_request?(), which allowed remote attackers to read arbitrary files (bsc#1098369)

This update for rubygem-sprockets-2_12 fixes the following issues:

Security issue fixed:

• CVE-2018-3760: Fix path traversal in sprockets/server.rb:forbidden_request?() that can allow remote attackers to read arbitrary files (bsc#1098369).

This update for rubygem-sprockets-2_12 fixes the following issues:

Security issue fixed:

• CVE-2018-3760: Fix path traversal in sprockets/server.rb:forbidden_request?() that can allow remote attackers to read arbitrary files (bsc#1098369).

This update for crowbar, crowbar-ha, crowbar-init, crowbar-openstack, crowbar-ui fixes the following issues:

This security issues was fixed:

• CVE-2018-3760: Upgrade rubygem-sprockets to prevent an information leak. Specially crafted requests could have been be used to access files that exists on the filesystem that is outside an application's root directory, when the Sprockets server is used in production (bsc#1098369).
• CVE-2016-861: Add rate limiting for glance api (bsc#1005886)

These non-security issues were fixed for crowbar:

• upgrade: Lock crowbar-ui before admin upgrade
• upgrade: Make sure schemas are properly migrated after the upgrade

These non-security issues were fixed for crowbar-core:

• upgrade: Add the upgrade menu entry
• upgrade: Fix upgrade link
• apache: copytruncate apache logs bsc#1083093
• Fix exception handling in get_log_lines
• upgrade: Raise the default timeouts for most time consuming actions
• upgrade: Do not allow manila-share on compute nodes
• control_lib: fix host allocation check
• upgrade: Check input is a valid node for nodes
• upgrade: Provide better information after the failure
• upgrade: Report missing scripts
• upgrade: Improve error messages with lists
• upgrade: Do not allow cinder-volume on compute nodes
• upgrade: Fix file layout for rails' autoloading (bsc#1096759)
• upgrade: Added API calls for postponing/resuming compute nodes upgrade
• upgrade: Unlock crowbar-ui after completed upgrade
• upgrade: Do not check if ceph roles are present on compute nodes
• upgrade: Fix labels for SOC8 repositories
• upgrade: Finish only controllers step

These non-security issues were fixed for crowbar-ha:

• haproxy: increased SSL stick table to 100k
• DRBD: Fix DRBD resources setup on reinstall node
• pacemaker: allow multiple meta parameters (bsc#1093898)

These non-security issues were fixed for crowbar-openstack:

• nova: reload nova-placement-api (bsc#1103383)
• Synchronize SSL in the cluster (bsc#1081518)
• neutron: add force_metadata attribute
• copytruncate apache logs instead of creating
• rabbitmq: set client timout to default value
• Revert 'database: Split database-server role into backend specific roles'
• Revert 'database: Allow parallel deployments of postgresql and mysql'
• Revert 'database: Allow parallel HA deployment of PostgreSQL and MariaDB'
• Revert 'database: Fix 'Attributes' UI after role renaming'
• Revert 'monasca: Fix check for mysql after it got moved to a separate role'
• Revert 'Restore caching of db_settings'
• Revert 'database: Migration fixes for separate DB roles'
• database: Migration fixes for separate DB roles
• Restore caching of db_settings
• monasca: Fix check for mysql after it got moved to a separate role
• database: Fix 'Attributes' UI after role renaming
• database: Allow parallel HA deployment of PostgreSQL and MariaDB
• database: Allow parallel deployments of postgresql and mysql
• database: Split database-server role into backend specific roles
• Do not automatically put manila-share roles to compute nodes
• rabbitmq: check for rabbit readiness
• rabbitmq: Make sure rabbit is running on cluster
• monasca: various monasca-installer improvements
• manila: Correct field name for cluster name
• mariadb: Add prefix to configs
• mariadb: Remove redundant config values
• aodh: Add config for alarm_history_ttl (bsc#1073703)

These non-security issues were fixed for crowbar-ui:

• upgrade: Dummy backend for status testing
• upgrade: Refactor postpone nodes upgrade
• upgrade: Allow interruption of status wait loop
• upgrade: Added ability to postpone upgrade nodes
• upgrade: Add ability to postpone upgrade nodes
• upgrade: Add ability to postpone upgrade nodes
• upgrade: Add ability to postpone upgrade nodes
• Add ability to postpone upgrade
• upgrade: Remove openstack precheck
• upgrade: Fixed error key for ha_configured
• upgrade: Remove CEPH related code
• Remove the non-essential database-configuration controller
• remove ui typo test -…

This update for crowbar, crowbar-ha, crowbar-init, crowbar-openstack, crowbar-ui fixes the following issues:

This security issues was fixed:

• CVE-2018-3760: Upgrade rubygem-sprockets to prevent an information leak. Specially crafted requests could have been be used to access files that exists on the filesystem that is outside an application's root directory, when the Sprockets server is used in production (bsc#1098369).
• CVE-2016-861: Add rate limiting for glance api (bsc#1005886)

These non-security issues were fixed for crowbar:

• upgrade: Lock crowbar-ui before admin upgrade
• upgrade: Make sure schemas are properly migrated after the upgrade
• upgrade: No need for database dump before the upgrade
• upgrade: No need to use crowbar-init during the upgrade

These non-security issues were fixed for crowbar-core:

• upgrade: Remove pre-upgrade constraints from existing locations
• upgrade: Show the grep result when checking for not-migrated instances
• upgrade: Set clone_stateless_services to false on upgrade
• control_lib: fix host allocation check
• Fix exception handling in get_log_lines
• apache: copytruncate apache logs bsc#1083093
• upgrade: Refresh repos before crowbar-ui update (bsc#1099392)
• upgrade: Reset RabbitMQ nodes during upgrade
• upgrade: Do not allow cinder-volume on compute nodes
• upgrade: Wait until all nova-compute services are up before evacuation
• upgrade: Save the information which set of nodes should be upgraded
• Let skip_unready_nodes skip also nodes that are in crowbar_upgrade state
• upgrade: Add missing brackets checking for nodes
• upgrade: Make sure postponed nodes can be skipped when applying proposal
• upgrade: When the upgrade is not finished, show a link to wizard
• upgrade: Correctly delete remaining upgrade scripts
• upgrade: Wait for services shutdown to finish
• upgrade: Unlock crowbar-ui after completed upgrade
• upgrade: Stop cron before stopping any other service
• upgrade: Provide better information after the failure
• upgrade: Report missing scripts
• upgrade: Better check for upgraded nodes - do not rely on state
• upgrade: Improve error messages with lists
• upgrade: Check input is a valid node for nodes
• upgrade: Delete upgrade scripts really at the end of upgrade
• upgrade: Increase the timeout for deleting pacemaker resources
• upgrade: Adapt the check for upgraded? value
• upgrade: Move step to mark the admin upgrade end
• upgrade: Do not finalize nodes that are not upgraded
• upgrade: Fix file layout for rails' autoloading (bsc#1096759)
• upgrade: Deleting cinder services from database no longer needed
• upgrade: Allow postpone and resume of compute nodes upgrade
• upgrade: Allow the access to controller actions when upgrade is postponed
• upgrade: Finalize upgrade of controller nodes after they are done
• upgrade: Added API calls for postponing/resuming compute nodes upgrade
• upgrade: Unblock upgrade status API in Cloud8
• upgrade: Do not end admin step while it is still running (bsc#1095420)
• upgrade: Adapt ceph-related checks to 7-8 upgrade
• upgrade: Allow running schema migrations on upgrade
• upgrade: Fix platform retrieval

These non-security issues were fixed for crowbar-ha:

• pacemaker: allow multiple meta parameters (bsc#1093898)
• haproxy: active-active mode, just one VIP

These non-security issues were fixed for crowbar-openstack:

• Synchronize SSL in the cluster (bsc#1081518)
• neutron: add force_metadata attribute
• rabbitmq: set client timout to default value
• /etc/sysctl.d/99-sysctl.conf is a symlink to /etc/sysctl.conf
• Do not automatically put manila-share roles to compute nodes
• rabbitmq: check for rabbit readiness
• rabbitmq: Make sure rabbit is running on cluster
• monasca: various monasca-installer improvements
• monasca: reduce monasca-installer runs (bsc#1096043)
• manila: Correct field name for cluster name
• Do not mark [:nova][:db_synced] too early
• nova: Do not do partial online migrations, that was Newton specific
• monasca:…

It was discovered that Sprockets incorrectly handled certain specially crafted requests when the Sprockets server was used in production. A remote attacker could possibly use this issue to access files outside of the application's root directory.