{"id":"CVE-2019-6778","aliases":["BELL-CVE-2019-6778","DEBIAN-CVE-2019-6778","DLA-1694-1","DSA-4454-1","EUVD-2019-16336","GHSA-4wxm-q46g-3mcf","RHSA-2019:1883","RHSA-2019:1968","RHSA-2019:2425","RHSA-2019:2892","SUSE-SU-2019:0423-1","SUSE-SU-2019:0435-1","SUSE-SU-2019:0457-1","SUSE-SU-2019:0471-1","SUSE-SU-2019:0471-2","SUSE-SU-2019:0489-1","SUSE-SU-2019:0582-1","SUSE-SU-2019:0825-1","SUSE-SU-2019:0827-1","SUSE-SU-2019:0891-1","SUSE-SU-2019:0921-1","SUSE-SU-2019:13962-1","SUSE-SU-2019:14001-1","SUSE-SU-2019:14011-1","SUSE-SU-2019:2223-1","SUSE-SU-2020:0844-1","SUSE-SU-2020:0845-1","SUSE-SU-2020:14396-1","SUSE-SU-2020:1501-1","SUSE-SU-2020:1514-1","SUSE-SU-2020:1523-1","SUSE-SU-2020:1526-1","SUSE-SU-2020:1538-1","SUSE-SU-2021:14706-1","UBUNTU-CVE-2019-6778","USN-3923-1","openSUSE-SU-2019:0254-1","openSUSE-SU-2019:2044-1","openSUSE-SU-2020:0468-1","openSUSE-SU-2024:11287-1","openSUSE-SU-2024:11387-1"],"status":"published","title":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","severity":{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-08","score":0.0061,"percentile":0.49473,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-787"],"published":"2019-01-25T00:00:00Z","modified":"2026-10-24T10:30:29Z","fixes":[{"ecosystem":"Debian:12","package":"qemu","fixed_in":["1:3.1+dfsg-3"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"qemu","fixed_in":["1:3.1+dfsg-3"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"qemu","fixed_in":["1:3.1+dfsg-3"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"slirp4netns","fixed_in":["0.2.1-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"slirp4netns","fixed_in":["0.2.1-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"slirp4netns","fixed_in":["0.2.1-1"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-img","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm-common","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm-debuginfo","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm-tools","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-img","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm-common","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm-debuginfo","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm-tools","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-img","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm-common","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm-debuginfo","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm-tools","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-img","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm-common","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm-debuginfo","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm-tools","fixed_in":["10:1.5.3-160.el7_6.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"qemu","fixed_in":["2.0.0+dfsg-2ubuntu1.45"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"qemu","fixed_in":["1:2.5+dfsg-5ubuntu10.36"],"sources":["osv"]},{"ecosystem":"Ubuntu:18.04:LTS","package":"qemu","fixed_in":["1:2.11+dfsg-1ubuntu7.12"],"sources":["osv"]},{"ecosystem":"openSUSE:Tumbleweed","package":"slirp4netns","fixed_in":["1.1.11-1.2"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.1+dfsg-3"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.1+dfsg-3"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:3.1+dfsg-3"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"slirp4netns","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.1-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"slirp4netns","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.1-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"slirp4netns","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.1-1"}]}]},{"source":"osv","ecosystem":"Debian:8","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.1+dfsg-12+deb8u10"}]}],"versions":["1:2.1+dfsg-11","1:2.1+dfsg-12","1:2.1+dfsg-12+deb8u1","1:2.1+dfsg-12+deb8u2","1:2.1+dfsg-12+deb8u3","1:2.1+dfsg-12+deb8u4","1:2.1+dfsg-12+deb8u4~bpo70+1","1:2.1+dfsg-12+deb8u5","1:2.1+dfsg-12+deb8u5a","1:2.1+dfsg-12+deb8u5a~bpo70+1","1:2.1+dfsg-12+deb8u6","1:2.1+dfsg-12+deb8u7","1:2.1+dfsg-12+deb8u8","1:2.1+dfsg-12+deb8u9","1:2.1+dfsg-12~bpo70+1"],"bundled":3},{"source":"osv","ecosystem":"Debian:9","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.8+dfsg-6+deb9u6"}]}],"versions":["1:2.8+dfsg-6","1:2.8+dfsg-6+deb9u1","1:2.8+dfsg-6+deb9u2","1:2.8+dfsg-6+deb9u3","1:2.8+dfsg-6+deb9u4","1:2.8+dfsg-6+deb9u5"],"bundled":12},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::client","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::computenode","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::server","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::workstation","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:1.5.3-160.el7_6.3"}]}]},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:7::hypervisor","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.2","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.2","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.2","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.2","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.2","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.3","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.3","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.3","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.3","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:rhev_manager:4.3","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-18.el7_6.7"}]}],"bundled":2},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:10::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:13::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:13::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:13::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:13::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:13::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:14::el7","package":"qemu-img-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:14::el7","package":"qemu-kvm-common-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:14::el7","package":"qemu-kvm-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:14::el7","package":"qemu-kvm-rhev-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:openstack:14::el7","package":"qemu-kvm-tools-rhev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10:2.12.0-33.el7"}]}],"bundled":6},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::client","package":"qemu-guest-agent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::client","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::client","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::client","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::client","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::computenode","package":"qemu-guest-agent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::computenode","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::computenode","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::computenode","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::computenode","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::server","package":"qemu-guest-agent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::server","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::server","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::server","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::server","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::workstation","package":"qemu-guest-agent","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::workstation","package":"qemu-img","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::workstation","package":"qemu-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::workstation","package":"qemu-kvm-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"Red Hat:enterprise_linux:6::workstation","package":"qemu-kvm-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:0.12.1.2-2.506.el6_10.5"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-9.20.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-9.20.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP4","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-5.8.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP4","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-5.8.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP4","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-5.8.1"}]}],"bundled":5},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.2-48.49.3"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.20.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.20.1"}]}],"bundled":4},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 7","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.49.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.49.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.49.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-BCL","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.49.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 4","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.49.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.28.1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.28.1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.28.1"}]}],"bundled":8},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.5_28-22.58.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.5_28-22.58.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_40-22.77.1"}]}],"bundled":15},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.1_04-2.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.1_04-2.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.1_04-2.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.11.1_04-2.6.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 7","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.6_06-43.48.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.6_06-43.48.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-LTSS","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.6_06-43.48.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-BCL","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.6_06-43.48.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.7.6_06-43.48.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-60.21.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-60.21.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_40-61.43.2"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_40-61.43.2"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.4_40-61.43.2"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Point of Sale 11 SP3","package":"xen","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.2.5_21-45.30.1"}]}],"bundled":14},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP1","package":"libcontainers-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20190401-3.3.5"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP1","package":"fuse-overlayfs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1-3.3.8"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP1","package":"fuse3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.1-3.3.8"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP1","package":"podman","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.4-4.8.1"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Containers 15 SP1","package":"slirp4netns","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.0-3.3.3"}]}],"bundled":3},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP1","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1.1-9.14.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP1","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1.1-9.14.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1.1-3.9.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP5","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1.1-3.9.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4-LTSS","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-60.31.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP4","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-5.26.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP4","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-5.26.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP1","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.29.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP1-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.3.1-33.29.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-ESPOS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-9.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-9.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-9.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.2-9.36.1"}]}],"bundled":6},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 7","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.59.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.59.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.59.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2-BCL","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6.2-41.59.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:HPE Helion OpenStack 8","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud 8","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:OpenStack Cloud Crowbar 8","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3-LTSS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3-BCL","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Enterprise Storage 5","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1-6.44.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Point of Sale 11 SP3","package":"kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2-53.38.1"}]}],"bundled":21},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0+dfsg-2ubuntu1.45"}]}],"versions":["1.5.0+dfsg-3ubuntu5","1.5.0+dfsg-3ubuntu6","1.6.0+dfsg-2ubuntu1","1.6.0+dfsg-2ubuntu2","1.6.0+dfsg-2ubuntu3","1.6.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu1","1.7.0+dfsg-2ubuntu2","1.7.0+dfsg-2ubuntu3","1.7.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu5","1.7.0+dfsg-2ubuntu7","1.7.0+dfsg-2ubuntu8","1.7.0+dfsg-2ubuntu9","1.7.0+dfsg-3ubuntu1~ppa1","1.7.0+dfsg-3ubuntu1","1.7.0+dfsg-3ubuntu2","1.7.0+dfsg-3ubuntu3","1.7.0+dfsg-3ubuntu4","1.7.0+dfsg-3ubuntu5","1.7.0+dfsg-3ubuntu6","1.7.0+dfsg-3ubuntu7","2.0.0~rc1+dfsg-0ubuntu1","2.0.0~rc1+dfsg-0ubuntu2","2.0.0~rc1+dfsg-0ubuntu3","2.0.0~rc1+dfsg-0ubuntu3.1","2.0.0+dfsg-2ubuntu1","2.0.0+dfsg-2ubuntu1.1","2.0.0+dfsg-2ubuntu1.2","2.0.0+dfsg-2ubuntu1.3","2.0.0+dfsg-2ubuntu1.5","2.0.0+dfsg-2ubuntu1.6","2.0.0+dfsg-2ubuntu1.7","2.0.0+dfsg-2ubuntu1.8","2.0.0+dfsg-2ubuntu1.9","2.0.0+dfsg-2ubuntu1.10","2.0.0+dfsg-2ubuntu1.11","2.0.0+dfsg-2ubuntu1.13","2.0.0+dfsg-2ubuntu1.14","2.0.0+dfsg-2ubuntu1.15","2.0.0+dfsg-2ubuntu1.16","2.0.0+dfsg-2ubuntu1.17","2.0.0+dfsg-2ubuntu1.18","2.0.0+dfsg-2ubuntu1.19","2.0.0+dfsg-2ubuntu1.20","2.0.0+dfsg-2ubuntu1.21","2.0.0+dfsg-2ubuntu1.22","2.0.0+dfsg-2ubuntu1.24","2.0.0+dfsg-2ubuntu1.25","2.0.0+dfsg-2ubuntu1.26","2.0.0+dfsg-2ubuntu1.27","2.0.0+dfsg-2ubuntu1.28","2.0.0+dfsg-2ubuntu1.29","2.0.0+dfsg-2ubuntu1.30","2.0.0+dfsg-2ubuntu1.31","2.0.0+dfsg-2ubuntu1.32","2.0.0+dfsg-2ubuntu1.33","2.0.0+dfsg-2ubuntu1.34","2.0.0+dfsg-2ubuntu1.35","2.0.0+dfsg-2ubuntu1.36","2.0.0+dfsg-2ubuntu1.38","2.0.0+dfsg-2ubuntu1.39","2.0.0+dfsg-2ubuntu1.40","2.0.0+dfsg-2ubuntu1.41","2.0.0+dfsg-2ubuntu1.42","2.0.0+dfsg-2ubuntu1.43","2.0.0+dfsg-2ubuntu1.44"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.5+dfsg-5ubuntu10.36"}]}],"versions":["1:2.3+dfsg-5ubuntu9","1:2.3+dfsg-5ubuntu10","1:2.4+dfsg-4ubuntu1","1:2.4+dfsg-4ubuntu2","1:2.4+dfsg-4ubuntu3","1:2.4+dfsg-5ubuntu3","1:2.5+dfsg-1ubuntu2","1:2.5+dfsg-1ubuntu3","1:2.5+dfsg-1ubuntu4","1:2.5+dfsg-1ubuntu5","1:2.5+dfsg-5ubuntu1","1:2.5+dfsg-5ubuntu2","1:2.5+dfsg-5ubuntu4","1:2.5+dfsg-5ubuntu6","1:2.5+dfsg-5ubuntu7","1:2.5+dfsg-5ubuntu10","1:2.5+dfsg-5ubuntu10.1","1:2.5+dfsg-5ubuntu10.2","1:2.5+dfsg-5ubuntu10.3","1:2.5+dfsg-5ubuntu10.4","1:2.5+dfsg-5ubuntu10.5","1:2.5+dfsg-5ubuntu10.6","1:2.5+dfsg-5ubuntu10.7","1:2.5+dfsg-5ubuntu10.8","1:2.5+dfsg-5ubuntu10.9","1:2.5+dfsg-5ubuntu10.10","1:2.5+dfsg-5ubuntu10.11","1:2.5+dfsg-5ubuntu10.13","1:2.5+dfsg-5ubuntu10.14","1:2.5+dfsg-5ubuntu10.15","1:2.5+dfsg-5ubuntu10.16","1:2.5+dfsg-5ubuntu10.20","1:2.5+dfsg-5ubuntu10.21","1:2.5+dfsg-5ubuntu10.22","1:2.5+dfsg-5ubuntu10.24","1:2.5+dfsg-5ubuntu10.25","1:2.5+dfsg-5ubuntu10.26","1:2.5+dfsg-5ubuntu10.28","1:2.5+dfsg-5ubuntu10.29","1:2.5+dfsg-5ubuntu10.30","1:2.5+dfsg-5ubuntu10.31","1:2.5+dfsg-5ubuntu10.32","1:2.5+dfsg-5ubuntu10.33","1:2.5+dfsg-5ubuntu10.34","1:2.5+dfsg-5ubuntu10.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.11+dfsg-1ubuntu7.12"}]}],"versions":["1:2.10+dfsg-0ubuntu3","1:2.10+dfsg-0ubuntu4","1:2.10+dfsg-0ubuntu5","1:2.11+dfsg-1ubuntu1","1:2.11+dfsg-1ubuntu2","1:2.11+dfsg-1ubuntu4","1:2.11+dfsg-1ubuntu5","1:2.11+dfsg-1ubuntu6","1:2.11+dfsg-1ubuntu7","1:2.11+dfsg-1ubuntu7.1","1:2.11+dfsg-1ubuntu7.2","1:2.11+dfsg-1ubuntu7.3","1:2.11+dfsg-1ubuntu7.4","1:2.11+dfsg-1ubuntu7.5","1:2.11+dfsg-1ubuntu7.6","1:2.11+dfsg-1ubuntu7.7","1:2.11+dfsg-1ubuntu7.8","1:2.11+dfsg-1ubuntu7.9","1:2.11+dfsg-1ubuntu7.10"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0+dfsg-2ubuntu1.45"}]}],"versions":["1.5.0+dfsg-3ubuntu5","1.5.0+dfsg-3ubuntu6","1.6.0+dfsg-2ubuntu1","1.6.0+dfsg-2ubuntu2","1.6.0+dfsg-2ubuntu3","1.6.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu1","1.7.0+dfsg-2ubuntu2","1.7.0+dfsg-2ubuntu3","1.7.0+dfsg-2ubuntu4","1.7.0+dfsg-2ubuntu5","1.7.0+dfsg-2ubuntu7","1.7.0+dfsg-2ubuntu8","1.7.0+dfsg-2ubuntu9","1.7.0+dfsg-3ubuntu1~ppa1","1.7.0+dfsg-3ubuntu1","1.7.0+dfsg-3ubuntu2","1.7.0+dfsg-3ubuntu3","1.7.0+dfsg-3ubuntu4","1.7.0+dfsg-3ubuntu5","1.7.0+dfsg-3ubuntu6","1.7.0+dfsg-3ubuntu7","2.0.0~rc1+dfsg-0ubuntu1","2.0.0~rc1+dfsg-0ubuntu2","2.0.0~rc1+dfsg-0ubuntu3","2.0.0~rc1+dfsg-0ubuntu3.1","2.0.0+dfsg-2ubuntu1","2.0.0+dfsg-2ubuntu1.1","2.0.0+dfsg-2ubuntu1.2","2.0.0+dfsg-2ubuntu1.3","2.0.0+dfsg-2ubuntu1.5","2.0.0+dfsg-2ubuntu1.6","2.0.0+dfsg-2ubuntu1.7","2.0.0+dfsg-2ubuntu1.8","2.0.0+dfsg-2ubuntu1.9","2.0.0+dfsg-2ubuntu1.10","2.0.0+dfsg-2ubuntu1.11","2.0.0+dfsg-2ubuntu1.13","2.0.0+dfsg-2ubuntu1.14","2.0.0+dfsg-2ubuntu1.15","2.0.0+dfsg-2ubuntu1.16","2.0.0+dfsg-2ubuntu1.17","2.0.0+dfsg-2ubuntu1.18","2.0.0+dfsg-2ubuntu1.19","2.0.0+dfsg-2ubuntu1.20","2.0.0+dfsg-2ubuntu1.21","2.0.0+dfsg-2ubuntu1.22","2.0.0+dfsg-2ubuntu1.24","2.0.0+dfsg-2ubuntu1.25","2.0.0+dfsg-2ubuntu1.26","2.0.0+dfsg-2ubuntu1.27","2.0.0+dfsg-2ubuntu1.28","2.0.0+dfsg-2ubuntu1.29","2.0.0+dfsg-2ubuntu1.30","2.0.0+dfsg-2ubuntu1.31","2.0.0+dfsg-2ubuntu1.32","2.0.0+dfsg-2ubuntu1.33","2.0.0+dfsg-2ubuntu1.34","2.0.0+dfsg-2ubuntu1.35","2.0.0+dfsg-2ubuntu1.36","2.0.0+dfsg-2ubuntu1.38","2.0.0+dfsg-2ubuntu1.39","2.0.0+dfsg-2ubuntu1.40","2.0.0+dfsg-2ubuntu1.41","2.0.0+dfsg-2ubuntu1.42","2.0.0+dfsg-2ubuntu1.43","2.0.0+dfsg-2ubuntu1.44"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.5+dfsg-5ubuntu10.36"}]}],"versions":["1:2.3+dfsg-5ubuntu9","1:2.3+dfsg-5ubuntu10","1:2.4+dfsg-4ubuntu1","1:2.4+dfsg-4ubuntu2","1:2.4+dfsg-4ubuntu3","1:2.4+dfsg-5ubuntu3","1:2.5+dfsg-1ubuntu2","1:2.5+dfsg-1ubuntu3","1:2.5+dfsg-1ubuntu4","1:2.5+dfsg-1ubuntu5","1:2.5+dfsg-5ubuntu1","1:2.5+dfsg-5ubuntu2","1:2.5+dfsg-5ubuntu4","1:2.5+dfsg-5ubuntu6","1:2.5+dfsg-5ubuntu7","1:2.5+dfsg-5ubuntu10","1:2.5+dfsg-5ubuntu10.1","1:2.5+dfsg-5ubuntu10.2","1:2.5+dfsg-5ubuntu10.3","1:2.5+dfsg-5ubuntu10.4","1:2.5+dfsg-5ubuntu10.5","1:2.5+dfsg-5ubuntu10.6","1:2.5+dfsg-5ubuntu10.7","1:2.5+dfsg-5ubuntu10.8","1:2.5+dfsg-5ubuntu10.9","1:2.5+dfsg-5ubuntu10.10","1:2.5+dfsg-5ubuntu10.11","1:2.5+dfsg-5ubuntu10.13","1:2.5+dfsg-5ubuntu10.14","1:2.5+dfsg-5ubuntu10.15","1:2.5+dfsg-5ubuntu10.16","1:2.5+dfsg-5ubuntu10.20","1:2.5+dfsg-5ubuntu10.21","1:2.5+dfsg-5ubuntu10.22","1:2.5+dfsg-5ubuntu10.24","1:2.5+dfsg-5ubuntu10.25","1:2.5+dfsg-5ubuntu10.26","1:2.5+dfsg-5ubuntu10.28","1:2.5+dfsg-5ubuntu10.29","1:2.5+dfsg-5ubuntu10.30","1:2.5+dfsg-5ubuntu10.31","1:2.5+dfsg-5ubuntu10.32","1:2.5+dfsg-5ubuntu10.33","1:2.5+dfsg-5ubuntu10.34","1:2.5+dfsg-5ubuntu10.35"],"bundled":4},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.11+dfsg-1ubuntu7.12"}]}],"versions":["1:2.10+dfsg-0ubuntu3","1:2.10+dfsg-0ubuntu4","1:2.10+dfsg-0ubuntu5","1:2.11+dfsg-1ubuntu1","1:2.11+dfsg-1ubuntu2","1:2.11+dfsg-1ubuntu4","1:2.11+dfsg-1ubuntu5","1:2.11+dfsg-1ubuntu6","1:2.11+dfsg-1ubuntu7","1:2.11+dfsg-1ubuntu7.1","1:2.11+dfsg-1ubuntu7.2","1:2.11+dfsg-1ubuntu7.3","1:2.11+dfsg-1ubuntu7.4","1:2.11+dfsg-1ubuntu7.5","1:2.11+dfsg-1ubuntu7.6","1:2.11+dfsg-1ubuntu7.7","1:2.11+dfsg-1ubuntu7.8","1:2.11+dfsg-1ubuntu7.9","1:2.11+dfsg-1ubuntu7.10"],"bundled":4},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"fuse-overlayfs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1-lp151.2.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"fuse3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.1-lp151.2.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"libcontainers-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"20190401-lp151.2.3.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"podman","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.4-lp151.3.3.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"slirp4netns","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.0-lp151.2.3.1"}]}],"bundled":3},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1.1-lp151.7.12.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Leap 15.1","package":"qemu-linux-user","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.1.1-lp151.7.12.1"}]}],"bundled":6},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"qemu","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.0-32.1"}]}],"bundled":135},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"slirp4netns","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.11-1.2"}]}]}],"products":[{"vendor":"canonical","product":"ubuntu_linux"},{"vendor":"fedoraproject","product":"fedora"},{"vendor":"opensuse","product":"leap"},{"vendor":"qemu","product":"qemu"}],"references":[{"url":"http://www.securityfocus.com/bid/106758","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-02/msg00073.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","Mailing List","Third Party Advisory","advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2019/01/24/5","tags":["x_refsource_MISC","x_transferred","Mailing List","Patch","Third Party Advisory","fix"]},{"url":"https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg03132.html","tags":["x_refsource_MISC","x_transferred","Mailing List","Patch","Third Party Advisory","fix","report"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CGCFIFSIWUREEQQOZDZFBYKWZHXCWBZN/","tags":["vendor-advisory","x_refsource_FEDORA","x_transferred","web"]},{"url":"https://usn.ubuntu.com/3923-1/","tags":["vendor-advisory","x_refsource_UBUNTU","x_transferred","Third Party Advisory","advisory"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KJMTVGDLA654HNCDGLCUEIP36SNJEKK7/","tags":["vendor-advisory","x_refsource_FEDORA","x_transferred","web"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-03/msg00042.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","Mailing List","Third Party Advisory","advisory"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00072.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","web"]},{"url":"https://www.debian.org/security/2019/dsa-4454","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","advisory"]},{"url":"https://seclists.org/bugtraq/2019/May/76","tags":["mailing-list","x_refsource_BUGTRAQ","x_transferred","web"]},{"url":"https://access.redhat.com/errata/RHSA-2019:1883","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2019:1968","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2019:2425","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00001.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","web"]},{"url":"https://access.redhat.com/errata/RHSA-2019:2892","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00007.html","tags":["vendor-advisory","x_refsource_SUSE","x_transferred","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-6778","tags":["advisory"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CGCFIFSIWUREEQQOZDZFBYKWZHXCWBZN/"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KJMTVGDLA654HNCDGLCUEIP36SNJEKK7/"},{"url":"https://github.com/advisories/GHSA-4wxm-q46g-3mcf"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2019-6778","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2019-6778","tags":["advisory"]},{"url":"https://access.redhat.com/security/updates/classification/#important","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1664205","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_1883.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-6778","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-6778","tags":["advisory","report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1693101","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_1968.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-20815","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-20815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-20815","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1615637","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1636712","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1636777","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1668160","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1678515","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1728358","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1728359","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1728360","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_2425.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-15746","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-15746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-15746","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-17958","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-17958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-17958","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-17963","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-17963","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-17963","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-6501","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-6501","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-6501","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-9824","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-9824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-9824","tags":["advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1581013","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1586245","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1636773","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1712670","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2019/rhsa-2019_2892.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-10839","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-10839","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-10839","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-11806","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-11806","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-11806","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-17962","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-17962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-17962","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2019-12155","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2019-12155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2019-12155","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190423-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1063993","tags":["report"]},{"url":"https://bugzilla.suse.com/1079730","tags":["report"]},{"url":"https://bugzilla.suse.com/1100408","tags":["report"]},{"url":"https://bugzilla.suse.com/1101982","tags":["report"]},{"url":"https://bugzilla.suse.com/1112646","tags":["report"]},{"url":"https://bugzilla.suse.com/1114957","tags":["report"]},{"url":"https://bugzilla.suse.com/1116717","tags":["report"]},{"url":"https://bugzilla.suse.com/1117275","tags":["report"]},{"url":"https://bugzilla.suse.com/1119493","tags":["report"]},{"url":"https://bugzilla.suse.com/1121600","tags":["report"]},{"url":"https://bugzilla.suse.com/1123156","tags":["report"]},{"url":"https://bugzilla.suse.com/1123179","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-6778","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190435-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190457-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190471-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190471-2/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190489-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1084604","tags":["report"]},{"url":"https://bugzilla.suse.com/1113231","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-7858","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190582-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1056334","tags":["report"]},{"url":"https://bugzilla.suse.com/1056386","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190825-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1056336","tags":["report"]},{"url":"https://bugzilla.suse.com/1110924","tags":["report"]},{"url":"https://bugzilla.suse.com/1111007","tags":["report"]},{"url":"https://bugzilla.suse.com/1111011","tags":["report"]},{"url":"https://bugzilla.suse.com/1111014","tags":["report"]},{"url":"https://bugzilla.suse.com/1112188","tags":["report"]},{"url":"https://bugzilla.suse.com/1114423","tags":["report"]},{"url":"https://bugzilla.suse.com/1114988","tags":["report"]},{"url":"https://bugzilla.suse.com/1115040","tags":["report"]},{"url":"https://bugzilla.suse.com/1115047","tags":["report"]},{"url":"https://bugzilla.suse.com/1117756","tags":["report"]},{"url":"https://bugzilla.suse.com/1123157","tags":["report"]},{"url":"https://bugzilla.suse.com/1126140","tags":["report"]},{"url":"https://bugzilla.suse.com/1126141","tags":["report"]},{"url":"https://bugzilla.suse.com/1126192","tags":["report"]},{"url":"https://bugzilla.suse.com/1126195","tags":["report"]},{"url":"https://bugzilla.suse.com/1126196","tags":["report"]},{"url":"https://bugzilla.suse.com/1126201","tags":["report"]},{"url":"https://bugzilla.suse.com/1129623","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2018-10839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17958","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-17963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-18849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19961","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19962","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-9824","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190827-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1027519","tags":["report"]},{"url":"https://bugzilla.suse.com/1105528","tags":["report"]},{"url":"https://bugzilla.suse.com/1108940","tags":["report"]},{"url":"https://bugzilla.suse.com/1115045","tags":["report"]},{"url":"https://bugzilla.suse.com/1126198","tags":["report"]},{"url":"https://bugzilla.suse.com/1127400","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2018-19965","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190891-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1026236","tags":["report"]},{"url":"https://bugzilla.suse.com/1069468","tags":["report"]},{"url":"https://bugzilla.suse.com/1119161","tags":["report"]},{"url":"https://bugzilla.suse.com/1120067","tags":["report"]},{"url":"https://bugzilla.suse.com/1126197","tags":["report"]},{"url":"https://bugzilla.suse.com/1126325","tags":["report"]},{"url":"https://bugzilla.suse.com/1127620","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20190921-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-201913962-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1109544","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-201914001-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1031382","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-201914011-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2019/suse-su-20192223-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1096726","tags":["report"]},{"url":"https://bugzilla.suse.com/1123387","tags":["report"]},{"url":"https://bugzilla.suse.com/1135460","tags":["report"]},{"url":"https://bugzilla.suse.com/1136974","tags":["report"]},{"url":"https://bugzilla.suse.com/1137860","tags":["report"]},{"url":"https://bugzilla.suse.com/1143386","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2018-15664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-10152","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20200844-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1154790","tags":["report"]},{"url":"https://bugzilla.suse.com/1161066","tags":["report"]},{"url":"https://bugzilla.suse.com/1162729","tags":["report"]},{"url":"https://bugzilla.suse.com/1163018","tags":["report"]},{"url":"https://bugzilla.suse.com/1165776","tags":["report"]},{"url":"https://bugzilla.suse.com/1166240","tags":["report"]},{"url":"https://bugzilla.suse.com/1166379","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-20382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-1711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-7039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8608","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20200845-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1156642","tags":["report"]},{"url":"https://bugzilla.suse.com/1156794","tags":["report"]},{"url":"https://bugzilla.suse.com/1158880","tags":["report"]},{"url":"https://bugzilla.suse.com/1162161","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-202014396-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1146873","tags":["report"]},{"url":"https://bugzilla.suse.com/1149811","tags":["report"]},{"url":"https://bugzilla.suse.com/1170940","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2019-12068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-1983","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20201501-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20201514-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20201523-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20201526-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2020/suse-su-20201538-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1160024","tags":["report"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-202114706-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1172383","tags":["report"]},{"url":"https://bugzilla.suse.com/1172384","tags":["report"]},{"url":"https://bugzilla.suse.com/1172385","tags":["report"]},{"url":"https://bugzilla.suse.com/1172478","tags":["report"]},{"url":"https://bugzilla.suse.com/1175441","tags":["report"]},{"url":"https://bugzilla.suse.com/1176673","tags":["report"]},{"url":"https://bugzilla.suse.com/1176682","tags":["report"]},{"url":"https://bugzilla.suse.com/1176684","tags":["report"]},{"url":"https://bugzilla.suse.com/1178934","tags":["report"]},{"url":"https://bugzilla.suse.com/1179467","tags":["report"]},{"url":"https://bugzilla.suse.com/1181108","tags":["report"]},{"url":"https://bugzilla.suse.com/1182137","tags":["report"]},{"url":"https://bugzilla.suse.com/1182425","tags":["report"]},{"url":"https://bugzilla.suse.com/1182577","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2014-3689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-1779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-12829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-14364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25625","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20257","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2019-6778","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3923-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2018-16867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-16872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-19489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2018-20216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2019-3812","tags":["report"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/CFHQEGEI3EZECFQN4HM6ST73KWNYQDTG/#CFHQEGEI3EZECFQN4HM6ST73KWNYQDTG","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/IPOWPMYYK3WJSOVNKFMAIQ3WHQED7KOC/#IPOWPMYYK3WJSOVNKFMAIQ3WHQED7KOC","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/S5VG234WOT345KSVGE32CW6SK7I55AZP/","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2014-0222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2014-8106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-5225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-6855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-8504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2015-8619","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10028","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-10155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-1714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-6836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-7995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-8910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-10806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-11434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-13711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-14167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-15289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2630","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-5973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-6058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7493","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-11806","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-12207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-15746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-20815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-3639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-03812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-11135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-12155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-13164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-14378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-8934","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-11869","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-13800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-16092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-17380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-25085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-27821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-29129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-20263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3545","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-3682","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2019-6778","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2019-03-17T18:00:46Z","modified":"2024-08-04T20:31:04.394Z","updated_at":"2026-11-02T14:20:23.381621Z"}],"euvd":[{"id":"EUVD-2019-16336","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2019-03-17T18:00:46Z","modified":"2024-08-04T20:31:04Z","updated_at":"2026-11-03T03:06:48.069977Z"}],"ghsa":[{"id":"GHSA-4wxm-q46g-3mcf","title":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2022-05-13T01:22:46Z","modified":"2023-02-01T05:06:54Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T14:50:26.86128Z"}],"nvd":[{"id":"CVE-2019-6778","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2019-03-21T16:01:10.203Z","modified":"2026-06-17T02:39:39.663Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":4.6,"vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-787"],"updated_at":"2026-11-02T14:05:07.268578Z"}],"osv":[{"id":"BELL-CVE-2019-6778","title":"CVE-2019-6778 does not affect BellSoft software","status":"withdrawn","published":"2019-03-21T16:01:00Z","modified":"2026-01-26T09:49:36.602754Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:15.340685Z"},{"id":"CVE-2019-6778","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2019-03-21T16:01:10.203Z","modified":"2026-10-24T10:30:29.885784848Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:12.675558Z"},{"id":"DEBIAN-CVE-2019-6778","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2019-03-21T16:01:10.203Z","modified":"2026-09-21T07:03:23.025565676Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:32.57265Z"},{"id":"RHSA-2019:1883","title":"Red Hat Security Advisory: qemu-kvm security update","status":"published","published":"2024-09-13T21:59:47Z","modified":"2026-06-29T10:25:38Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:06.0195Z"},{"id":"RHSA-2019:1968","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T21:59:35Z","modified":"2026-06-29T10:25:45Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:06.0195Z"},{"id":"RHSA-2019:2425","title":"Red Hat Security Advisory: qemu-kvm-rhev security and bug fix update","status":"published","published":"2024-09-13T22:00:54Z","modified":"2026-06-28T10:31:16Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:06.0195Z"},{"id":"RHSA-2019:2892","title":"Red Hat Security Advisory: qemu-kvm security update","status":"published","published":"2024-09-16T02:55:49Z","modified":"2026-07-01T10:05:33Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:06.0195Z"},{"id":"UBUNTU-CVE-2019-6778","description":"In QEMU 3.0.0, tcp_emu in slirp/tcp_subr.c has a heap-based buffer overflow.","status":"published","published":"2019-01-25T00:00:00Z","modified":"2026-02-04T02:20:27.278513Z","cvss":[{"version":"3.0","score":7.8,"vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:21.741399Z"},{"id":"DLA-1694-1","title":"qemu - security update","status":"published","published":"2019-02-28T00:00:00Z","modified":"2026-03-09T01:23:03.630637Z","updated_at":"2026-11-02T15:46:09.777694Z"},{"id":"DSA-4454-1","title":"qemu - security update","status":"published","published":"2019-05-30T00:00:00Z","modified":"2026-03-09T02:10:53.225814Z","updated_at":"2026-11-02T15:46:16.862196Z"},{"id":"openSUSE-SU-2019:0254-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n- CVE-2018-18954: Fixed a denial of service vulnerability related to PowerPC PowerNV memory operations (bsc#1114957).\n\nNon-security issues fixed:\n\n- Improved disk performance for qemu on xen (bsc#1100408).\n- Fixed xen offline migration (bsc#1079730, bsc#1101982, bsc#1063993).\n- Fixed pwrite64/pread64/write to return 0 over -1 for a zero length NULL buffer in qemu (bsc#1121600).\n- Use /bin/bash to echo value into sys fs for ksm control (bsc#1112646).\n- Return specification exception for unimplemented diag 308 subcodes rather than a hardware error (bsc#1123179).\n\nThis update was imported from the SUSE:SLE-15:Update update project.","status":"published","published":"2019-03-23T11:07:37Z","modified":"2026-02-04T03:39:38.502397Z","updated_at":"2026-11-02T16:58:30.39372Z"},{"id":"openSUSE-SU-2019:2044-1","title":"Security update for podman, slirp4netns and libcontainers-common","description":"\n  \nThis is a version update for podman to version 1.4.4 (bsc#1143386).\n\nAdditional changes by SUSE on top:\n\n- Remove fuse-overlayfs because it's (currently) an unsatisfied dependency on\n  SLE (bsc#1143386)\n- Update libpod.conf to use correct infra_command\n- Update libpod.conf to use better versioned pause container\n- Update libpod.conf to use official kubic pause container\n- Update libpod.conf to match latest features set:\n  detach_keys, lock_type, runtime_supports_json\n- Add podman-remote varlink client\n\nVersion update podman to v1.4.4:\n\n- Features\n\n  - Podman now has greatly improved support for containers using multiple OCI\n    runtimes. Containers now remember if they were created with a different\n    runtime using --runtime and will always use that runtime\n  - The cached and delegated options for volume mounts are now allowed for\n    Docker compatability (#3340)\n  - The podman diff command now supports the --latest flag\n\n- Bugfixes\n\n  - Fixed a bug where rootless Podman would attempt to use the entire root\n    configuration if no rootless configuration was present for the user,\n    breaking rootless Podman for new installations\n  - Fixed a bug where rootless Podman's pause process would block SIGTERM,\n    preventing graceful system shutdown and hanging until the system's init\n    send SIGKILL\n  - Fixed a bug where running Podman as root with sudo -E would not work after\n    running rootless Podman at least once\n  - Fixed a bug where options for tmpfs volumes added with the --tmpfs flag\n    were being ignored\n  - Fixed a bug where images with no layers could not properly be displayed\n    and removed by Podman\n  - Fixed a bug where locks were not properly freed on failure to create a\n    container or pod\n  - Fixed a bug where podman cp on a single file would create a directory at\n    the target and place the file in it (#3384)\n  - Fixed a bug where podman inspect --format '{{.Mounts}}' would print a\n    hexadecimal address instead of a container's mounts\n  - Fixed a bug where rootless Podman would not add an entry to container's\n    /etc/hosts files for their own hostname (#3405)\n  - Fixed a bug where podman ps --sync would segfault (#3411)\n  - Fixed a bug where podman generate kube would produce an invalid ports\n    configuration (#3408)\n\n- Misc\n\n  - Updated containers/storage to v1.12.13\n  - Podman now performs much better on systems with heavy I/O load\n  - The --cgroup-manager flag to podman now shows the correct default setting\n    in help if the default was overridden by libpod.conf\n  - For backwards compatability, setting --log-driver=json-file in podman run\n    is now supported as an alias for --log-driver=k8s-file. This is considered\n    deprecated, and json-file will be moved to a new implementation in the\n    future ([#3363](https://github.com/containers/libpo\\\n    d/issues/3363))\n  - Podman's default libpod.conf file now allows the crun OCI runtime to be\n    used if it is installed\n\nUpdate podman to v1.4.2:\n\n- Fixed a bug where Podman could not run containers using an older version of\n  Systemd as init\n- Updated vendored Buildah to v1.9.0 to resolve a critical bug with\n  Dockerfile RUN instructions\n- The error message for running podman kill on containers that are not\n  running has been improved\n- Podman remote client can now log to a file if syslog is not available\n- The podman exec command now sets its error code differently based on\n  whether the container does not exist, and the command in the container does\n  not exist\n- The podman inspect command on containers now outputs Mounts JSON that matches\n  that of docker inspect, only including user-specified volumes and\n  differentiating bind mounts and named volumes\n- The podman inspect command now reports the path to a container's OCI spec\n  with the OCIConfigPath key (only included when the container is initialized\n  or running)\n- The podman run --mount command now supports the bind-nonrecursive option for\n  bind mounts\n- Fixed a bug where podman play kube would fail to create containers due to an\n  unspecified log driver\n- Fixed a bug where Podman would fail to build with musl libc\n- Fixed a bug where rootless Podman using slirp4netns networking in an\n  environment with no nameservers on the host other than localhost would\n  result in nonfunctional networking\n- Fixed a bug where podman import would not properly set environment\n  variables, discarding their values and retaining only keys\n- Fixed a bug where Podman would fail to run when built with Apparmor support\n  but run on systems without the Apparmor kernel module loaded\n- Remote Podman will now default the username it uses to log in to remote\n  systems to the username of the current user\n- Podman now uses JSON logging with OCI runtimes that support it, allowing for\n  better error reporting\n- Updated vendored containers/image to v2.0\n- Update conmon to v0.3.0\n- Support OOM Monitor under cgroup V2\n- Add config binary and make target for configuring conmon with a go library\n  for importing values\n\nUpdated podman to version 1.4.0 (bsc#1137860) and (bsc#1135460) \n\n- Podman checkpoint and podman restore commands can now be\n  used to migrate containers between Podman installations on\n  different systems.\n- The podman cp now supports pause flag.\n- The remote client now supports a configuration file for\n  pre-configuring connections to remote Podman installations\n- CVE-2019-10152: Fixed an iproper dereference of symlinks of the\n  the podman cp command which introduced in version 1.1.0 (bsc#1136974).\n- Fixed a bug where podman commit could improperly set environment variables \n  that contained = characters\n- Fixed a bug where rootless podman would sometimes fail to start\n  containers with forwarded ports\n- Fixed a bug where podman version on the remote client could\n  segfault\n- Fixed a bug where podman container runlabel would use /proc/self/exe instead of \n  the path of the Podman command when printing the command being executed\n- Fixed a bug where filtering images by label did not work\n- Fixed a bug where specifying a bing mount or tmpfs mount over\n  an image volume would cause a container to be unable to start\n- Fixed a bug where podman generate kube did not work with\n  containers with named volumes\n- Fixed a bug where rootless podman would receive permission\n  denied errors accessing conmon.pid\n- Fixed a bug where podman cp with a folder specified as target\n  would replace the folder, as opposed to copying into it\n- Fixed a bug where rootless Podman commands could double-unlock\n  a lock, causing a crash\n- Fixed a bug where podman incorrectly set tmpcopyup on /dev/\n  mounts, causing errors when using the Kata containers runtime\n- Fixed a bug where podman exec would fail on older kernels\n- Podman commit command is now usable with the Podman remote client\n- Signature-policy flag has been deprecated\n- Updated vendored containers/storage and containers/image libraries \n  with numerous bugfixes\n- Updated vendored Buildah to v1.8.3\n- Podman now requires Conmon v0.2.0\n- The podman cp command is now aliased as podman container cp\n- Rootless podman will now default init_path using root Podman's\n  configuration files (/etc/containers/libpod.conf and\n  /usr/share/containers/libpod.conf) if not overridden in the\n  rootless configuration\n- Added fuse-overlayfs dependency to support overlay based rootless image\n  manipulations\n- The podman cp command can now read input redirected to STDIN, and output to\n  STDOUT instead of a file, using - instead of an argument.\n- The podman remote client now displays version information from both the\n  client and server in podman version\n- The podman unshare command has been added, allowing easy entry into the\n  user namespace set up by rootless Podman (allowing the removal of files\n  created by rootless podman, among other things)\n- Fixed a bug where Podman containers with the --rm flag were removing\n  created volumes when they were automatically removed\n- Fixed a bug where container and pod locks were incorrectly marked as\n  released after a system reboot, causing errors on container and pod removal\n- Fixed a bug where Podman pods could not be removed if any container in the\n  pod encountered an error during removal\n- Fixed a bug where Podman pods run with the cgroupfs CGroup driver would encounter \n  a race condition during removal, potentially failing to remove the pod CGroup\n- Fixed a bug where the podman container checkpoint and podman container\n  restore commands were not visible in the remote client\n- Fixed a bug where podman remote ps --ns would not print the container's namespaces\n- Fixed a bug where removing stopped containers with healthchecks could cause an error\n- Fixed a bug where the default libpod.conf file was causing parsing errors\n- Fixed a bug where pod locks were not being freed when pods were removed,\n  potentially leading to lock exhaustion\n- Fixed a bug where 'podman run' with SD_NOTIFY set could, on short-running\n  containers, create an inconsistent state rendering the container unusable\n- The remote Podman client now uses the Varlink bridge to establish remote\n  connections by default\n- Fixed an issue with apparmor_parser (bsc#1123387)\n\n- Update to libpod v1.4.0 (bsc#1137860):\n- The podman checkpoint and podman restore commands can now be\n  used to migrate containers between Podman installations on\n  different systems\n- The podman cp command now supports a pause flag to pause\n  containers while copying into them\n- The remote client now supports a configuration file for\n  pre-configuring connections to remote Podman installations\n- Fixed CVE-2019-10152 - The podman cp command improperly\n  dereferenced symlinks in host context\n- Fixed a bug where podman commit could improperly set\n  environment variables that contained = characters\n- Fixed a bug where rootless Podman would sometimes fail to start\n  containers with forwarded ports\n- Fixed a bug where podman version on the remote client could\n  segfault\n- Fixed a bug where podman container runlabel would use\n  /proc/self/exe instead of the path of the Podman command when\n  printing the command being executed\n- Fixed a bug where filtering images by label did not work\n- Fixed a bug where specifying a bing mount or tmpfs mount over\n  an image volume would cause a container to be unable to start\n- Fixed a bug where podman generate kube did not work with\n  containers with named volumes\n- Fixed a bug where rootless Podman would receive permission\n  denied errors accessing conmon.pid\n- Fixed a bug where podman cp with a folder specified as target\n  would replace the folder, as opposed to copying into it\n- Fixed a bug where rootless Podman commands could double-unlock\n  a lock, causing a crash\n- Fixed a bug where Podman incorrectly set tmpcopyup on /dev/\n  mounts, causing errors when using the Kata containers runtime\n- Fixed a bug where podman exec would fail on older kernels\n- The podman commit command is now usable with the Podman remote\n  client\n- The --signature-policy flag (used with several image-related\n  commands) has been deprecated\n- The podman unshare command now defines two environment\n  variables in the spawned shell: CONTAINERS_RUNROOT and\n  CONTAINERS_GRAPHROOT, pointing to temporary and permanent\n  storage for rootless containers\n- Updated vendored containers/storage and containers/image\n  libraries with numerous bugfixes\n- Updated vendored Buildah to v1.8.3\n- Podman now requires Conmon v0.2.0\n- The podman cp command is now aliased as podman container cp\n- Rootless Podman will now default init_path using root Podman's\n  configuration files (/etc/containers/libpod.conf and\n  /usr/share/containers/libpod.conf) if not overridden in the\n  rootless configuration\n\n- Update to image v1.5.1\n- Vendor in latest containers/storage\n- docker/docker_client: Drop redundant Domain(ref.ref) call\n- pkg/blobinfocache: Split implementations into subpackages\n- copy: progress bar: show messages on completion\n- docs: rename manpages to *.5.command\n- add container-certs.d.md manpage\n- pkg/docker/config: Bring auth tests from\n  docker/docker_client_test\n- Don't allocate a sync.Mutex separately\n\nUpdate to storage v1.12.10:\n\n- Add function to parse out mount options from graphdriver\n- Merge the disparate parts of all of the Unix-like lockfiles\n- Fix unix-but-not-Linux compilation\n- Return XDG_RUNTIME_DIR as RootlessRuntimeDir if set\n- Cherry-pick moby/moby #39292 for CVE-2018-15664 fixes\n- lockfile: add RecursiveLock() API\n- Update generated files\n- Fix crash on tesing of aufs code\n- Let consumers know when Layers and Images came from read-only stores\n- chown: do not change owner for the mountpoint\n- locks: correctly mark updates to the layers list\n- CreateContainer: don't worry about mapping layers unless necessary\n- docs: fix manpage for containers-storage.conf\n- docs: sort configuration options alphabetically\n- docs: document OSTree file deduplication\n- Add missing options to man page for containers-storage\n- overlay: use the layer idmapping if present\n- vfs: prefer layer custom idmappings\n- layers: propagate down the idmapping settings\n- Recreate symlink when not found\n- docs: fix manpage for configuration file\n- docs: add special handling for manpages in sect 5\n- overlay: fix single-lower test\n- Recreate symlink when not found\n- overlay: propagate errors from mountProgram\n- utils: root in a userns uses global conf file\n- Fix handling of additional stores\n- Correctly check permissions on rootless directory\n- Fix possible integer overflow on 32bit builds\n- Evaluate device path for lvm\n- lockfile test: make concurrent RW test determinisitc\n- lockfile test: make concurrent read tests deterministic\n- drivers.DirCopy: fix filemode detection\n- storage: move the logic to detect rootless into utils.go\n- Don't set (struct flock).l_pid\n- Improve documentation of getLockfile\n- Rename getLockFile to createLockerForPath, and document it\n- Add FILES section to containers-storage.5 man page\n- add digest locks\n- drivers/copy: add a non-cgo fallback\n\nslirp4netns was updated to 0.3.0:\n\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() (bsc#1123156)\n\nThis update also includes:\n\n- fuse3 and fuse-overlayfs to support rootless containers.\n\nThis update was imported from the SUSE:SLE-15-SP1:Update update project.","status":"published","published":"2019-09-01T18:18:38Z","modified":"2026-02-04T03:16:17.832304Z","updated_at":"2026-11-02T16:58:30.784344Z"},{"id":"openSUSE-SU-2020:0468-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\n- CVE-2020-7039: Fixed a heap buffer overflow in tcp_emu() routine while emulating IRC and\n  other protocols (bsc#1161066).\n- CVE-2019-15034: Fixed a buffer overflow in hw/display/bochs-display.c due to improper PCI \n  config space allocation (bsc#1166379).\n- CVE-2020-1711: Fixed an out of bounds heap buffer access iscsi_co_block_status() routine\n  which could have allowed a remote denial of service or arbitrary code with privileges \n  of the QEMU process on the host (bsc#1166240).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() routine while emulating \n  the identification protocol and copying message data to a socket buffer (bsc#1123156).\n- CVE-2020-8608: Fixed a heap buffer overflow in tcp_emu() routine while emulating IRC and\n  other protocols (bsc#1163018).\n- CVE-2019-20382: Fixed a memory leak in the VNC display driver which could have led to \n  exhaustion of the host memory leading to a potential Denial of service (bsc#1165776).\n- Fixed a live migration error (bsc#1154790).\n- Fixed an issue where migrating VMs on KVM gets missing features:ospke error (bsc#1162729).\n\nThis update was imported from the SUSE:SLE-15-SP1:Update update project.","status":"published","published":"2020-04-06T22:21:00Z","modified":"2026-02-04T03:44:39.681607Z","updated_at":"2026-11-02T16:58:31.152112Z"},{"id":"openSUSE-SU-2024:11287-1","title":"qemu-6.1.0-32.1 on GA media","description":"These are all security issues fixed in the qemu-6.1.0-32.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2025-05-07T18:08:57.481645Z","updated_at":"2026-11-02T16:58:34.894275Z"},{"id":"openSUSE-SU-2024:11387-1","title":"slirp4netns-1.1.11-1.2 on GA media","description":"These are all security issues fixed in the slirp4netns-1.1.11-1.2 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:37:25.698814Z","updated_at":"2026-11-02T16:58:35.195147Z"},{"id":"SUSE-SU-2019:0423-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n- CVE-2018-18954: Fixed a denial of service vulnerability related to PowerPC PowerNV memory operations (bsc#1114957).\n\nNon-security issues fixed:\n\n- Improved disk performance for qemu on xen (bsc#1100408).\n- Fixed xen offline migration (bsc#1079730, bsc#1101982, bsc#1063993).\n- Fixed pwrite64/pread64/write to return 0 over -1 for a zero length NULL buffer in qemu (bsc#1121600).\n- Use /bin/bash to echo value into sys fs for ksm control (bsc#1112646).\n- Return specification exception for unimplemented diag 308 subcodes rather than a hardware error (bsc#1123179).\n","status":"published","published":"2019-02-18T15:26:50Z","modified":"2026-02-04T04:22:58.164555Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0435-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n- CVE-2018-18954: Fixed a denial of service vulnerability related to PowerPC PowerNV memory operations (bsc#1114957).\n\nNon-security issues fixed:\n\n- Improved disk performance for qemu on xen (bsc#1100408).\n- Fixed xen offline migration (bsc#1079730, bsc#1101982, bsc#1063993).\n- Fixed pwrite64/pread64/write to return 0 over -1 for a zero length NULL buffer in qemu (bsc#1121600).\n- Use /bin/bash to echo value into sys fs for ksm control (bsc#1112646).\n- Return specification exception for unimplemented diag 308 subcodes rather than a hardware error (bsc#1123179).\n","status":"published","published":"2019-02-19T12:12:38Z","modified":"2026-02-04T02:22:49.786112Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0457-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n* CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n","status":"published","published":"2019-02-21T06:07:42Z","modified":"2026-02-04T04:27:54.624216Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0471-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issue fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n","status":"published","published":"2019-02-22T12:47:28Z","modified":"2026-02-04T04:36:52.806007Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0471-2","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issue fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n","status":"published","published":"2019-04-27T15:57:03Z","modified":"2026-02-04T04:13:34.437584Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0489-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n- CVE-2018-7858: Fixed a denial of service which could occur while updating the VGA display, after guest has adjusted the display dimensions (bsc#1084604).\n- CVE-2017-13673: Fixed a denial of service in the cpu_physical_memory_snapshot_get_dirty function.\n- CVE-2017-13672: Fixed a denial of service via vectors involving display update.\n\nNon-security issues fixed:\n\n- Fixed bad guest time after migration (bsc#1113231).\n","status":"published","published":"2019-02-26T07:40:31Z","modified":"2026-02-04T03:59:44.996909Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0582-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity vulnerabilities addressed:\n\n- CVE-2019-6778: Fixed an out-of-bounds access in slirp (bsc#1123156)\n- CVE-2018-16872: Fixed a host security vulnerability related to handling symlinks in usb-mtp (bsc#1119493)\n- CVE-2018-19489: Fixed a Denial-of-Service in virtfs (bsc#1117275)\n- CVE-2018-19364: Fixed an use-after-free vulnerability if virtfs interface is deliberately abused (bsc#1116717)\n- CVE-2018-18954: Fixed an out-of-bounds access performing PowerNV memory operations (bsc#1114957)\n- CVE-2017-13673: Fixed a reachable assert failure during during display update (bsc#1056386)\n- CVE-2017-13672: Fixed an out-of-bounds read access during display update (bsc#1056334)\n- CVE-2018-7858: Fixed an out-of-bounds access in cirrus when updating vga display allowing for Denial-of-Service (bsc#1084604)\n\nOther bug fixes and changes:\n\n- Fix pwrite64/pread64/write to return 0 over -1 for a zero length NULL buffer in qemu (bsc#1121600)\n- Fix bad guest time after migration (bsc#1113231)\n","status":"published","published":"2019-03-11T17:34:20Z","modified":"2025-05-02T04:06:23.528007Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0825-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed: \n\n- CVE-2018-18849: Fixed an out of bounds memory access issue that was found in the LSI53C895A SCSI Host Bus Adapter \n  emulation while writing a message in lsi_do_msgin. It could occur during migration if the 'msg_len' field has an invalid \n  value. A user/process could use this flaw to crash the Qemu process resulting in DoS (bsc#1114423).\n- CVE-2018-19967: Fixed HLE constructs that allowed guests to lock up the host,\n  resulting in a Denial of Service (DoS). (XSA-282) (bsc#1114988)\n- CVE-2018-19665: Fixed an integer overflow in Bluetooth routines allows memory corruption (bsc#1117756).\n- CVE-2018-18438: Fixed an integer overflow in ccid_card_vscard_read function which allows memory corruption (bsc#1112188).\n- CVE-2018-17962: Fixed a Buffer Overflow in pcnet_receive in hw/net/pcnet.c because an incorrect integer data type is used (bsc#1111011).\n- Fixed an issue which could allow a malicious unprivileged guest userspace process to escalate its privilege \n  to that of other userspace processes in the same guest and potentially thereby to that \n  of the guest operating system (bsc#1126201).\n- CVE-2018-19961 CVE-2018-19962: Fixed insufficient TLB flushing / improper large page mappings with AMD IOMMUs (XSA-275)(bsc#1115040).\n- CVE-2018-17963: Fixed qemu_deliver_packet_iov in net/net.c that accepts packet sizes greater than INT_MAX, which allows attackers \n  to cause a denial of service or possibly have unspecified other impact. (bsc#1111014)\n- Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own \n  pagetables leading to privilege escalation (bsc#1126195).\n- Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service\n  attack affecting the whole system (bsc#1126196)\n- CVE-2018-17958: Fixed a Buffer Overflow in rtl8139_do_receive in hw/net/rtl8139.c because an incorrect integer data type is used (bsc#1111007).\n- CVE-2018-10839: Fixed an integer overflow which could lead to a buffer overflow issue (bsc#1110924).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).\n- CVE-2018-19966: Fixed issue introduced by XSA-240 that could have caused conflicts with shadow paging (XSA-280)(bsc#1115047).\n- CVE-2017-13672: Fixed an out of bounds read access during display update (bsc#1056336).\n- Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow\n  a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).\n- Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to  be able to \n  escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory \n  leaks were also possible (bsc#1126140).\n- Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that \n  of the hypervisor (bsc#1126141).\n- CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process \n  to read uninitialised stack memory contents (bsc#1129623).\n","status":"published","published":"2019-04-01T09:25:46Z","modified":"2026-02-04T02:54:24.888199Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0827-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).\n- CVE-2017-13672: Fixed an out of bounds read access during display update (bsc#1056336).\n- Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to  be able to \n  escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory \n  leaks were also possible (bsc#1126140)\n- Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that \n  of the hypervisor (bsc#1126141).\n- CVE-2018-18849: Fixed an out of bounds msg buffer access which could lead to denial of service (bsc#1114423).  \n- Fixed an issue which could allow a malicious unprivileged guest userspace process to escalate its privilege \n  to that of other userspace processes in the same guest and potentially thereby to that \n  of the guest operating system (bsc#1126201).  \n- CVE-2018-17958: Fixed an integer overflow leading to a buffer overflow in the\n  rtl8139 component (bsc#1111007)\n- CVE-2018-19967: Fixed HLE constructs that allowed guests to lock up the host,\n  resulting in a Denial of Service (DoS). (XSA-282) (bsc#1114988)  \n- CVE-2018-19665: Fixed an integer overflow resulting in memory corruption in\n  various Bluetooth functions, allowing this to crash qemu process resulting in\n  Denial of Service (DoS). (bsc#1117756).\n- CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process \n  to read uninitialised stack memory contents (bsc#1129623).\n- CVE-2018-19961, CVE-2018-19962: Fixed an issue related to insufficient TLB\n  flushing with AMD IOMMUs, which potentially allowed a guest to escalate its\n  privileges, may cause a Denial of Service (DoS) affecting the entire host, or\n  may be able to access data it is not supposed to access. (XSA-275)\n  (bsc#1115040)\n- CVE-2018-19966: Fixed an issue related to a previous fix for XSA-240, which\n  conflicted with shadow paging and allowed a guest to cause Xen to crash,\n  resulting in a Denial of Service (DoS) (XSA-280) (bsc#1115047).\n- CVE-2018-10839: Fixed an integer overflow leading to a buffer overflow in\n  the ne2000 component (bsc#1110924).\n- CVE-2018-19965: Fixed an issue related to the INVPCID instruction in case\n  non-canonical addresses are accessed, which may allow a guest to cause Xen to\n  crash, resulting in a Denial of Service (DoS) affecting the entire host.\n  (XSA-279) (bsc#1115045).\n- Fixed an issue which could allow malicious 64bit PV guests to cause a host crash (bsc#1127400).\n- Fixed an issue which could allow malicious PV guests may cause a host crash or \n  gain access to data pertaining to other guests.Additionally, vulnerable configurations \n  are likely to be unstable even in the absence of an attack (bsc#1126198).\n- Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow \n  a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).\n- CVE-2018-17963: Fixed an integer overflow in relation to large packet sizes,\n  leading to a denial of service (DoS). (bsc#1111014).\n- Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service\n  attack affecting the whole system (bsc#1126196).\n- Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own \n  pagetables leading to privilege escalation (bsc#1126195).\n- CVE-2018-17962: Fixed an integer overflow leading to a buffer overflow in the\n  pcnet component (bsc#1111011)\n- CVE-2018-18438: Fixed an integer overflow in ccid_card_vscard_read function which could lead to memory corruption (bsc#1112188).\n\nOther issues fixed: \n\n- Upstream bug fixes (bsc#1027519)\n- Fixed an issue where XEN SLE12-SP1 domU hangs on SLE12-SP3 HV1108940 (bsc#1108940).\n","status":"published","published":"2019-04-01T09:26:41Z","modified":"2026-02-04T02:52:20.568305Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0891-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed: \t  \n\n- Fixed an issue which could allow malicious PV guests may cause a host crash or \n  gain access to data pertaining to other guests.Additionally, vulnerable configurations \n  are likely to be unstable even in the absence of an attack (bsc#1126198).\n- Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow \n  a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).\n- Fixed an issue which could allow a malicious unprivileged guest userspace process to escalate its privilege \n  to that of other userspace processes in the same guest and potentially thereby to that \n  of the guest operating system (bsc#1126201).\n- Fixed an issue which could allow malicious or buggy x86 PV guest kernels to mount a Denial of Service\n  attack affecting the whole system (bsc#1126197).\n- Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own \n  pagetables leading to privilege escalation (bsc#1126195).\n- Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service\n  attack affecting the whole system (bsc#1126196).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).\n- Fixed an issue which could allow malicious 64bit PV guests to cause a host crash (bsc#1127400).\n- Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to  be able to \n  escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory \n  leaks were also possible (bsc#1126140).\n- Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that \n  of the hypervisor (bsc#1126141).\n- CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process \n  to read uninitialised stack memory contents (bsc#1129623).\n\nOther issues addressed: \n\n- Upstream bug fixes (bsc#1027519)\n- Packages should no longer use /var/adm/fillup-templates (bsc#1069468). \n- Added Xen cmdline option 'suse_vtsc_tolerance' to avoid TSC emulation for HVM domUs (bsc#1026236).\n- Fixed an issue where setup of grant_tables and other variables may fail (bsc#1126325).\n- Fixed a building issue (bsc#1119161).\n- Added a requirement for xen, xl.cfg firmware='pvgrub32|pvgrub64 (bsc#1127620).\n- Fixed a segmetation fault in Libvirt when crash triggered on top of HVM guest (bsc#1120067).\n","status":"published","published":"2019-04-05T11:32:00Z","modified":"2026-02-04T02:22:41.032877Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:0921-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed: \n\n- Fixed an issue which could allow malicious PV guests may cause a host crash or \n  gain access to data pertaining to other guests.Additionally, vulnerable configurations \n  are likely to be unstable even in the absence of an attack (bsc#1126198).\n- Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow \n  a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).\n- Fixed an issue which could allow a malicious unprivileged guest userspace process to escalate its privilege \n  to that of other userspace processes in the same guest and potentially thereby to that \n  of the guest operating system (bsc#1126201).\n- Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service\n  attack affecting the whole system (bsc#1126196).\n- Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own \n  pagetables leading to privilege escalation (bsc#1126195).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).\n- Fixed an issue which could allow malicious 64bit PV guests to cause a host crash (bsc#1127400).\n- Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to  be able to \n  escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory \n  leaks were also possible (bsc#1126140).\n- Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that \n  of the hypervisor (bsc#1126141).\n- CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process \n  to read uninitialised stack memory contents (bsc#1129623).\n- CVE-2018-19967: Fixed HLE constructs that allowed guests to lock up the host,\n  resulting in a Denial of Service (DoS). (XSA-282) (bsc#1114988)\n\nOther issue addressed: \n\n- Added Xen cmdline option 'suse_vtsc_tolerance' to avoid TSC emulation for HVM domUs (bsc#1026236).\n","status":"published","published":"2019-04-10T07:17:50Z","modified":"2026-02-04T03:05:04.834874Z","updated_at":"2026-11-02T15:53:45.926331Z"},{"id":"SUSE-SU-2019:13962-1","title":"Security update for kvm","description":"This update for kvm fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-6778: Fixed a heap buffer overflow issue in the SLiRP networking implementation (bsc#1123156).\n- CVE-2018-19489: Fixed a denial of service vulnerability in virtfs (bsc#1117275).\n- CVE-2018-19364: Fixed a use-after-free if the virtfs interface resulting in a denial of service (bsc#1116717).\n\nNon-security issue fixed:\n\n- Fixed LAPIC TSC deadline timer save/restore (bsc#1109544)\n","status":"published","published":"2019-02-15T10:43:11Z","modified":"2026-02-04T04:39:05.201406Z","updated_at":"2026-11-02T15:53:46.44301Z"},{"id":"SUSE-SU-2019:14001-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed: \n\n- Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow \n  a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).\n- Fixed an issue which could allow a malicious unprivileged guest userspace process to escalate its privilege \n  to that of other userspace processes in the same guest and potentially thereby to that \n  of the guest operating system (bsc#1126201).\n- Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own \n  pagetables leading to privilege escalation (bsc#1126195).\n- Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service\n  attack affecting the whole system (bsc#1126196).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).\n- Fixed an issue which could allow malicious PV guests may cause a host crash or \n  gain access to data pertaining to other guests.Additionally, vulnerable configurations \n  are likely to be unstable even in the absence of an attack (bsc#1126198).\n- Fixed an issue which could allow malicious 64bit PV guests to cause a host crash (bsc#1127400).\n- Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to  be able to \n  escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory \n  leaks were also possible (bsc#1126140).\n- Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that \n  of the hypervisor (bsc#1126141).\n- CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process \n  to read uninitialised stack memory contents (bsc#1129623).\n\nOther issues fixed: \n\n- Fixed an issue where VMs crashing when migrating between dom0 hosts (bsc#1031382).\n- Upstream bug fixes (bsc#1027519)\n","status":"published","published":"2019-04-01T09:26:17Z","modified":"2026-02-04T04:04:59.862631Z","updated_at":"2026-11-02T15:53:46.44301Z"},{"id":"SUSE-SU-2019:14011-1","title":"Security update for xen","description":"This update for xen fixes the following issues:\n\nSecurity issues fixed: \n\n- CVE-2018-19965: Fixed an issue related to the INVPCID instruction in case\n  non-canonical addresses are accessed, which may allow a guest to cause Xen to\n  crash, resulting in a Denial of Service (DoS) affecting the entire host.\n  (XSA-279) (bsc#1115045)\n- CVE-2018-18849: Fixed an out of bounds memory access issue was found in the \n  LSI53C895A SCSI Host Bus Adapter emulation while writing a message in lsi_do_msgin (bsc#1114423).\n- CVE-2018-19665: Fixed an integer overflow resulting in memory corruption in\n  various Bluetooth functions, allowing this to crash qemu process resulting in\n  Denial of Service (DoS). (bsc#1117756).\n- CVE-2018-18438: Fixed an integer overflow in ccid_card_vscard_read function which could allow memory corruption (bsc#1112188).\n- CVE-2018-17962: Fixed an integer overflow leading to a buffer overflow in the\n  pcnet component (bsc#1111011)\n- CVE-2018-17963: Fixed an integer overflow in relation to large packet sizes,\n  leading to a denial of service (DoS). (bsc#1111014)\n- Fixed an issue which could allow an untrusted PV domain with access to a physical device to DMA into its own \n  pagetables leading to privilege escalation (bsc#1126195).\n- Fixed an issue which could allow a malicious or buggy x86 PV guest kernels can mount a Denial of Service\n  attack affecting the whole system (bsc#1126196).\n- CVE-2018-17958: Fixed an integer overflow  which could lead to buffer overflow (bsc#1111007).\n- CVE-2018-10839: Fixed an integer overflow leading to a buffer overflow in\n  the ne2000 component (bsc#1110924).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() found in slirp (bsc#1123157).\n- CVE-2018-19966: Fixed issue introduced by XSA-240 that could have caused conflicts with shadow paging (XSA-280)(bsc#1115047).\n- CVE-2018-19967: Fixed HLE constructs that allowed guests to lock up the host,\n  resulting in a Denial of Service (DoS). (XSA-282) (bsc#1114988).\n- Fixed multiple access violations introduced by XENMEM_exchange hypercall which could allow\n  a single PV guest to leak arbitrary amounts of memory, leading to a denial of service (bsc#1126192).\n- Fixed an issue which could allow malicious or buggy guests with passed through PCI devices to  be able to \n  escalate their privileges, crash the host, or access data belonging to other guests. Additionally memory \n  leaks were also possible (bsc#1126140).\n- Fixed a race condition issue which could allow malicious PV guests to escalate their privilege to that \n  of the hypervisor (bsc#1126141).\n- CVE-2019-9824: Fixed an information leak in SLiRP networking implementation which could allow a user/process \n  to read uninitialised stack memory contents (bsc#1129623).\n","status":"published","published":"2019-04-03T09:06:19Z","modified":"2026-02-04T04:30:05.027865Z","updated_at":"2026-11-02T15:53:46.44301Z"},{"id":"SUSE-SU-2019:2223-1","title":"Security update for podman, slirp4netns and libcontainers-common","description":"\n  \nThis is a version update for podman to version 1.4.4 (bsc#1143386).\n\nAdditional changes by SUSE on top:\n\n- Remove fuse-overlayfs because it's (currently) an unsatisfied dependency on\n  SLE (bsc#1143386)\n- Update libpod.conf to use correct infra_command\n- Update libpod.conf to use better versioned pause container\n- Update libpod.conf to use official kubic pause container\n- Update libpod.conf to match latest features set:\n  detach_keys, lock_type, runtime_supports_json\n- Add podman-remote varlink client\n\nVersion update podman to v1.4.4:\n\n- Features\n\n  - Podman now has greatly improved support for containers using multiple OCI\n    runtimes. Containers now remember if they were created with a different\n    runtime using --runtime and will always use that runtime\n  - The cached and delegated options for volume mounts are now allowed for\n    Docker compatability (#3340)\n  - The podman diff command now supports the --latest flag\n\n- Bugfixes\n\n  - Fixed a bug where rootless Podman would attempt to use the entire root\n    configuration if no rootless configuration was present for the user,\n    breaking rootless Podman for new installations\n  - Fixed a bug where rootless Podman's pause process would block SIGTERM,\n    preventing graceful system shutdown and hanging until the system's init\n    send SIGKILL\n  - Fixed a bug where running Podman as root with sudo -E would not work after\n    running rootless Podman at least once\n  - Fixed a bug where options for tmpfs volumes added with the --tmpfs flag\n    were being ignored\n  - Fixed a bug where images with no layers could not properly be displayed\n    and removed by Podman\n  - Fixed a bug where locks were not properly freed on failure to create a\n    container or pod\n  - Fixed a bug where podman cp on a single file would create a directory at\n    the target and place the file in it (#3384)\n  - Fixed a bug where podman inspect --format '{{.Mounts}}' would print a\n    hexadecimal address instead of a container's mounts\n  - Fixed a bug where rootless Podman would not add an entry to container's\n    /etc/hosts files for their own hostname (#3405)\n  - Fixed a bug where podman ps --sync would segfault (#3411)\n  - Fixed a bug where podman generate kube would produce an invalid ports\n    configuration (#3408)\n\n- Misc\n\n  - Updated containers/storage to v1.12.13\n  - Podman now performs much better on systems with heavy I/O load\n  - The --cgroup-manager flag to podman now shows the correct default setting\n    in help if the default was overridden by libpod.conf\n  - For backwards compatability, setting --log-driver=json-file in podman run\n    is now supported as an alias for --log-driver=k8s-file. This is considered\n    deprecated, and json-file will be moved to a new implementation in the\n    future ([#3363](https://github.com/containers/libpo\\\n    d/issues/3363))\n  - Podman's default libpod.conf file now allows the crun OCI runtime to be\n    used if it is installed\n\nUpdate podman to v1.4.2:\n\n- Fixed a bug where Podman could not run containers using an older version of\n  Systemd as init\n- Updated vendored Buildah to v1.9.0 to resolve a critical bug with\n  Dockerfile RUN instructions\n- The error message for running podman kill on containers that are not\n  running has been improved\n- Podman remote client can now log to a file if syslog is not available\n- The podman exec command now sets its error code differently based on\n  whether the container does not exist, and the command in the container does\n  not exist\n- The podman inspect command on containers now outputs Mounts JSON that matches\n  that of docker inspect, only including user-specified volumes and\n  differentiating bind mounts and named volumes\n- The podman inspect command now reports the path to a container's OCI spec\n  with the OCIConfigPath key (only included when the container is initialized\n  or running)\n- The podman run --mount command now supports the bind-nonrecursive option for\n  bind mounts\n- Fixed a bug where podman play kube would fail to create containers due to an\n  unspecified log driver\n- Fixed a bug where Podman would fail to build with musl libc\n- Fixed a bug where rootless Podman using slirp4netns networking in an\n  environment with no nameservers on the host other than localhost would\n  result in nonfunctional networking\n- Fixed a bug where podman import would not properly set environment\n  variables, discarding their values and retaining only keys\n- Fixed a bug where Podman would fail to run when built with Apparmor support\n  but run on systems without the Apparmor kernel module loaded\n- Remote Podman will now default the username it uses to log in to remote\n  systems to the username of the current user\n- Podman now uses JSON logging with OCI runtimes that support it, allowing for\n  better error reporting\n- Updated vendored containers/image to v2.0\n- Update conmon to v0.3.0\n- Support OOM Monitor under cgroup V2\n- Add config binary and make target for configuring conmon with a go library\n  for importing values\n\nUpdated podman to version 1.4.0 (bsc#1137860) and (bsc#1135460) \n\n- Podman checkpoint and podman restore commands can now be\n  used to migrate containers between Podman installations on\n  different systems.\n- The podman cp now supports pause flag.\n- The remote client now supports a configuration file for\n  pre-configuring connections to remote Podman installations\n- CVE-2019-10152: Fixed an iproper dereference of symlinks of the\n  the podman cp command which introduced in version 1.1.0 (bsc#1136974).\n- Fixed a bug where podman commit could improperly set environment variables \n  that contained = characters\n- Fixed a bug where rootless podman would sometimes fail to start\n  containers with forwarded ports\n- Fixed a bug where podman version on the remote client could\n  segfault\n- Fixed a bug where podman container runlabel would use /proc/self/exe instead of \n  the path of the Podman command when printing the command being executed\n- Fixed a bug where filtering images by label did not work\n- Fixed a bug where specifying a bing mount or tmpfs mount over\n  an image volume would cause a container to be unable to start\n- Fixed a bug where podman generate kube did not work with\n  containers with named volumes\n- Fixed a bug where rootless podman would receive permission\n  denied errors accessing conmon.pid\n- Fixed a bug where podman cp with a folder specified as target\n  would replace the folder, as opposed to copying into it\n- Fixed a bug where rootless Podman commands could double-unlock\n  a lock, causing a crash\n- Fixed a bug where podman incorrectly set tmpcopyup on /dev/\n  mounts, causing errors when using the Kata containers runtime\n- Fixed a bug where podman exec would fail on older kernels\n- Podman commit command is now usable with the Podman remote client\n- Signature-policy flag has been deprecated\n- Updated vendored containers/storage and containers/image libraries \n  with numerous bugfixes\n- Updated vendored Buildah to v1.8.3\n- Podman now requires Conmon v0.2.0\n- The podman cp command is now aliased as podman container cp\n- Rootless podman will now default init_path using root Podman's\n  configuration files (/etc/containers/libpod.conf and\n  /usr/share/containers/libpod.conf) if not overridden in the\n  rootless configuration\n- Added fuse-overlayfs dependency to support overlay based rootless image\n  manipulations\n- The podman cp command can now read input redirected to STDIN, and output to\n  STDOUT instead of a file, using - instead of an argument.\n- The podman remote client now displays version information from both the\n  client and server in podman version\n- The podman unshare command has been added, allowing easy entry into the\n  user namespace set up by rootless Podman (allowing the removal of files\n  created by rootless podman, among other things)\n- Fixed a bug where Podman containers with the --rm flag were removing\n  created volumes when they were automatically removed\n- Fixed a bug where container and pod locks were incorrectly marked as\n  released after a system reboot, causing errors on container and pod removal\n- Fixed a bug where Podman pods could not be removed if any container in the\n  pod encountered an error during removal\n- Fixed a bug where Podman pods run with the cgroupfs CGroup driver would encounter \n  a race condition during removal, potentially failing to remove the pod CGroup\n- Fixed a bug where the podman container checkpoint and podman container\n  restore commands were not visible in the remote client\n- Fixed a bug where podman remote ps --ns would not print the container's namespaces\n- Fixed a bug where removing stopped containers with healthchecks could cause an error\n- Fixed a bug where the default libpod.conf file was causing parsing errors\n- Fixed a bug where pod locks were not being freed when pods were removed,\n  potentially leading to lock exhaustion\n- Fixed a bug where 'podman run' with SD_NOTIFY set could, on short-running\n  containers, create an inconsistent state rendering the container unusable\n- The remote Podman client now uses the Varlink bridge to establish remote\n  connections by default\n- Fixed an issue with apparmor_parser (bsc#1123387)\n\n- Update to libpod v1.4.0 (bsc#1137860):\n- The podman checkpoint and podman restore commands can now be\n  used to migrate containers between Podman installations on\n  different systems\n- The podman cp command now supports a pause flag to pause\n  containers while copying into them\n- The remote client now supports a configuration file for\n  pre-configuring connections to remote Podman installations\n- Fixed CVE-2019-10152 - The podman cp command improperly\n  dereferenced symlinks in host context\n- Fixed a bug where podman commit could improperly set\n  environment variables that contained = characters\n- Fixed a bug where rootless Podman would sometimes fail to start\n  containers with forwarded ports\n- Fixed a bug where podman version on the remote client could\n  segfault\n- Fixed a bug where podman container runlabel would use\n  /proc/self/exe instead of the path of the Podman command when\n  printing the command being executed\n- Fixed a bug where filtering images by label did not work\n- Fixed a bug where specifying a bing mount or tmpfs mount over\n  an image volume would cause a container to be unable to start\n- Fixed a bug where podman generate kube did not work with\n  containers with named volumes\n- Fixed a bug where rootless Podman would receive permission\n  denied errors accessing conmon.pid\n- Fixed a bug where podman cp with a folder specified as target\n  would replace the folder, as opposed to copying into it\n- Fixed a bug where rootless Podman commands could double-unlock\n  a lock, causing a crash\n- Fixed a bug where Podman incorrectly set tmpcopyup on /dev/\n  mounts, causing errors when using the Kata containers runtime\n- Fixed a bug where podman exec would fail on older kernels\n- The podman commit command is now usable with the Podman remote\n  client\n- The --signature-policy flag (used with several image-related\n  commands) has been deprecated\n- The podman unshare command now defines two environment\n  variables in the spawned shell: CONTAINERS_RUNROOT and\n  CONTAINERS_GRAPHROOT, pointing to temporary and permanent\n  storage for rootless containers\n- Updated vendored containers/storage and containers/image\n  libraries with numerous bugfixes\n- Updated vendored Buildah to v1.8.3\n- Podman now requires Conmon v0.2.0\n- The podman cp command is now aliased as podman container cp\n- Rootless Podman will now default init_path using root Podman's\n  configuration files (/etc/containers/libpod.conf and\n  /usr/share/containers/libpod.conf) if not overridden in the\n  rootless configuration\n\n- Update to image v1.5.1\n- Vendor in latest containers/storage\n- docker/docker_client: Drop redundant Domain(ref.ref) call\n- pkg/blobinfocache: Split implementations into subpackages\n- copy: progress bar: show messages on completion\n- docs: rename manpages to *.5.command\n- add container-certs.d.md manpage\n- pkg/docker/config: Bring auth tests from\n  docker/docker_client_test\n- Don't allocate a sync.Mutex separately\n\nUpdate to storage v1.12.10:\n\n- Add function to parse out mount options from graphdriver\n- Merge the disparate parts of all of the Unix-like lockfiles\n- Fix unix-but-not-Linux compilation\n- Return XDG_RUNTIME_DIR as RootlessRuntimeDir if set\n- Cherry-pick moby/moby #39292 for CVE-2018-15664 fixes\n- lockfile: add RecursiveLock() API\n- Update generated files\n- Fix crash on tesing of aufs code\n- Let consumers know when Layers and Images came from read-only stores\n- chown: do not change owner for the mountpoint\n- locks: correctly mark updates to the layers list\n- CreateContainer: don't worry about mapping layers unless necessary\n- docs: fix manpage for containers-storage.conf\n- docs: sort configuration options alphabetically\n- docs: document OSTree file deduplication\n- Add missing options to man page for containers-storage\n- overlay: use the layer idmapping if present\n- vfs: prefer layer custom idmappings\n- layers: propagate down the idmapping settings\n- Recreate symlink when not found\n- docs: fix manpage for configuration file\n- docs: add special handling for manpages in sect 5\n- overlay: fix single-lower test\n- Recreate symlink when not found\n- overlay: propagate errors from mountProgram\n- utils: root in a userns uses global conf file\n- Fix handling of additional stores\n- Correctly check permissions on rootless directory\n- Fix possible integer overflow on 32bit builds\n- Evaluate device path for lvm\n- lockfile test: make concurrent RW test determinisitc\n- lockfile test: make concurrent read tests deterministic\n- drivers.DirCopy: fix filemode detection\n- storage: move the logic to detect rootless into utils.go\n- Don't set (struct flock).l_pid\n- Improve documentation of getLockfile\n- Rename getLockFile to createLockerForPath, and document it\n- Add FILES section to containers-storage.5 man page\n- add digest locks\n- drivers/copy: add a non-cgo fallback\n\nslirp4netns was updated to 0.3.0:\n\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() (bsc#1123156)\n\nThis update also includes:\n\n- fuse3 and fuse-overlayfs to support rootless containers.\n","status":"published","published":"2019-08-27T13:43:02Z","modified":"2026-02-04T02:25:11.997335Z","updated_at":"2026-11-02T15:53:46.44301Z"},{"id":"SUSE-SU-2020:0844-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\n- CVE-2020-7039: Fixed a heap buffer overflow in tcp_emu() routine while emulating IRC and\n  other protocols (bsc#1161066).\n- CVE-2019-15034: Fixed a buffer overflow in hw/display/bochs-display.c due to improper PCI \n  config space allocation (bsc#1166379).\n- CVE-2020-1711: Fixed an out of bounds heap buffer access iscsi_co_block_status() routine\n  which could have allowed a remote denial of service or arbitrary code with privileges \n  of the QEMU process on the host (bsc#1166240).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() routine while emulating \n  the identification protocol and copying message data to a socket buffer (bsc#1123156).\n- CVE-2020-8608: Fixed a heap buffer overflow in tcp_emu() routine while emulating IRC and\n  other protocols (bsc#1163018).\n- CVE-2019-20382: Fixed a memory leak in the VNC display driver which could have led to \n  exhaustion of the host memory leading to a potential Denial of service (bsc#1165776).\n- Fixed a live migration error (bsc#1154790).\n- Fixed an issue where migrating VMs on KVM gets missing features:ospke error (bsc#1162729).\n","status":"published","published":"2020-04-01T14:19:10Z","modified":"2026-02-04T04:25:49.919654Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:0845-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\n- CVE-2020-7039: Fixed a heap buffer overflow in tcp_emu() routine while emulating IRC and\n  other protocols (bsc#1161066).\n- CVE-2019-15034: Fixed a buffer overflow in hw/display/bochs-display.c due to improper PCI \n  config space allocation (bsc#1166379).\n- CVE-2020-1711: Fixed an out of bounds heap buffer access iscsi_co_block_status() routine\n  which could have allowed a remote denial of service or arbitrary code with privileges \n  of the QEMU process on the host (bsc#1166240).\n- CVE-2019-6778: Fixed a heap buffer overflow in tcp_emu() routine while emulating \n  the identification protocol and copying message data to a socket buffer (bsc#1123156).\n- CVE-2020-8608: Fixed a heap buffer overflow in tcp_emu() routine while emulating IRC and\n  other protocols (bsc#1163018).\n- CVE-2019-20382: Fixed a memory leak in the VNC display driver which could have led to \n  exhaustion of the host memory leading to a potential Denial of service (bsc#1165776).\n- Fixed live migration errors (bsc#1154790, bsc#1156794, bsc#1156642).\n- Fixed an issue where migrating VMs on KVM gets missing features:ospke error (bsc#1162729).\n- Fixed an issue where booting up a guest system with mdev passthrough device as installation\n  device was failing (bsc#1158880).\n ","status":"published","published":"2020-04-01T14:19:43Z","modified":"2026-02-04T04:37:11.833722Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:14396-1","title":"Security update for kvm","description":"This update for kvm fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2019-12068: Fixed a potential DoS in the LSI SCSI controller emulation (bsc#1146873).\n- CVE-2020-1983: Fixed a use-after-free in the ip_reass function of slirp (bsc#1170940).\n- CVE-2020-8608: Fixed a potential OOB access in slirp (bsc#1163018).\n- CVE-2020-7039: Fixed a potential OOB access in slirp (bsc#1161066).\n- CVE-2019-15890: Fixed a use-after-free during packet reassembly in slirp (bsc#1149811).\n- Fixed multiple potential DoS issues in SLIRP, similar to CVE-2019-6778 (bsc#1123156).\n","status":"published","published":"2020-06-11T13:23:22Z","modified":"2026-02-04T02:47:20.950274Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:1501-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2020-1983: Fixed a use-after-free in the ip_reass function of slirp (bsc#1170940).\n- CVE-2019-20382: Fixed a potential DoS due to a memory leak in VNC disconnect (bsc#1165776).\n- CVE-2020-1711: Fixed a potential OOB access in the iSCSI client code (bsc#1166240).\n- CVE-2020-8608: Fixed a potential OOB access in slirp (bsc#1163018).\n- CVE-2020-7039: Fixed a potential OOB access in slirp (bsc#1161066).\n- Fixed multiple potential DoS issues in SLIRP, similar to CVE-2019-6778 (bsc#1123156).\n\nNon-security issue fixed:\n\n- Miscellaneous fixes to the in-package support documentation.\n","status":"published","published":"2020-05-28T14:49:43Z","modified":"2025-05-02T04:09:10.024776Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:1514-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2020-1711: Fixed a potential OOB access in the iSCSI client code (bsc#1166240).\n- CVE-2019-12068: Fixed a potential DoS in the LSI SCSI controller emulation (bsc#1146873).\n- CVE-2020-1983: Fixed a use-after-free in the ip_reass function of slirp (bsc#1170940).\n- CVE-2020-8608: Fixed a potential OOB access in slirp (bsc#1163018).\n- CVE-2020-7039: Fixed a potential OOB access in slirp (bsc#1161066).\n- CVE-2019-15890: Fixed a use-after-free during packet reassembly in slirp (bsc#1149811).\n- Fixed multiple potential DoS issues in SLIRP, similar to CVE-2019-6778 (bsc#1123156).\n","status":"published","published":"2020-06-02T08:14:29Z","modified":"2026-02-04T02:29:07.166823Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:1523-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2020-1983: Fixed a use-after-free in the ip_reass function of slirp (bsc#1170940).\n- CVE-2019-20382: Fixed a potential DoS due to a memory leak in VNC disconnect (bsc#1165776).\n- CVE-2020-1711: Fixed a potential OOB access in the iSCSI client code (bsc#1166240).\n- CVE-2020-8608: Fixed a potential OOB access in slirp (bsc#1163018).\n- CVE-2020-7039: Fixed a potential OOB access in slirp (bsc#1161066).\n- Fixed multiple potential DoS issues in SLIRP, similar to CVE-2019-6778 (bsc#1123156).\n\nNon-security issue fixed:\n\n- Miscellaneous fixes to the in-package support documentation.\n","status":"published","published":"2020-06-03T06:35:58Z","modified":"2026-02-04T02:30:48.361926Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:1526-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2020-1711: Fixed a potential OOB access in the iSCSI client code (bsc#1166240).\n- CVE-2019-12068: Fixed a potential DoS in the LSI SCSI controller emulation (bsc#1146873).\n- CVE-2020-1983: Fixed a use-after-free in the ip_reass function of slirp (bsc#1170940).\n- CVE-2020-8608: Fixed a potential OOB access in slirp (bsc#1163018).\n- CVE-2020-7039: Fixed a potential OOB access in slirp (bsc#1161066).\n- CVE-2019-15890: Fixed a use-after-free during packet reassembly in slirp (bsc#1149811).\n- Fixed multiple potential DoS issues in SLIRP, similar to CVE-2019-6778 (bsc#1123156).\n","status":"published","published":"2020-06-03T10:04:37Z","modified":"2026-02-04T02:27:15.425356Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2020:1538-1","title":"Security update for qemu","description":"This update for qemu fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2020-1711: Fixed a potential OOB access in the iSCSI client code (bsc#1166240).\n- CVE-2019-12068: Fixed a potential DoS in the LSI SCSI controller emulation (bsc#1146873).\n- CVE-2020-1983: Fixed a use-after-free in the ip_reass function of slirp (bsc#1170940).\n- CVE-2020-8608: Fixed a potential OOB access in slirp (bsc#1163018).\n- CVE-2020-7039: Fixed a potential OOB access in slirp (bsc#1161066).\n- CVE-2019-15890: Fixed a use-after-free during packet reassembly in slirp (bsc#1149811).\n- Fixed multiple potential DoS issues in SLIRP, similar to CVE-2019-6778 (bsc#1123156).\n\nNon-security issue fixed:\n\n- Make sure that required memory is mapped properly during an incoming migration of a Xen HVM domU (bsc#1160024).\n","status":"published","published":"2020-06-04T10:59:37Z","modified":"2026-02-04T04:29:27.977063Z","updated_at":"2026-11-02T15:53:47.634847Z"},{"id":"SUSE-SU-2021:14706-1","title":"Security update for kvm","description":"This update for kvm fixes the following issues:\n\n- Fix OOB read and write due to integer overflow in sm501_2d_operation() in hw/display/sm501.c (CVE-2020-12829, bsc#1172385)\n- Fix OOB access possibility in MegaRAID SAS 8708EM2 emulation (CVE-2020-13362 bsc#1172383)\n- Fix use-after-free in usb xhci packet handling (CVE-2020-25723, bsc#1178934)\n- Fix use-after-free in usb ehci packet handling (CVE-2020-25084, bsc#1176673)\n- Fix OOB access in usb hcd-ohci emulation (CVE-2020-25624, bsc#1176682)\n- Fix infinite loop (DoS) in usb hcd-ohci emulation (CVE-2020-25625, bsc#1176684)\n- Fix OOB access in atapi emulation (CVE-2020-29443, bsc#1181108)\n- Fix DoS in e1000 emulated device (CVE-2021-20257 bsc#1182577)\n- Fix OOB access in SLIRP ARP packet processing (CVE-2020-29130, bsc#1179467)\n- Fix OOB access while processing USB packets (CVE-2020-14364 bsc#1175441)\n- Fix potential privilege escalation in virtfs (CVE-2021-20181 bsc#1182137)\n- Fix package scripts to not use hard coded paths for temporary working directories and log files (bsc#1182425)\n- Fix use-after-free in slirp (CVE-2019-15890 bsc#1149811)\n- Fix for similar problems as for the original fix prompting this issue (CVE-2019-6778 bsc#1123156)\n- Fix potential OOB accesses in slirp (CVE-2020-8608 bsc#1163018 CVE-2020-7039 bsc#1161066)\n- Fix use after free in slirp (CVE-2020-1983 bsc#1170940)\n- Fix potential DOS in lsi scsi controller emulation (CVE-2019-12068 bsc#1146873)\n- Fix OOB access possibility in ES1370 audio device emulation (CVE-2020-13361 bsc#1172384)\n- Fix OOB access in ROM loading (CVE-2020-13765 bsc#1172478)\n","status":"published","published":"2021-04-23T15:32:45Z","modified":"2026-02-04T02:56:04.771314Z","updated_at":"2026-11-02T15:53:49.138643Z"},{"id":"USN-3923-1","title":"qemu vulnerabilities","description":"Michael Hanselmann discovered that QEMU incorrectly handled the Media\nTransfer Protocol (MTP). An attacker inside the guest could use this issue\nto read or write arbitrary files and cause a denial of service, or possibly\nexecute arbitrary code. This issue only affected Ubuntu 18.10.\n(CVE-2018-16867)\n\nMichael Hanselmann discovered that QEMU incorrectly handled the Media\nTransfer Protocol (MTP). An attacker inside the guest could use this issue\nto read arbitrary files, contrary to expectations. This issue only affected\nUbuntu 18.04 LTS and Ubuntu 18.10. (CVE-2018-16872)\n\nZhibin Hu discovered that QEMU incorrectly handled the Plan 9 File System\nsupport. An attacker inside the guest could use this issue to cause QEMU to\ncrash, resulting in a denial of service. (CVE-2018-19489)\n\nLi Quang and Saar Amar discovered multiple issues in the QEMU PVRDMA\ndevice. An attacker inside the guest could use these issues to cause a\ndenial of service, or possibly execute arbitrary code. This issue only\naffected Ubuntu 18.10. These issues were resolved by disabling PVRDMA\nsupport in Ubuntu 18.10. (CVE-2018-20123, CVE-2018-20124, CVE-2018-20125,\nCVE-2018-20126, CVE-2018-20191, CVE-2018-20216)\n\nMichael Hanselmann discovered that QEMU incorrectly handled certain i2c\ncommands. A local attacker could possibly use this issue to read QEMU\nprocess memory. This issue only affected Ubuntu 18.04 LTS and Ubuntu 18.10.\n(CVE-2019-3812)\n\nIt was discovered that QEMU incorrectly handled the Slirp networking\nback-end. An attacker inside the guest could use this issue to cause QEMU\nto crash, resulting in a denial of service, or possibly execute arbitrary\ncode on the host. In the default installation, when QEMU is used with\nlibvirt, attackers would be isolated by the libvirt AppArmor profile.\n(CVE-2019-6778)\n","status":"published","published":"2019-03-27T12:10:22Z","modified":"2026-02-10T04:41:29Z","updated_at":"2026-11-02T16:58:14.019824Z"}]}}