CVE-2017-8380

Related Vulnerabilities: CVE-2017-8380  

Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.

The MITRE CVE dictionary describes this issue as:

Buffer overflow in the "megasas_mmio_write" function in Qemu 2.9.0 allows remote attackers to have unspecified impact via unknown vectors.

Find out more about CVE-2017-8380 from the MITRE CVE dictionary dictionary and NIST NVD.

CVSS v2 metrics

NOTE: The following CVSS v2 metrics and score provided are preliminary and subject to review.

Base Score 3.8
Base Metrics AV:A/AC:M/Au:S/C:P/I:N/A:P
Access Vector Adjacent Network
Access Complexity Medium
Authentication Single
Confidentiality Impact Partial
Integrity Impact None
Availability Impact Partial

CVSS v3 metrics

NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.

CVSS3 Base Score 4.4
CVSS3 Base Metrics CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:L
Attack Vector Adjacent Network
Attack Complexity High
Privileges Required Low
User Interaction None
Scope Changed
Confidentiality Low
Integrity Impact None
Availability Impact Low

Find out more about Red Hat support for the Common Vulnerability Scoring System (CVSS).

Affected Packages State

Platform Package State
Red Hat OpenStack Platform 9.0 qemu-kvm-rhev Not affected
Red Hat OpenStack Platform 8.0 (Liberty) qemu-kvm-rhev Not affected
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 qemu-kvm-rhev Not affected
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7 qemu-kvm-rhev Not affected
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) qemu-kvm-rhev Not affected
Red Hat Enterprise Linux 7 qemu-kvm-rhev Not affected
Red Hat Enterprise Linux 7 qemu-kvm Not affected
Red Hat Enterprise Linux 6 qemu-kvm Not affected
Red Hat Enterprise Linux 6 qemu-kvm-rhev Not affected
Red Hat Enterprise Linux 5 kvm Not affected
Red Hat Enterprise Linux 5 xen Not affected

Acknowledgements

Red Hat would like to thank YY Z(Researcher) Wjjzhang (Tencent.com Inc.) for reporting this issue.