RHSA-2019:0361

csafUSredhat_csaf

Red Hat Security Advisory: rhvm-appliance security update

view advisory published 2019-02-18

An update for rhvm-appliance is now available for Red Hat Virtualization 4 for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

01

describes (2)

Related CVEs.

IDseverity exploitable
CVE-2018-16865UShigh7.8—
An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when many entries are sent to the jou…
CVE-2018-16864UShigh7.8—
An allocation of memory without limits, that could result in the stack clashing with another memory region, was discovered in systemd-journald when a program with long command line…
02

references

External citations — patches, advisories, analysis.

03

remediations (12)

  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.noarch as a component of Red Hat Virtualization 4 Hypervisor for RHEL 7

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.noarch as a component of Red Hat Virtualization 4 Hypervisor for RHEL 7

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.noarch as a component of Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.noarch as a component of Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.src as a component of Red Hat Virtualization 4 Hypervisor for RHEL 7

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.src as a component of Red Hat Virtualization 4 Hypervisor for RHEL 7

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.src as a component of Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Fixedrhvm-appliance-2:4.2-20190129.0.el7.src as a component of Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/2974891

    https://access.redhat.com/errata/RHSA-2019:0361
  • Workaroundrhvm-appliance-2:4.2-20190129.0.el7.noarch as a component of Red Hat Virtualization 4 Hypervisor for RHEL 7

    To increase the time an attacker needs to exploit this flaw you could override the `StartLimitInterval=` (called StartLimitIntervalSec in newer systemd versions) and `StartLimitBurst=` settings. In this way the attack may require much longer to be successful. To edit the journald service use `sudo systemctl edit systemd-journald.service` and add: ``` [Service] StartLimitInterval=120 StartLimitBurst=3 ```

  • Workaroundrhvm-appliance-2:4.2-20190129.0.el7.noarch as a component of Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts

    To increase the time an attacker needs to exploit this flaw you could override the `StartLimitInterval=` (called StartLimitIntervalSec in newer systemd versions) and `StartLimitBurst=` settings. In this way the attack may require much longer to be successful. To edit the journald service use `sudo systemctl edit systemd-journald.service` and add: ``` [Service] StartLimitInterval=120 StartLimitBurst=3 ```

  • Workaroundrhvm-appliance-2:4.2-20190129.0.el7.src as a component of Red Hat Virtualization 4 Hypervisor for RHEL 7

    To increase the time an attacker needs to exploit this flaw you could override the `StartLimitInterval=` (called StartLimitIntervalSec in newer systemd versions) and `StartLimitBurst=` settings. In this way the attack may require much longer to be successful. To edit the journald service use `sudo systemctl edit systemd-journald.service` and add: ``` [Service] StartLimitInterval=120 StartLimitBurst=3 ```

  • Workaroundrhvm-appliance-2:4.2-20190129.0.el7.src as a component of Red Hat Virtualization 4 Management Agent for RHEL 7 Hosts

    To increase the time an attacker needs to exploit this flaw you could override the `StartLimitInterval=` (called StartLimitIntervalSec in newer systemd versions) and `StartLimitBurst=` settings. In this way the attack may require much longer to be successful. To edit the journald service use `sudo systemctl edit systemd-journald.service` and add: ``` [Service] StartLimitInterval=120 StartLimitBurst=3 ```

scry

Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.

Free scan