This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Security Advisory Articles
- RSA Community
- :
- Support
- :
- Security Advisory Articles
- :
- RSA Archer VRM OVA – Spectre and Meltdown Vulnerabilities (CVE-2017-5715, CVE-2017-5753, CVE-2017-5...
-
Options
- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RSA Archer VRM OVA – Spectre and Meltdown Vulnerabilities (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754)
Article Number
000036184
CVE ID
CVE-2017-5753, CVE-2017-5715, CVE-2017-5754
Applies To
RSA Product Set: VRM
RSA Product/Service Type: VRM Virtual Images (OVA)
RSA Product/Service Type: VRM Virtual Images (OVA)
Article Summary
The VRM Virtual Image OVA is a single-user, root-user-only appliance. The vulnerabilities do not introduce any additional risk to a customer’s environment for “in-guest” attacks, provided the recommended best practices to protect the access of highly privileged accounts are followed. However, you should patch your VRM Virtual Images (CentOS Version 6) with latest kernel security update, which is currently available in the CentOS repository:
https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html
https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html
Link to Advisories
Resolution
The following rpm files from the CentOS file repository must be installed in each VRM warehouse node to apply the kernel patch:
Once the rpms are installed, you must reboot each warehouse node.
Another way to apply the security patches is to run this command on each node: <yum update> followed by a reboot on each node one by one.
Note: The VRM Virtual Images are configured with an internal network which will not have access to CentOS repository. Therefore, you should ask your IT department if there is an internal repository or a proxy server that you can use while you apply the patch.
- kernel-2.6.32-696.18.7.el6.x86_64.rpm
- kernel-abi-whitelists-2.6.32-696.18.7.el6.noarch.rpm
- kernel-debug-2.6.32-696.18.7.el6.x86_64.rpm
- kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
- kernel-debug-devel-2.6.32-696.18.7.el6.x86_64.rpm
- kernel-devel-2.6.32-696.18.7.el6.x86_64.rpm
- kernel-doc-2.6.32-696.18.7.el6.noarch.rpm
- kernel-firmware-2.6.32-696.18.7.el6.noarch.rpm
- kernel-headers-2.6.32-696.18.7.el6.x86_64.rpm
- perf-2.6.32-696.18.7.el6.x86_64.rpm
- python-perf-2.6.32-696.18.7.el6.x86_64.rpm
- kernel-2.6.32-696.18.7.el6.i686.rpm
- kernel-abi-whitelists-2.6.32-696.18.7.el6.noarch.rpm
- kernel-debug-2.6.32-696.18.7.el6.i686.rpm
- kernel-debug-devel-2.6.32-696.18.7.el6.i686.rpm
- kernel-devel-2.6.32-696.18.7.el6.i686.rpm
- kernel-doc-2.6.32-696.18.7.el6.noarch.rpm
- kernel-firmware-2.6.32-696.18.7.el6.noarch.rpm
- kernel-headers-2.6.32-696.18.7.el6.i686.rpm
- perf-2.6.32-696.18.7.el6.i686.rpm
- python-perf-2.6.32-696.18.7.el6.i686.rpm
Once the rpms are installed, you must reboot each warehouse node.
Another way to apply the security patches is to run this command on each node: <yum update> followed by a reboot on each node one by one.
Note: The VRM Virtual Images are configured with an internal network which will not have access to CentOS repository. Therefore, you should ask your IT department if there is an internal repository or a proxy server that you can use while you apply the patch.
Disclaimer
Read and use the information in this RSA Security Advisory to assist in avoiding any situation that might arise from the problems described herein. If you have any questions regarding this product alert, contact RSA Software Technical Support at 1- 800 995 5095. RSA Security LLC and its affiliates, including without limitation, its ultimate parent company, Dell EMC, distributes RSA Security Advisories in order to bring to the attention of users of the affected RSA products, important security information. RSA recommends that all users determine the applicability of this information to their individual situations and take appropriate action. The information set forth herein is provided 'as is' without warranty of any kind. RSA disclaims all warranties, either express or implied, including the warranties of merchantability, fitness for a particular purpose, title and non-infringement. In no event, shall RSA, its affiliates or suppliers, be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if RSA, its affiliates or suppliers have been advised of the possibility of such damages. Some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental damages, so the foregoing limitation may not apply.
No ratings
