{
  "@context": {
    "@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
    "affected_products": {
      "@id": "https://www.variotdbs.pl/ref/affected_products"
    },
    "configurations": {
      "@id": "https://www.variotdbs.pl/ref/configurations"
    },
    "credits": {
      "@id": "https://www.variotdbs.pl/ref/credits"
    },
    "cvss": {
      "@id": "https://www.variotdbs.pl/ref/cvss/"
    },
    "description": {
      "@id": "https://www.variotdbs.pl/ref/description/"
    },
    "exploit_availability": {
      "@id": "https://www.variotdbs.pl/ref/exploit_availability/"
    },
    "external_ids": {
      "@id": "https://www.variotdbs.pl/ref/external_ids/"
    },
    "iot": {
      "@id": "https://www.variotdbs.pl/ref/iot/"
    },
    "iot_taxonomy": {
      "@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
    },
    "patch": {
      "@id": "https://www.variotdbs.pl/ref/patch/"
    },
    "problemtype_data": {
      "@id": "https://www.variotdbs.pl/ref/problemtype_data/"
    },
    "references": {
      "@id": "https://www.variotdbs.pl/ref/references/"
    },
    "sources": {
      "@id": "https://www.variotdbs.pl/ref/sources/"
    },
    "sources_release_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_release_date/"
    },
    "sources_update_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_update_date/"
    },
    "threat_type": {
      "@id": "https://www.variotdbs.pl/ref/threat_type/"
    },
    "title": {
      "@id": "https://www.variotdbs.pl/ref/title/"
    },
    "type": {
      "@id": "https://www.variotdbs.pl/ref/type/"
    }
  },
  "@id": "https://www.variotdbs.pl/vuln/VAR-201706-0334",
  "affected_products": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/affected_products#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "model": "linux enterprise software development kit",
        "scope": "eq",
        "trust": 1.6,
        "vendor": "suse",
        "version": "11.0"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 1.3,
        "vendor": "redhat",
        "version": "5"
      },
      {
        "model": "enterprise linux workstation",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.0"
      },
      {
        "model": "enterprise linux server tus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.6"
      },
      {
        "model": "linux enterprise for sap",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "12"
      },
      {
        "model": "linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "debian",
        "version": "9.0"
      },
      {
        "model": "web gateway",
        "scope": "gte",
        "trust": 1.0,
        "vendor": "mcafee",
        "version": "7.7.0.0"
      },
      {
        "model": "glibc",
        "scope": "lte",
        "trust": 1.0,
        "vendor": "gnu",
        "version": "2.25"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.5"
      },
      {
        "model": "enterprise linux server tus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.2"
      },
      {
        "model": "suse linux enterprise point of sale",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "novell",
        "version": "11.0"
      },
      {
        "model": "linux enterprise server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "11"
      },
      {
        "model": "enterprise linux server tus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.3"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.0"
      },
      {
        "model": "enterprise linux server tus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.5"
      },
      {
        "model": "suse linux enterprise desktop",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "novell",
        "version": "12.0"
      },
      {
        "model": "linux enterprise server for raspberry pi",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "12"
      },
      {
        "model": "linux enterprise software development kit",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "12.0"
      },
      {
        "model": "suse linux enterprise server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "novell",
        "version": "11.0"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.6"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.7"
      },
      {
        "model": "enterprise linux workstation",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.0"
      },
      {
        "model": "enterprise linux server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.0"
      },
      {
        "model": "leap",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "opensuse",
        "version": "42.2"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.2"
      },
      {
        "model": "enterprise linux server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.6"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.3"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.2"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.3"
      },
      {
        "model": "enterprise linux server long life",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "5.9"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.5"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.0"
      },
      {
        "model": "enterprise linux desktop",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.0"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.2"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.4"
      },
      {
        "model": "enterprise linux server tus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.6"
      },
      {
        "model": "linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "debian",
        "version": "8.0"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.5"
      },
      {
        "model": "linux enterprise server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "12"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "5.9"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.4"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.2"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.4"
      },
      {
        "model": "web gateway",
        "scope": "lte",
        "trust": 1.0,
        "vendor": "mcafee",
        "version": "7.6.2.14"
      },
      {
        "model": "linux enterprise server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "10"
      },
      {
        "model": "enterprise linux server aus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.6"
      },
      {
        "model": "cloud magnum orchestration",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "openstack",
        "version": "7"
      },
      {
        "model": "enterprise linux desktop",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "6.0"
      },
      {
        "model": "web gateway",
        "scope": "lte",
        "trust": 1.0,
        "vendor": "mcafee",
        "version": "7.7.2.2"
      },
      {
        "model": "enterprise linux server eus",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.6"
      },
      {
        "model": "enterprise linux server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "redhat",
        "version": "7.0"
      },
      {
        "model": "c library",
        "scope": "lte",
        "trust": 0.8,
        "vendor": "gnu",
        "version": "2.25"
      },
      {
        "model": "cloud magnum orchestration",
        "scope": null,
        "trust": 0.8,
        "vendor": "openstack",
        "version": null
      },
      {
        "model": "leap",
        "scope": null,
        "trust": 0.8,
        "vendor": "opensuse",
        "version": null
      },
      {
        "model": "linux enterprise desktop",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "linux enterprise for sap",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "linux enterprise point of sale",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "linux enterprise server",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "linux enterprise server for raspberry pi",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "linux enterprise software development kit",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "openstack cloud",
        "scope": null,
        "trust": 0.8,
        "vendor": "suse",
        "version": null
      },
      {
        "model": "enterprise linux",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux aus",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux eus",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux long life",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux server",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux server eus",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux server tus",
        "scope": null,
        "trust": 0.8,
        "vendor": "red hat",
        "version": null
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "7"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "6"
      },
      {
        "model": "vm server for",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "x863.4"
      },
      {
        "model": "vm server for",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "x863.3"
      },
      {
        "model": "linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "7"
      },
      {
        "model": "linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "6"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.7"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.7.2.2"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.4"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.3"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.2"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.14"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.1"
      },
      {
        "model": "web gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.0"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.22.90"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.12.2"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.12.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.11.2"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.11.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.10.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.2.5"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.2.4"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.2.3"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.2.2"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.2.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.2"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1.9"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1.3-10"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1.3"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1.2"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0.6"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0.5"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0.4"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0.3"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0.2"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.0"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.25"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.24"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.23"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.22"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.21"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.20"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.19"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.18"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.17"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.16"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.15"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.14.1"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.14"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.13"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.12"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.11.3"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.11"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.10"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.1.3.10"
      },
      {
        "model": "cfengine",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "1.2.3"
      },
      {
        "model": "linux sparc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux s/390",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux powerpc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux mips",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux ia-64",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux ia-32",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux ia-30",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux arm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "linux amd64",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "web gateway",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.7.2.3"
      },
      {
        "model": "web gateway",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "mcafee",
        "version": "7.6.2.15"
      }
    ],
    "sources": [
      {
        "db": "BID",
        "id": "99127"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "configurations": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/configurations#",
      "children": {
        "@container": "@list"
      },
      "cpe_match": {
        "@container": "@list"
      },
      "data": {
        "@container": "@list"
      },
      "nodes": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "cpe_match": [
              {
                "cpe22Uri": "cpe:/a:gnu:glibc",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/a:openstack:cloud_magnum_orchestration",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:opensuse_project:leap",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:suse:linux_enterprise_desktop",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:suse:linux_enterprise_for_sap",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:suse:suse_linux_enterprise_point_of_sale",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:suse:linux_enterprise_server",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:suse:linux_enterprise_server_for_raspberry_pi",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:suse:linux_enterprise_software_development_kit",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/a:suse:openstack_cloud",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux_aus",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux_eus",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux_long_life",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux_server",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux_server_eus",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:redhat:enterprise_linux_server_tus",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      }
    ]
  },
  "credits": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/credits#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "T. Weber",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      }
    ],
    "trust": 0.6
  },
  "cve": "CVE-2017-1000366",
  "cvss": {
    "@context": {
      "cvssV2": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
      },
      "cvssV3": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
      },
      "severity": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/cvss/severity#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/severity"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "cvssV2": [
          {
            "accessComplexity": "LOW",
            "accessVector": "LOCAL",
            "authentication": "NONE",
            "author": "nvd@nist.gov",
            "availabilityImpact": "COMPLETE",
            "baseScore": 7.2,
            "confidentialityImpact": "COMPLETE",
            "exploitabilityScore": 3.9,
            "id": "CVE-2017-1000366",
            "impactScore": 10.0,
            "integrityImpact": "COMPLETE",
            "severity": "HIGH",
            "trust": 1.9,
            "vectorString": "AV:L/AC:L/Au:N/C:C/I:C/A:C",
            "version": "2.0"
          },
          {
            "accessComplexity": "LOW",
            "accessVector": "LOCAL",
            "authentication": "NONE",
            "author": "VULHUB",
            "availabilityImpact": "COMPLETE",
            "baseScore": 7.2,
            "confidentialityImpact": "COMPLETE",
            "exploitabilityScore": 3.9,
            "id": "VHN-100094",
            "impactScore": 10.0,
            "integrityImpact": "COMPLETE",
            "severity": "HIGH",
            "trust": 0.1,
            "vectorString": "AV:L/AC:L/AU:N/C:C/I:C/A:C",
            "version": "2.0"
          }
        ],
        "cvssV3": [
          {
            "attackComplexity": "LOW",
            "attackVector": "LOCAL",
            "author": "nvd@nist.gov",
            "availabilityImpact": "HIGH",
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "exploitabilityScore": 1.8,
            "id": "CVE-2017-1000366",
            "impactScore": 5.9,
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "trust": 1.8,
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.0"
          }
        ],
        "severity": [
          {
            "author": "nvd@nist.gov",
            "id": "CVE-2017-1000366",
            "trust": 1.0,
            "value": "HIGH"
          },
          {
            "author": "NVD",
            "id": "CVE-2017-1000366",
            "trust": 0.8,
            "value": "High"
          },
          {
            "author": "CNNVD",
            "id": "CNNVD-201706-808",
            "trust": 0.6,
            "value": "HIGH"
          },
          {
            "author": "VULHUB",
            "id": "VHN-100094",
            "trust": 0.1,
            "value": "HIGH"
          },
          {
            "author": "VULMON",
            "id": "CVE-2017-1000366",
            "trust": 0.1,
            "value": "HIGH"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "description": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/description#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "glibc contains a vulnerability that allows specially crafted LD_LIBRARY_PATH values to manipulate the heap/stack, causing them to alias, potentially resulting in arbitrary code execution. Please note that additional hardening changes have been made to glibc to prevent manipulation of stack and heap memory but these issues are not directly exploitable, as such they have not been given a CVE. This affects glibc 2.25 and earlier. glibc Contains a buffer error vulnerability.Information is obtained, information is altered, and service operation is disrupted (DoS) There is a possibility of being put into a state. GNU glibc is prone to local memory-corruption vulnerability. \nAn attacker could exploit this  issue to execute arbitrary code in the  context of the application. \nGNU glibc 2.25 and prior versions are vulnerable. \n-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n=====================================================================\n                   Red Hat Security Advisory\n\nSynopsis:          Important: glibc security update\nAdvisory ID:       RHSA-2017:1479-01\nProduct:           Red Hat Enterprise Linux\nAdvisory URL:      https://access.redhat.com/errata/RHSA-2017:1479\nIssue date:        2017-06-19\nCVE Names:         CVE-2017-1000366 \n=====================================================================\n\n1. Summary:\n\nAn update for glibc is now available for Red Hat Enterprise Linux 5\nExtended Lifecycle Support, Red Hat Enterprise Linux 5.9 Long Life, Red Hat\nEnterprise Linux 6.2 Advanced Update Support, Red Hat Enterprise Linux 6.4\nAdvanced Update Support, Red Hat Enterprise Linux 6.5 Advanced Update\nSupport, Red Hat Enterprise Linux 6.5 Telco Extended Update Support, Red\nHat Enterprise Linux 6.6 Advanced Update Support, Red Hat Enterprise Linux\n6.6 Telco Extended Update Support, Red Hat Enterprise Linux 6.7 Extended\nUpdate Support, and Red Hat Enterprise Linux 7.2 Extended Update Support. \n\nRed Hat Product Security has rated this update as having a security impact\nof Important. A Common Vulnerability Scoring System (CVSS) base score,\nwhich gives a detailed severity rating, is available for each vulnerability\nfrom the CVE link(s) in the References section. \n\n2. Relevant releases/architectures:\n\nRed Hat Enterprise Linux ComputeNode EUS (v. 7.2) - x86_64\nRed Hat Enterprise Linux ComputeNode Optional EUS (v. 7.2) - x86_64\nRed Hat Enterprise Linux HPC Node EUS (v. 6.7) - x86_64\nRed Hat Enterprise Linux HPC Node Optional EUS (v. 6.7) - x86_64\nRed Hat Enterprise Linux Long Life (v. 5.9 server) - i386, ia64, x86_64\nRed Hat Enterprise Linux Server (v. 5 ELS) - i386, s390x, x86_64\nRed Hat Enterprise Linux Server AUS (v. 6.2) - x86_64\nRed Hat Enterprise Linux Server AUS (v. 6.4) - x86_64\nRed Hat Enterprise Linux Server AUS (v. 6.5) - x86_64\nRed Hat Enterprise Linux Server AUS (v. 6.6) - x86_64\nRed Hat Enterprise Linux Server EUS (v. 6.7) - i386, ppc64, s390x, x86_64\nRed Hat Enterprise Linux Server EUS (v. 7.2) - ppc64, ppc64le, s390x, x86_64\nRed Hat Enterprise Linux Server Optional AUS (v. 6.2) - x86_64\nRed Hat Enterprise Linux Server Optional AUS (v. 6.4) - x86_64\nRed Hat Enterprise Linux Server Optional AUS (v. 6.5) - x86_64\nRed Hat Enterprise Linux Server Optional AUS (v. 6.6) - x86_64\nRed Hat Enterprise Linux Server Optional EUS (v. 6.7) - i386, ppc64, s390x, x86_64\nRed Hat Enterprise Linux Server Optional EUS (v. 7.2) - ppc64, ppc64le, s390x, x86_64\nRed Hat Enterprise Linux Server Optional TUS (v. 6.5) - x86_64\nRed Hat Enterprise Linux Server Optional TUS (v. 6.6) - x86_64\nRed Hat Enterprise Linux Server TUS (v. 6.5) - x86_64\nRed Hat Enterprise Linux Server TUS (v. 6.6) - x86_64\n\n3. Description:\n\nThe glibc packages provide the standard C libraries (libc), POSIX thread\nlibraries (libpthread), standard math libraries (libm), and the name\nservice cache daemon (nscd) used by multiple programs on the system. \nWithout these libraries, the Linux system cannot function correctly. This is glibc-side mitigation which blocks\nprocessing of LD_LIBRARY_PATH for programs running in secure-execution mode\nand reduces the number of allocations performed by the processing of\nLD_AUDIT, LD_PRELOAD, and LD_HWCAP_MASK, making successful exploitation of\nthis issue more difficult. (CVE-2017-1000366)\n\nRed Hat would like to thank Qualys Research Labs for reporting this issue. \n\n4. Solution:\n\nFor details on how to apply this update, which includes the changes\ndescribed in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258\n\nFor the update to take effect, all services linked to the glibc library\nmust be restarted, or the system rebooted. \n\n5. Bugs fixed (https://bugzilla.redhat.com/):\n\n1452543 - CVE-2017-1000366 glibc: heap/stack gap jumping via unbounded stack allocations\n\n6. Package List:\n\nRed Hat Enterprise Linux Long Life (v. 5.9 server):\n\nSource:\nglibc-2.5-107.el5_9.9.src.rpm\n\ni386:\nglibc-2.5-107.el5_9.9.i386.rpm\nglibc-2.5-107.el5_9.9.i686.rpm\nglibc-common-2.5-107.el5_9.9.i386.rpm\nglibc-debuginfo-2.5-107.el5_9.9.i386.rpm\nglibc-debuginfo-2.5-107.el5_9.9.i686.rpm\nglibc-debuginfo-common-2.5-107.el5_9.9.i386.rpm\nglibc-devel-2.5-107.el5_9.9.i386.rpm\nglibc-headers-2.5-107.el5_9.9.i386.rpm\nglibc-utils-2.5-107.el5_9.9.i386.rpm\nnscd-2.5-107.el5_9.9.i386.rpm\n\nia64:\nglibc-2.5-107.el5_9.9.i686.rpm\nglibc-2.5-107.el5_9.9.ia64.rpm\nglibc-common-2.5-107.el5_9.9.ia64.rpm\nglibc-debuginfo-2.5-107.el5_9.9.i686.rpm\nglibc-debuginfo-2.5-107.el5_9.9.ia64.rpm\nglibc-debuginfo-common-2.5-107.el5_9.9.i386.rpm\nglibc-devel-2.5-107.el5_9.9.ia64.rpm\nglibc-headers-2.5-107.el5_9.9.ia64.rpm\nglibc-utils-2.5-107.el5_9.9.ia64.rpm\nnscd-2.5-107.el5_9.9.ia64.rpm\n\nx86_64:\nglibc-2.5-107.el5_9.9.i686.rpm\nglibc-2.5-107.el5_9.9.x86_64.rpm\nglibc-common-2.5-107.el5_9.9.x86_64.rpm\nglibc-debuginfo-2.5-107.el5_9.9.i386.rpm\nglibc-debuginfo-2.5-107.el5_9.9.i686.rpm\nglibc-debuginfo-2.5-107.el5_9.9.x86_64.rpm\nglibc-debuginfo-common-2.5-107.el5_9.9.i386.rpm\nglibc-devel-2.5-107.el5_9.9.i386.rpm\nglibc-devel-2.5-107.el5_9.9.x86_64.rpm\nglibc-headers-2.5-107.el5_9.9.x86_64.rpm\nglibc-utils-2.5-107.el5_9.9.x86_64.rpm\nnscd-2.5-107.el5_9.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server (v. 5 ELS):\n\nSource:\nglibc-2.5-123.el5_11.4.src.rpm\n\ni386:\nglibc-2.5-123.el5_11.4.i386.rpm\nglibc-2.5-123.el5_11.4.i686.rpm\nglibc-common-2.5-123.el5_11.4.i386.rpm\nglibc-debuginfo-2.5-123.el5_11.4.i386.rpm\nglibc-debuginfo-2.5-123.el5_11.4.i686.rpm\nglibc-debuginfo-common-2.5-123.el5_11.4.i386.rpm\nglibc-devel-2.5-123.el5_11.4.i386.rpm\nglibc-headers-2.5-123.el5_11.4.i386.rpm\nglibc-utils-2.5-123.el5_11.4.i386.rpm\nnscd-2.5-123.el5_11.4.i386.rpm\n\ns390x:\nglibc-2.5-123.el5_11.4.s390.rpm\nglibc-2.5-123.el5_11.4.s390x.rpm\nglibc-common-2.5-123.el5_11.4.s390x.rpm\nglibc-debuginfo-2.5-123.el5_11.4.s390.rpm\nglibc-debuginfo-2.5-123.el5_11.4.s390x.rpm\nglibc-devel-2.5-123.el5_11.4.s390.rpm\nglibc-devel-2.5-123.el5_11.4.s390x.rpm\nglibc-headers-2.5-123.el5_11.4.s390x.rpm\nglibc-utils-2.5-123.el5_11.4.s390x.rpm\nnscd-2.5-123.el5_11.4.s390x.rpm\n\nx86_64:\nglibc-2.5-123.el5_11.4.i686.rpm\nglibc-2.5-123.el5_11.4.x86_64.rpm\nglibc-common-2.5-123.el5_11.4.x86_64.rpm\nglibc-debuginfo-2.5-123.el5_11.4.i386.rpm\nglibc-debuginfo-2.5-123.el5_11.4.i686.rpm\nglibc-debuginfo-2.5-123.el5_11.4.x86_64.rpm\nglibc-debuginfo-common-2.5-123.el5_11.4.i386.rpm\nglibc-devel-2.5-123.el5_11.4.i386.rpm\nglibc-devel-2.5-123.el5_11.4.x86_64.rpm\nglibc-headers-2.5-123.el5_11.4.x86_64.rpm\nglibc-utils-2.5-123.el5_11.4.x86_64.rpm\nnscd-2.5-123.el5_11.4.x86_64.rpm\n\nRed Hat Enterprise Linux HPC Node EUS (v. 6.7):\n\nSource:\nglibc-2.12-1.166.el6_7.8.src.rpm\n\nx86_64:\nglibc-2.12-1.166.el6_7.8.i686.rpm\nglibc-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-common-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-devel-2.12-1.166.el6_7.8.i686.rpm\nglibc-devel-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-headers-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-utils-2.12-1.166.el6_7.8.x86_64.rpm\nnscd-2.12-1.166.el6_7.8.x86_64.rpm\n\nRed Hat Enterprise Linux HPC Node Optional EUS (v. 6.7):\n\nx86_64:\nglibc-debuginfo-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-static-2.12-1.166.el6_7.8.i686.rpm\nglibc-static-2.12-1.166.el6_7.8.x86_64.rpm\n\nRed Hat Enterprise Linux Server AUS (v. 6.2):\n\nSource:\nglibc-2.12-1.47.el6_2.18.src.rpm\n\nx86_64:\nglibc-2.12-1.47.el6_2.18.i686.rpm\nglibc-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-common-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-debuginfo-2.12-1.47.el6_2.18.i686.rpm\nglibc-debuginfo-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-debuginfo-common-2.12-1.47.el6_2.18.i686.rpm\nglibc-debuginfo-common-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-devel-2.12-1.47.el6_2.18.i686.rpm\nglibc-devel-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-headers-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-utils-2.12-1.47.el6_2.18.x86_64.rpm\nnscd-2.12-1.47.el6_2.18.x86_64.rpm\n\nRed Hat Enterprise Linux Server AUS (v. 6.4):\n\nSource:\nglibc-2.12-1.107.el6_4.10.src.rpm\n\nx86_64:\nglibc-2.12-1.107.el6_4.10.i686.rpm\nglibc-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-common-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-debuginfo-2.12-1.107.el6_4.10.i686.rpm\nglibc-debuginfo-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-debuginfo-common-2.12-1.107.el6_4.10.i686.rpm\nglibc-debuginfo-common-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-devel-2.12-1.107.el6_4.10.i686.rpm\nglibc-devel-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-headers-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-utils-2.12-1.107.el6_4.10.x86_64.rpm\nnscd-2.12-1.107.el6_4.10.x86_64.rpm\n\nRed Hat Enterprise Linux Server AUS (v. 6.5):\n\nSource:\nglibc-2.12-1.132.el6_5.9.src.rpm\n\nx86_64:\nglibc-2.12-1.132.el6_5.9.i686.rpm\nglibc-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-common-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-debuginfo-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-devel-2.12-1.132.el6_5.9.i686.rpm\nglibc-devel-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-headers-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-utils-2.12-1.132.el6_5.9.x86_64.rpm\nnscd-2.12-1.132.el6_5.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server TUS (v. 6.5):\n\nSource:\nglibc-2.12-1.132.el6_5.9.src.rpm\n\nx86_64:\nglibc-2.12-1.132.el6_5.9.i686.rpm\nglibc-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-common-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-debuginfo-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-devel-2.12-1.132.el6_5.9.i686.rpm\nglibc-devel-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-headers-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-utils-2.12-1.132.el6_5.9.x86_64.rpm\nnscd-2.12-1.132.el6_5.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server AUS (v. 6.6):\n\nSource:\nglibc-2.12-1.149.el6_6.12.src.rpm\n\nx86_64:\nglibc-2.12-1.149.el6_6.12.i686.rpm\nglibc-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-common-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-debuginfo-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-devel-2.12-1.149.el6_6.12.i686.rpm\nglibc-devel-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-headers-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-utils-2.12-1.149.el6_6.12.x86_64.rpm\nnscd-2.12-1.149.el6_6.12.x86_64.rpm\n\nRed Hat Enterprise Linux Server TUS (v. 6.6):\n\nSource:\nglibc-2.12-1.149.el6_6.12.src.rpm\n\nx86_64:\nglibc-2.12-1.149.el6_6.12.i686.rpm\nglibc-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-common-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-debuginfo-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-devel-2.12-1.149.el6_6.12.i686.rpm\nglibc-devel-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-headers-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-utils-2.12-1.149.el6_6.12.x86_64.rpm\nnscd-2.12-1.149.el6_6.12.x86_64.rpm\n\nRed Hat Enterprise Linux Server EUS (v. 6.7):\n\nSource:\nglibc-2.12-1.166.el6_7.8.src.rpm\n\ni386:\nglibc-2.12-1.166.el6_7.8.i686.rpm\nglibc-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-devel-2.12-1.166.el6_7.8.i686.rpm\nglibc-headers-2.12-1.166.el6_7.8.i686.rpm\nglibc-utils-2.12-1.166.el6_7.8.i686.rpm\nnscd-2.12-1.166.el6_7.8.i686.rpm\n\nppc64:\nglibc-2.12-1.166.el6_7.8.ppc.rpm\nglibc-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-common-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.ppc.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.ppc.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-devel-2.12-1.166.el6_7.8.ppc.rpm\nglibc-devel-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-headers-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-utils-2.12-1.166.el6_7.8.ppc64.rpm\nnscd-2.12-1.166.el6_7.8.ppc64.rpm\n\ns390x:\nglibc-2.12-1.166.el6_7.8.s390.rpm\nglibc-2.12-1.166.el6_7.8.s390x.rpm\nglibc-common-2.12-1.166.el6_7.8.s390x.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.s390.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.s390x.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.s390.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.s390x.rpm\nglibc-devel-2.12-1.166.el6_7.8.s390.rpm\nglibc-devel-2.12-1.166.el6_7.8.s390x.rpm\nglibc-headers-2.12-1.166.el6_7.8.s390x.rpm\nglibc-utils-2.12-1.166.el6_7.8.s390x.rpm\nnscd-2.12-1.166.el6_7.8.s390x.rpm\n\nx86_64:\nglibc-2.12-1.166.el6_7.8.i686.rpm\nglibc-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-common-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-devel-2.12-1.166.el6_7.8.i686.rpm\nglibc-devel-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-headers-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-utils-2.12-1.166.el6_7.8.x86_64.rpm\nnscd-2.12-1.166.el6_7.8.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional AUS (v. 6.2):\n\nSource:\nglibc-2.12-1.47.el6_2.18.src.rpm\n\nx86_64:\nglibc-debuginfo-2.12-1.47.el6_2.18.i686.rpm\nglibc-debuginfo-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-debuginfo-common-2.12-1.47.el6_2.18.i686.rpm\nglibc-debuginfo-common-2.12-1.47.el6_2.18.x86_64.rpm\nglibc-static-2.12-1.47.el6_2.18.i686.rpm\nglibc-static-2.12-1.47.el6_2.18.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional AUS (v. 6.4):\n\nSource:\nglibc-2.12-1.107.el6_4.10.src.rpm\n\nx86_64:\nglibc-debuginfo-2.12-1.107.el6_4.10.i686.rpm\nglibc-debuginfo-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-debuginfo-common-2.12-1.107.el6_4.10.i686.rpm\nglibc-debuginfo-common-2.12-1.107.el6_4.10.x86_64.rpm\nglibc-static-2.12-1.107.el6_4.10.i686.rpm\nglibc-static-2.12-1.107.el6_4.10.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional AUS (v. 6.5):\n\nSource:\nglibc-2.12-1.132.el6_5.9.src.rpm\n\nx86_64:\nglibc-debuginfo-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-static-2.12-1.132.el6_5.9.i686.rpm\nglibc-static-2.12-1.132.el6_5.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional TUS (v. 6.5):\n\nSource:\nglibc-2.12-1.132.el6_5.9.src.rpm\n\nx86_64:\nglibc-debuginfo-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.i686.rpm\nglibc-debuginfo-common-2.12-1.132.el6_5.9.x86_64.rpm\nglibc-static-2.12-1.132.el6_5.9.i686.rpm\nglibc-static-2.12-1.132.el6_5.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional AUS (v. 6.6):\n\nx86_64:\nglibc-debuginfo-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-static-2.12-1.149.el6_6.12.i686.rpm\nglibc-static-2.12-1.149.el6_6.12.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional TUS (v. 6.6):\n\nx86_64:\nglibc-debuginfo-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.i686.rpm\nglibc-debuginfo-common-2.12-1.149.el6_6.12.x86_64.rpm\nglibc-static-2.12-1.149.el6_6.12.i686.rpm\nglibc-static-2.12-1.149.el6_6.12.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional EUS (v. 6.7):\n\ni386:\nglibc-debuginfo-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-static-2.12-1.166.el6_7.8.i686.rpm\n\nppc64:\nglibc-debuginfo-2.12-1.166.el6_7.8.ppc.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.ppc.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.ppc64.rpm\nglibc-static-2.12-1.166.el6_7.8.ppc.rpm\nglibc-static-2.12-1.166.el6_7.8.ppc64.rpm\n\ns390x:\nglibc-debuginfo-2.12-1.166.el6_7.8.s390.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.s390x.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.s390.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.s390x.rpm\nglibc-static-2.12-1.166.el6_7.8.s390.rpm\nglibc-static-2.12-1.166.el6_7.8.s390x.rpm\n\nx86_64:\nglibc-debuginfo-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.i686.rpm\nglibc-debuginfo-common-2.12-1.166.el6_7.8.x86_64.rpm\nglibc-static-2.12-1.166.el6_7.8.i686.rpm\nglibc-static-2.12-1.166.el6_7.8.x86_64.rpm\n\nRed Hat Enterprise Linux ComputeNode EUS (v. 7.2):\n\nSource:\nglibc-2.17-106.el7_2.9.src.rpm\n\nx86_64:\nglibc-2.17-106.el7_2.9.i686.rpm\nglibc-2.17-106.el7_2.9.x86_64.rpm\nglibc-common-2.17-106.el7_2.9.x86_64.rpm\nglibc-debuginfo-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-2.17-106.el7_2.9.x86_64.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.x86_64.rpm\nglibc-devel-2.17-106.el7_2.9.i686.rpm\nglibc-devel-2.17-106.el7_2.9.x86_64.rpm\nglibc-headers-2.17-106.el7_2.9.x86_64.rpm\nglibc-utils-2.17-106.el7_2.9.x86_64.rpm\nnscd-2.17-106.el7_2.9.x86_64.rpm\n\nRed Hat Enterprise Linux ComputeNode Optional EUS (v. 7.2):\n\nx86_64:\nglibc-debuginfo-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-2.17-106.el7_2.9.x86_64.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.x86_64.rpm\nglibc-static-2.17-106.el7_2.9.i686.rpm\nglibc-static-2.17-106.el7_2.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server EUS (v. 7.2):\n\nSource:\nglibc-2.17-106.el7_2.9.src.rpm\n\nppc64:\nglibc-2.17-106.el7_2.9.ppc.rpm\nglibc-2.17-106.el7_2.9.ppc64.rpm\nglibc-common-2.17-106.el7_2.9.ppc64.rpm\nglibc-debuginfo-2.17-106.el7_2.9.ppc.rpm\nglibc-debuginfo-2.17-106.el7_2.9.ppc64.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.ppc.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.ppc64.rpm\nglibc-devel-2.17-106.el7_2.9.ppc.rpm\nglibc-devel-2.17-106.el7_2.9.ppc64.rpm\nglibc-headers-2.17-106.el7_2.9.ppc64.rpm\nglibc-utils-2.17-106.el7_2.9.ppc64.rpm\nnscd-2.17-106.el7_2.9.ppc64.rpm\n\nppc64le:\nglibc-2.17-106.el7_2.9.ppc64le.rpm\nglibc-common-2.17-106.el7_2.9.ppc64le.rpm\nglibc-debuginfo-2.17-106.el7_2.9.ppc64le.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.ppc64le.rpm\nglibc-devel-2.17-106.el7_2.9.ppc64le.rpm\nglibc-headers-2.17-106.el7_2.9.ppc64le.rpm\nglibc-utils-2.17-106.el7_2.9.ppc64le.rpm\nnscd-2.17-106.el7_2.9.ppc64le.rpm\n\ns390x:\nglibc-2.17-106.el7_2.9.s390.rpm\nglibc-2.17-106.el7_2.9.s390x.rpm\nglibc-common-2.17-106.el7_2.9.s390x.rpm\nglibc-debuginfo-2.17-106.el7_2.9.s390.rpm\nglibc-debuginfo-2.17-106.el7_2.9.s390x.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.s390.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.s390x.rpm\nglibc-devel-2.17-106.el7_2.9.s390.rpm\nglibc-devel-2.17-106.el7_2.9.s390x.rpm\nglibc-headers-2.17-106.el7_2.9.s390x.rpm\nglibc-utils-2.17-106.el7_2.9.s390x.rpm\nnscd-2.17-106.el7_2.9.s390x.rpm\n\nx86_64:\nglibc-2.17-106.el7_2.9.i686.rpm\nglibc-2.17-106.el7_2.9.x86_64.rpm\nglibc-common-2.17-106.el7_2.9.x86_64.rpm\nglibc-debuginfo-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-2.17-106.el7_2.9.x86_64.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.x86_64.rpm\nglibc-devel-2.17-106.el7_2.9.i686.rpm\nglibc-devel-2.17-106.el7_2.9.x86_64.rpm\nglibc-headers-2.17-106.el7_2.9.x86_64.rpm\nglibc-utils-2.17-106.el7_2.9.x86_64.rpm\nnscd-2.17-106.el7_2.9.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional EUS (v. 7.2):\n\nppc64:\nglibc-debuginfo-2.17-106.el7_2.9.ppc.rpm\nglibc-debuginfo-2.17-106.el7_2.9.ppc64.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.ppc.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.ppc64.rpm\nglibc-static-2.17-106.el7_2.9.ppc.rpm\nglibc-static-2.17-106.el7_2.9.ppc64.rpm\n\nppc64le:\nglibc-debuginfo-2.17-106.el7_2.9.ppc64le.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.ppc64le.rpm\nglibc-static-2.17-106.el7_2.9.ppc64le.rpm\n\ns390x:\nglibc-debuginfo-2.17-106.el7_2.9.s390.rpm\nglibc-debuginfo-2.17-106.el7_2.9.s390x.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.s390.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.s390x.rpm\nglibc-static-2.17-106.el7_2.9.s390.rpm\nglibc-static-2.17-106.el7_2.9.s390x.rpm\n\nx86_64:\nglibc-debuginfo-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-2.17-106.el7_2.9.x86_64.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.i686.rpm\nglibc-debuginfo-common-2.17-106.el7_2.9.x86_64.rpm\nglibc-static-2.17-106.el7_2.9.i686.rpm\nglibc-static-2.17-106.el7_2.9.x86_64.rpm\n\nThese packages are GPG signed by Red Hat for security.  Our key and\ndetails on how to verify the signature are available from\nhttps://access.redhat.com/security/team/key/\n\n7. References:\n\nhttps://access.redhat.com/security/cve/CVE-2017-1000366\nhttps://access.redhat.com/security/updates/classification/#important\nhttps://access.redhat.com/security/vulnerabilities/stackguard\n\n8. Contact:\n\nThe Red Hat security contact is \u003csecalert@redhat.com\u003e. More contact\ndetails at https://access.redhat.com/security/team/contact/\n\nCopyright 2017 Red Hat, Inc. \n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niD8DBQFZSDV3XlSAg2UNWIIRAibeAKC2QtxViqngTTBVM9fvG1XjRCkgwACgrHP1\nPVr1sUH9RUhxrQOKQqWtnKY=\n=ywUB\n-----END PGP SIGNATURE-----\n\n--\nRHSA-announce mailing list\nRHSA-announce@redhat.com\nhttps://www.redhat.com/mailman/listinfo/rhsa-announce\n. For the full details, please refer to their advisory\npublished at:\nhttps://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt\n\nFor the oldstable distribution (jessie), this problem has been fixed\nin version 2.19-18+deb8u10. \n\nFor the stable distribution (stretch), this problem has been fixed in\nversion 2.24-11+deb9u1. \n\nFor the unstable distribution (sid), this problem will be fixed soon. \n\nWe recommend that you upgrade your glibc packages. \nQualys Security Advisory\n\nThe Stack Clash\n\n\n========================================================================\nContents\n========================================================================\n\nI. Introduction\nII. Problem\n    II.1. Automatic stack expansion\n    II.2. Stack guard-page\n    II.3. Stack-clash exploitation\nIII. Solutions\nIV. Results\n    IV.1. Linux\n    IV.2. OpenBSD\n    IV.3. NetBSD\n    IV.4. FreeBSD\n    IV.5. Solaris\nV. Acknowledgments\n\n\n========================================================================\nI. Introduction\n========================================================================\n\nOur research started with a 96-megabyte surprise:\n\nb97bb000-b97dc000 rw-p 00000000 00:00 0          [heap]\nbf7c6000-bf806000 rw-p 00000000 00:00 0          [stack]\n\nand a 12-year-old question: \"If the heap grows up, and the stack grows\ndown, what happens when they clash? Is it exploitable? How?\"\n\n- In 2005, Gael Delalleau presented \"Large memory management\n  vulnerabilities\" and the first stack-clash exploit in user-space\n  (against mod_php 4.3.0 on Apache 2.0.53):\n\n  http://cansecwest.com/core05/memory_vulns_delalleau.pdf\n\n- In 2010, Rafal Wojtczuk published \"Exploiting large memory management\n  vulnerabilities in Xorg server running on Linux\", the second\n  stack-clash exploit in user-space (CVE-2010-2240):\n\n  http://www.invisiblethingslab.com/resources/misc-2010/xorg-large-memory-attacks.pdf\n\n- Since 2010, security researchers have exploited several stack-clashes\n  in the kernel-space; for example:\n\n  https://jon.oberheide.org/blog/2010/11/29/exploiting-stack-overflows-in-the-linux-kernel/\n  https://jon.oberheide.org/files/infiltrate12-thestackisback.pdf\n  https://googleprojectzero.blogspot.com/2016/06/exploiting-recursion-in-linux-kernel_20.html\n\nIn user-space, however, this problem has been greatly underestimated;\nthe only public exploits are Gael Delalleau\u0027s and Rafal Wojtczuk\u0027s, and\nthey were written before Linux introduced a protection against\nstack-clashes (a \"guard-page\" mapped below the stack):\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-2240\n\nIn this advisory, we show that stack-clashes are widespread in\nuser-space, and exploitable despite the stack guard-page; we discovered\nmultiple vulnerabilities in guard-page implementations, and devised\ngeneral methods for:\n\n- \"Clashing\" the stack with another memory region: we allocate memory\n  until the stack reaches another memory region, or until another memory\n  region reaches the stack;\n\n- \"Jumping\" over the stack guard-page: we move the stack-pointer from\n  the stack and into the other memory region, without accessing the\n  stack guard-page;\n\n- \"Smashing\" the stack, or the other memory region: we overwrite the\n  stack with the other memory region, or the other memory region with\n  the stack. \n\nTo illustrate our findings, we developed the following exploits and\nproofs-of-concepts:\n\n- a local-root exploit against Exim (CVE-2017-1000369, CVE-2017-1000376)\n  on i386 Debian;\n\n- a local-root exploit against Sudo (CVE-2017-1000367, CVE-2017-1000366)\n  on i386 Debian, Ubuntu, CentOS;\n\n- an independent Sudoer-to-root exploit against CVE-2017-1000367 on any\n  SELinux-enabled distribution;\n\n- a local-root exploit against ld.so and most SUID-root binaries\n  (CVE-2017-1000366, CVE-2017-1000370) on i386 Debian, Fedora, CentOS;\n\n- a local-root exploit against ld.so and most SUID-root PIEs\n  (CVE-2017-1000366, CVE-2017-1000371) on i386 Debian, Ubuntu, Fedora;\n\n- a local-root exploit against /bin/su (CVE-2017-1000366,\n  CVE-2017-1000365) on i386 Debian;\n\n- a proof-of-concept that gains eip control against Sudo on i386\n  grsecurity/PaX (CVE-2017-1000367, CVE-2017-1000366, CVE-2017-1000377);\n\n- a local proof-of-concept that gains rip control against Exim\n  (CVE-2017-1000369) on amd64 Debian;\n\n- a local-root exploit against ld.so and most SUID-root binaries\n  (CVE-2017-1000366, CVE-2017-1000379) on amd64 Debian, Ubuntu, Fedora,\n  CentOS;\n\n- a proof-of-concept against /usr/bin/at on i386 OpenBSD, for\n  CVE-2017-1000372 in OpenBSD\u0027s stack guard-page implementation and\n  CVE-2017-1000373 in OpenBSD\u0027s qsort() function;\n\n- a proof-of-concept for CVE-2017-1000374 and CVE-2017-1000375 in\n  NetBSD\u0027s stack guard-page implementation;\n\n- a proof-of-concept for CVE-2017-1085 in FreeBSD\u0027s setrlimit()\n  RLIMIT_STACK implementation;\n\n- two proofs-of-concept for CVE-2017-1083 and CVE-2017-1084 in FreeBSD\u0027s\n  stack guard-page implementation;\n\n- a local-root exploit against /usr/bin/rsh (CVE-2017-3630,\n  CVE-2017-3629, CVE-2017-3631) on Solaris 11. \n\n\n========================================================================\nII. Problem\n========================================================================\n\nNote: in this advisory, the \"start of the stack\" is the lowest address\nof its memory region, and the \"end of the stack\" is the highest address\nof its memory region; we do not use the ambiguous terms \"top of the\nstack\" and \"bottom of the stack\". \n\n========================================================================\nII.1. Automatic stack expansion\n========================================================================\n\nThe user-space stack of a process is automatically expanded by the\nkernel:\n\n- if the stack-pointer (the esp register, on i386) reaches the start of\n  the stack and the unmapped memory pages below (the stack grows down,\n  on i386),\n\n- then a \"page-fault\" exception is raised and caught by the kernel,\n\n- and the page-fault handler transparently expands the user-space stack\n  of the process (it decreases the start address of the stack),\n\n- or it terminates the process with a SIGSEGV if the stack expansion\n  fails (for example, if the RLIMIT_STACK is reached). \n\nUnfortunately, this stack expansion mechanism is implicit and fragile:\nit relies on page-fault exceptions, but if another memory region is\nmapped directly below the stack, then the stack-pointer can move from\nthe stack into the other memory region without raising a page-fault,\nand:\n\n- the kernel cannot tell that the process needed more stack memory;\n\n- the process cannot tell that its stack-pointer moved from the stack\n  into another memory region. \n\nIn contrast, the heap expansion mechanism is explicit and robust: the\nprocess uses the brk() system-call to tell the kernel that it needs more\nheap memory, and the kernel expands the heap accordingly (it increases\nthe end address of the heap memory region -- the heap always grows up). \n\n========================================================================\nII.2. Stack guard-page\n========================================================================\n\nThe fragile stack expansion mechanism poses a security threat: if the\nstack-pointer of a process can move from the stack into another memory\nregion (which ends exactly where the stack starts) without raising a\npage-fault, then:\n\n- the process uses this other memory region as if it were an extension\n  of the stack;\n\n- a write to this stack extension smashes the other memory region;\n\n- a write to the other memory region smashes the stack extension. \n\nTo protect against this security threat, the kernel maps a \"guard-page\"\nbelow the start of the stack: one or more PROT_NONE pages (or unmappable\npages) that:\n\n- raise a page-fault exception if accessed (before the stack-pointer can\n  move from the stack into another memory region);\n\n- terminate the process with a SIGSEGV (because the page-fault handler\n  cannot expand the stack if another memory region is mapped directly\n  below). \n\nUnfortunately, a stack guard-page of a few kilobytes is insufficient\n(CVE-2017-1000364): if the stack-pointer \"jumps\" over the guard-page --\nif it moves from the stack into another memory region without accessing\nthe guard-page -- then no page-fault exception is raised and the stack\nextends into the other memory region. \n\nThis theoretical vulnerability was first described in Gael Delalleau\u0027s\n2005 presentation (slides 24-29). In the present advisory, we discuss\nits practicalities, and multiple vulnerabilities in stack guard-page\nimplementations (in OpenBSD, NetBSD, and FreeBSD), but we exclude\nrelated vulnerabilities such as unbounded alloca()s and VLAs\n(Variable-Length Arrays) that have been exploited in the past:\n\nhttp://phrack.org/issues/63/14.html\nhttp://blog.exodusintel.com/2013/01/07/who-was-phone/\n\n========================================================================\nII.3. Stack-clash exploitation\n========================================================================\n\n    Must be a clash, there\u0027s no alternative. \n                              --The Clash, \"Kingston Advice\"\n\nOur exploits follow a series of four sequential steps -- each step\nallocates memory that must not be freed before all steps are complete:\n\nStep 1: Clash (the stack with another memory region)\nStep 2: Run (move the stack-pointer to the start of the stack)\nStep 3: Jump (over the stack guard-page, into the other memory region)\nStep 4: Smash (the stack, or the other memory region)\n\n========================================================================\nII.3.1. Step 1: Clash the stack with another memory region\n========================================================================\n\n    Have the boys found the leak yet?\n                              --The Clash, \"The Leader\"\n\nAllocate memory until the start of the stack reaches the end of another\nmemory region, or until the end of another memory region reaches the\nstart of the stack. \n\n- The other memory region can be, for example:\n  . the heap;\n  . an anonymous mmap();\n  . the read-write segment of ld.so;\n  . the read-write segment of a PIE, a Position-Independent Executable. \n\n- The memory allocated in this Step 1 can be, for example:\n  . stack and heap memory;\n  . stack and anonymous mmap() memory;\n  . stack memory only. \n\n- The heap and anonymous mmap() memory can be:\n\n  . temporarily allocated, but not freed before the stack guard-page is\n    jumped over in Step 3 and memory is smashed in Step 4;\n\n  . permanently leaked. On Linux, a general method for allocating\n    anonymous mmap()s is the LD_AUDIT memory leak that we discovered in\n    the ld.so part of the glibc, the GNU C Library (CVE-2017-1000366). \n\n- The stack memory can be allocated, for example:\n\n  . through megabytes of command-line arguments and environment\n    variables. \n\n    On Linux, this general method for allocating stack memory is limited\n    by the kernel to 1/4 of the current RLIMIT_STACK (1GB on i386 if\n    RLIMIT_STACK is RLIM_INFINITY -- man execve, \"Limits on size of\n    arguments and environment\"). \n\n    However, as we were drafting this advisory, we realized that the\n    kernel imposes this limit on the argument and environment strings,\n    but not on the argv[] and envp[] pointers to these strings, and we\n    developed alternative versions of our Linux exploits that do not\n    depend on application-specific memory leaks (CVE-2017-1000365). through recursive function calls. \n\n    On BSD, we discovered a general method for allocating megabytes of\n    stack memory: a vulnerability in qsort() that causes this function\n    to recurse N/4 times, given a pathological input array of N elements\n    (CVE-2017-1000373 in OpenBSD, CVE-2017-1000378 in NetBSD, and\n    CVE-2017-1082 in FreeBSD). \n\n- In a few rare cases, Step 1 is not needed, because another memory\n  region is naturally mapped directly below the stack (for example,\n  ld.so in our Solaris exploit). \n\n========================================================================\nII.3.2. Step 2: Move the stack-pointer to the start of the stack\n========================================================================\n\n    Run, run, run, run, run, don\u0027t you know?\n                              --The Clash, \"Three Card Trick\"\n\nConsume the unused stack memory that separates the stack-pointer from\nthe start of the stack. This Step 2 is similar to Step 3 (\"Jump over the\nstack guard-page\") but is needed because:\n\n- the stack-pointer is usually several kilobytes higher than the start\n  of the stack (functions that allocate a large stack-frame decrease the\n  start address of the stack, but this address is never increased\n  again); moreover:\n\n  . the FreeBSD kernel automatically expands the user-space stack of a\n    process by multiples of 128KB (SGROWSIZ, in vm_map_growstack());\n\n  . the Linux kernel initially expands the user-space stack of a process\n    by 128KB (stack_expand, in setup_arg_pages()). \n\n- in Step 3, the stack-based buffer used to jump over the guard-page:\n\n  . is usually not large enough to simultaneously move the stack-pointer\n    to the start of the stack, and then into another memory region;\n\n  . must not be fully written to (a full write would access the stack\n    guard-page and terminate the process) but the stack memory consumed\n    in this Step 2 can be fully written to (for example, strdupa() can\n    be used in Step 2, but not in Step 3). \n\nThe stack memory consumed in this Step 2 can be, for example:\n\n- large stack-frames, alloca()s, or VLAs (which can be detected by\n  grsecurity/PaX\u0027s STACKLEAK plugin for GCC,\n  https://grsecurity.net/features.php);\n\n- recursive function calls (which can be detected by GNU cflow,\n  http://www.gnu.org/software/cflow/);\n\n- on Linux, we discovered that the argv[] and envp[] arrays of pointers\n  can be used to consume the 128KB of initial stack expansion, because\n  the kernel allocates these arrays on the stack long after the call to\n  setup_arg_pages(); this general method for completing Step 2 is\n  exploitable locally, but the initial stack expansion poses a major\n  obstacle to the remote exploitation of stack-clashes, as mentioned in\n  IV.1.1. \n\nIn a few rare cases, Step 2 is not needed, because the stack-pointer is\nnaturally close to the start of the stack (for example, in Exim\u0027s main()\nfunction, the 256KB group_list[] moves the stack-pointer to the start of\nthe stack and beyond). \n\n========================================================================\nII.3.3. Step 3: Jump over the stack guard-page, into another memory\nregion\n========================================================================\n\n    You need a little jump of electrical shockers. \n                              --The Clash, \"Clash City Rockers\"\n\nMove the stack-pointer from the stack and into the memory region that\nclashed with the stack in Step 1, but without accessing the guard-page. \nTo complete this Step 3, a large stack-based buffer, alloca(), or VLA is\nneeded, and:\n\n- it must be larger than the guard-page;\n\n- it must end in the stack, above the guard-page;\n\n- it must start in the memory region below the stack guard-page;\n\n- it must not be fully written to (a full write would access the\n  guard-page, raise a page-fault exception, and terminate the process,\n  because the memory region mapped directly below the stack prevents the\n  page-fault handler from expanding the stack). \n\nIn a few cases, Step 3 is not needed:\n\n- on FreeBSD, a stack guard-page is implemented but disabled by default\n  (CVE-2017-1083);\n\n- on OpenBSD, NetBSD, and FreeBSD, we discovered implementation\n  vulnerabilities that eliminate the stack guard-page (CVE-2017-1000372,\n  CVE-2017-1000374, CVE-2017-1084). \n\nOn Linux, we devised general methods for jumping over the stack\nguard-page (CVE-2017-1000366):\n\n- The glibc\u0027s __dcigettext() function alloca()tes single_locale, a\n  stack-based buffer of up to 128KB (MAX_ARG_STRLEN, man execve), the\n  length of the LANGUAGE environment variable (if the current locale is\n  neither \"C\" nor \"POSIX\", but distributions install default locales\n  such as \"C.UTF-8\" and \"en_US.utf8\"). \n\n  If LANGUAGE is mostly composed of \u0027:\u0027 characters, then single_locale\n  is barely written to, and can be used to jump over the stack\n  guard-page. \n\n  Moreover, if __dcigettext() finds the message to be translated, then\n  _nl_find_msg() strdup()licates the OUTPUT_CHARSET environment variable\n  and allows a local attacker to immediately smash the stack and gain\n  control of the instruction pointer (the eip register, on i386), as\n  detailed in Step 4a. \n\n  We exploited this stack-clash against Sudo and su, but most of the\n  SUID (set-user-ID) and SGID (set-group-ID) binaries that call\n  setlocale(LC_ALL, \"\") and __dcigettext() or its derivatives (the\n  *gettext() functions, the _() convenience macro, the strerror()\n  function) are exploitable. \n\n- The glibc\u0027s vfprintf() function (called by the *printf() family of\n  functions) alloca()tes a stack-based work buffer of up to 64KB\n  (__MAX_ALLOCA_CUTOFF) if a width or precision is greater than 1KB\n  (WORK_BUFFER_SIZE). \n\n  If the corresponding format specifier is %s then this work buffer is\n  never written to and can be used to jump over the stack guard-page. \n\n  None of our exploits is based on this method, but it was one of our\n  ideas to exploit Exim remotely, as mentioned in IV.1.1. \n\n- The glibc\u0027s getaddrinfo() function calls gaih_inet(), which\n  alloca()tes tmpbuf, a stack-based buffer of up to 64KB\n  (__MAX_ALLOCA_CUTOFF) that may be used to jump over the stack\n  guard-page. \n\n  Moreover, gaih_inet() calls the gethostbyname*() functions, which\n  malloc()ate a heap-based DNS response of up to 64KB (MAXPACKET) that\n  may allow a remote attacker to immediately smash the stack, as\n  detailed in Step 4a. \n\n  None of our exploits is based on this method, but it may be the key to\n  the remote exploitation of stack-clashes. \n\n- The glibc\u0027s run-time dynamic linker ld.so alloca()tes llp_tmp, a\n  stack-based copy of the LD_LIBRARY_PATH environment variable. If\n  LD_LIBRARY_PATH contains Dynamic String Tokens (DSTs), they are first\n  expanded: llp_tmp can be larger than 128KB (MAX_ARG_STRLEN) and not\n  fully written to, and can therefore be used to jump over the stack\n  guard-page and smash the memory region mapped directly below, as\n  detailed in Step 4b. \n\n  We exploited this ld.so stack-clash in two data-only attacks that\n  bypass NX (No-eXecute) and ASLR (Address Space Layout Randomization)\n  and obtain a privileged shell through most SUID and SGID binaries on\n  most i386 Linux distributions. \n\n- Several local and remote applications allocate a 256KB stack-based\n  \"gid_t buffer[NGROUPS_MAX];\" that is not fully written to and can be\n  used to move the stack-pointer to the start of the stack (Step 2) and\n  jump over the guard-page (Step 3). For example, Exim\u0027s main() function\n  and older versions of util-linux\u0027s su. \n\n  None of our exploits is based on this method, but an experimental\n  version of our Exim exploit unexpectedly gained control of eip after\n  the group_list[] buffer had jumped over the stack guard-page. \n\n========================================================================\nII.3.4. Step 4: Either smash the stack with another memory region (Step\n4a) or smash another memory region with the stack (Step 4b)\n========================================================================\n\n    Smash and grab, it\u0027s that kind of world. \n                              --The Clash, \"One Emotion\"\n\nIn Step 3, a function allocates a large stack-based buffer and jumps\nover the stack guard-page into the memory region mapped directly below;\nin Step 4, before this function returns and jumps back into the stack:\n\n- Step 4a: a write to the memory region mapped below the stack (where\n  esp still points to) effectively smashes the stack. We exploit this\n  general method for completing Step 4 in Exim, Sudo, and su:\n\n  . we overwrite a return-address on the stack and gain control of eip;\n\n  . we return-into-libc (into system() or __libc_dlopen()) to defeat NX;\n\n  . we brute-force ASLR (8 bits of entropy) if CVE-2016-3672 is patched;\n\n  . we bypass SSP (Stack-Smashing Protector) because we overwrite the\n    return-address of a function that is not protected by a stack canary\n    (the memcpy() that smashes the stack usually overwrites its own\n    stack-frame and return-address). \n\n- Step 4b: a write to the stack effectively smashes the memory region\n  mapped below (where esp still points to). This second method for\n  completing Step 4 is application-specific (it depends on the contents\n  of the memory region that we smash) unless we exploit the run-time\n  dynamic linker ld.so:\n\n  . on Solaris, we devised a general method for smashing ld.so\u0027s\n    read-write segment, overwriting one of its function pointers, and\n    executing our own shell-code;\n\n  . on Linux, we exploited most SUID and SGID binaries through ld.so:\n    our \"hwcap\" exploit smashes an mmap()ed string, and our \".dynamic\"\n    exploit smashes a PIE\u0027s read-write segment before it is mprotect()ed\n    read-only by Full RELRO (Full RELocate Read-Only -- GNU_RELRO and\n    BIND_NOW). \n\n\n========================================================================\nIII. Solutions\n========================================================================\n\nBased on our research, we recommend that the affected operating systems:\n\n- Increase the size of the stack guard-page to at least 1MB, and allow\n  system administrators to easily modify this value (for example,\n  grsecurity/PaX introduced /proc/sys/vm/heap_stack_gap in 2010). \n\n  This first, short-term solution is cheap, but it can be defeated by a\n  very large stack-based buffer. \n\n- Recompile all userland code (ld.so, libraries, binaries) with GCC\u0027s\n  \"-fstack-check\" option, which prevents the stack-pointer from moving\n  into another memory region without accessing the stack guard-page (it\n  writes one word to every 4KB page allocated on the stack). \n\n  This second, long-term solution is expensive, but it cannot be\n  defeated (even if the stack guard-page is only 4KB, one page) --\n  unless a vulnerability is discovered in the implementation of the\n  stack guard-page or the \"-fstack-check\" option. \n\n\n========================================================================\nIV. Results\n========================================================================\n\n========================================================================\nIV.1. Linux\n========================================================================\n\n========================================================================\nIV.1.1. Exim\n========================================================================\n\nDebian 8.5\n\nCrude exploitation\n\nOur first exploit, a Local Privilege Escalation against Exim\u0027s SUID-root\nPIE (Position-Independent Executable) on i386 Debian 8.5, simply follows\nthe four sequential steps outlined in II.3. \n\nStep 1: Clash the stack with the heap\n\nTo reach the start of the stack with the end of the heap (man brk), we\npermanently leak memory through multiple -p command-line arguments that\nare malloc()ated by Exim but never free()d (CVE-2017-1000369) -- we call\nsuch a malloc()ated chunk of heap memory a \"memleak-chunk\". \n\nBecause the -p argument strings are originally allocated on the stack by\nexecve(), we must cover half of the initial heap-stack distance (between\nthe start of the heap and the end of the stack) with stack memory, and\nhalf of this distance with heap memory. \n\nIf we set the RLIMIT_STACK to 136MB (MIN_GAP, arch/x86/mm/mmap.c) then\nthe initial heap-stack distance is minimal (randomized in a [96MB,137MB]\nrange), but we cannot reach the stack with the heap because of the 1/4\nlimit imposed by the kernel on the argument and environment strings (man\nexecve): 136MB/4=34MB of -p argument strings cannot cover 96MB/2=48MB,\nhalf of the minimum heap-stack distance. \n\nMoreover, if we increase the RLIMIT_STACK, the initial heap-stack\ndistance also increases and we still cannot reach the stack with the\nheap. However, if we set the RLIMIT_STACK to RLIM_INFINITY (4GB on i386)\nthen the kernel switches from the default top-down mmap() layout to a\nlegacy bottom-up mmap() layout, and:\n\n- the initial heap-stack distance is approximately 2GB, because the\n  start of the heap (the initial brk()) is randomized above the address\n  0x40000000, and the end of the stack is randomized below the address\n  0xC0000000;\n\n- we can reach the stack with the heap, despite the 1/4 limit imposed by\n  the kernel on the argument and environment strings, because 4GB/4=1GB\n  of -p argument strings can cover 2GB/2=1GB, half of the initial\n  heap-stack distance;\n\n- we clash the stack with the heap around the address 0x80000000. \n\nStep 2: Move the stack-pointer (esp) to the start of the stack\n\nThe 256KB stack-based group_list[] in Exim\u0027s main() naturally consumes\nthe 128KB of initial stack expansion, as mentioned in II.3.2. \n\nStep 3: Jump over the stack guard-page and into the heap\n\nTo move esp from the start of the stack into the heap, without accessing\nthe stack guard-page, we use a malformed -d command-line argument that\nis written to the 32KB (STRING_SPRINTF_BUFFER_SIZE) stack-based buffer\nin Exim\u0027s string_sprintf() function. This buffer is not fully written to\nand hence does not access the stack guard-page, because our -d argument\nstring is much shorter than 32KB. \n\nStep 4a: Smash the stack with the heap\n\nBefore string_sprintf() returns (and moves esp from the heap back into\nthe stack) it calls string_copy(), which malloc()ates and memcpy()es our\n-d argument string to the end of the heap, where esp still points to --\nwe call this malloc()ated chunk of heap memory the \"smashing-chunk\". \n\nThis call to memcpy() therefore smashes its own stack-frame (which is\nnot protected by SSP) with the contents of our smashing-chunk, and we\noverwrite memcpy()\u0027s return-address with the address of libc\u0027s system()\nfunction (which is not randomized by ASLR because Debian 8.5 is\nvulnerable to CVE-2016-3672):\n\n- instead of smashing memcpy()\u0027s stack-frame with an 8-byte pattern (the\n  return-address to system() and its argument) we smash it with a simple\n  4-byte pattern (the return-address to system()), append \".\" to the\n  PATH environment variable, and symlink() our exploit to the string\n  that begins at the address of libc\u0027s system() function;\n\n- system() does not drop our escalated root privileges, because Debian\u0027s\n  /bin/sh is dash, not bash and its -p option (man bash). \n\nThis first version of our Exim exploit obtained a root-shell after\nnearly a week of failed attempts; to improve this result, we analyzed\nevery step of a successful run. \n\nRefined exploitation\n\nStep 1: Clash the stack with the heap\n\n+ The heap must be able to reach the stack [Condition 1]\n\nThe start of the heap is randomized in the 32MB range above the end of\nExim\u0027s PIE (the end of its .bss section), but the growth of the heap is\nsometimes blocked by libraries that are mmap()ed within the same range\n(because of the legacy bottom-up mmap() layout). On Debian 8.5, Exim\u0027s\nlibraries occupy about 8MB and thus block the growth of the heap with a\nprobability of 8MB/32MB = 1/4. \n\nWhen the heap is blocked by the libraries, malloc() switches from brk()\nto mmap()s of 1MB (MMAP_AS_MORECORE_SIZE), and our memory leak reaches\nthe stack with mmap()s instead of the heap. Such a stack-clash is also\nexploitable, but its probability of success is low, as detailed in\nIV.1.6., and we therefore discarded this approach. \n\n+ The heap must always reach the stack, when not blocked by libraries\n\nBecause the initial heap-stack distance (between the start of the heap\nand the end of the stack) is a random variable:\n\n- either we allocate the exact amount of heap memory to cover the mean\n  heap-stack distance, but the probability of success of this approach\n  is low and we therefore discarded it;\n\n- or we allocate enough heap memory to always reach the stack, even when\n  the initial heap-stack distance is maximal; after the heap reaches the\n  stack, our memory leak allocates mmap()s of 1MB above the stack (below\n  0xC0000000) and below the heap (above the libraries), but it must not\n  exhaust the address-space (the 1GB below 0x40000000 is unmappable);\n\n- the final heap-stack distance (between the end of the heap and the\n  start of the stack) is also a random variable:\n\n  . its minimum value is 8KB (the stack guard-page, plus a safety page\n    imposed by the brk() system-call in mm/mmap.c);\n\n  . its maximum value is roughly the size of a memleak-chunk, plus 128KB\n    (DEFAULT_TOP_PAD, malloc/malloc.c). \n\nStep 3: Jump over the stack guard-page and into the heap\n\n- The stack-pointer must jump over the guard-page and land into the free\n  chunk at the end of the heap (the remainder of the heap after malloc()\n  switches from brk() to mmap()), where both the smashing-chunk and\n  memcpy()\u0027s stack-frame are allocated and overwritten in Step 4a\n  [Condition 2];\n\n- The write (of approximately smashing-chunk bytes) to\n  string_sprintf()\u0027s stack-based buffer (which starts where the\n  guard-page jump lands) must not crash into the end of the heap\n  [Condition 3]. \n\nStep 4a: Smash the stack with the heap\n\nThe smashing-chunk must be allocated into the free chunk at the end of\nthe heap:\n\n- the smashing-chunk must not be allocated into the free chunks left\n  over at the end of the 1MB mmap()s [Condition 4];\n\n- the memleak-chunks must not be allocated into the free chunk at the\n  end of the heap [Condition 5]. \n\nIntuitively, the probability of gaining control of eip depends on the\nsize of the smashing-chunk (the guard-page jump\u0027s landing-zone) and the\nsize of the memleak-chunks (which determines the final heap-stack\ndistance). \n\nTo maximize this probability, we wrote a helper program that imposes the\nfollowing conditions on the smashing-chunk and memleak-chunks:\n\n- the smashing-chunk must be smaller than 32KB\n  (STRING_SPRINTF_BUFFER_SIZE) [Condition 3];\n\n- the memleak-chunks must be smaller than 128KB (DEFAULT_MMAP_THRESHOLD,\n  malloc/malloc.c);\n\n- the free chunk at the end of the heap must be larger than twice the\n  smashing-chunk size [Conditions 2 and 3];\n\n- the free chunk at the end of the heap must be smaller than the\n  memleak-chunk size [Condition 5];\n\n- when the final heap-stack distance is minimal, the 32KB\n  (STRING_SPRINTF_BUFFER_SIZE) guard-page jump must land below the free\n  chunk at the end of the heap [Condition 2];\n\n- the free chunks at the end of the 1MB mmap()s must be:\n\n  . either smaller than the smashing-chunk [Condition 4];\n\n  . or larger than the free chunk at the end of the heap (glibc\u0027s\n    malloc() is a best-fit allocator) [Condition 4]. \n\nThe resulting smashing-chunk and memleak-chunk sizes are:\n\nsmash: 10224    memleak: 27656  brk_min: 20464  brk_max: 24552  mmap_top: 25304\nprobability: 1/16 (0.06190487817)\n\nIn theory, the probability of gaining control of eip is 1/21: the\nproduct of the 1/16 probability calculated by this helper program\n(approximately (smashing-chunk / (memleak-chunk + DEFAULT_TOP_PAD))) and\nthe 3/4 probability of reaching the stack with the heap [Condition 1]. \n\nIn practice, on Debian 8.5, our final Exim exploit:\n\n- gains eip control in 1 run out of 28, on average;\n\n- takes 2.5 seconds per run (on a 4GB Virtual Machine);\n\n- has a good chance of obtaining a root-shell after 28*2.5 = 70 seconds;\n\n- uses 4GB of memory (2GB in the Exim process, and 2GB in the process\n  fork()ed by system()). \n\nDebian 8.6\n\nUnlike Debian 8.5, Debian 8.6 is not vulnerable to CVE-2016-3672: after\ngaining eip control in Step 4a (Smash), the probability of successfully\nreturning-into-libc\u0027s system() function is 1/256 (8 bits of entropy --\nlibraries are randomized in a 1MB range but aligned on 4KB). \n\nConsequently, our final Exim exploit has a good chance of obtaining a\nroot-shell on Debian 8.6 after 256*28*2.5 seconds = 5 hours (256*28=7168\nruns). \n\nAs we were drafting this advisory, we tried an alternative approach\nagainst Exim on Debian 8.6: we discovered that its stack is executable,\nbecause it depends on libgnutls-deb0, which depends on libp11-kit, which\ndepends on libffi, which incorrectly requires an executable GNU_STACK\n(CVE-2017-1000376). \n\nInitially, we discarded this approach because our 1GB of -p argument\nstrings on the stack is not executable (_dl_make_stack_executable() only\nmprotect()s the stack below argv[] and envp[]):\n\n41e00000-723d7000 rw-p 00000000 00:00 0          [heap]\n802f1000-80334000 rwxp 00000000 00:00 0          [stack]\n80334000-bfce6000 rw-p 00000000 00:00 0\n\nand because the stack is randomized in an 8MB range but we do not\ncontrol the contents of any large buffer on the executable stack. \n\nLater, we discovered that two 128KB (MAX_ARG_STRLEN) copies of the\nLD_PRELOAD environment variable can be allocated onto the executable\nstack by ld.so\u0027s dl_main() and open_path() functions, automatically\nfreed upon return from these functions, and re-allocated (but not\noverwritten) by Exim\u0027s 256KB stack-based group_list[]. \n\nIn theory, the probability of returning into our shell-code (into these\nexecutable copies of LD_PRELOAD) is 1/32 (2*128KB/8MB), higher than the\n1/256 probability of returning-into-libc. In practice, this alternative\nExim exploit has a good chance of obtaining a root-shell after 1174 runs\n-- instead of 32*28=896 runs in theory, because the two 128KB copies of\nLD_PRELOAD are never perfectly aligned with Exim\u0027s 256KB group_list[] --\nor 1174*2.5 seconds = 50 minutes. \n\nDebian 9 and 10\n\nUnlike Debian 8, Debian 9 and 10 are not vulnerable to offset2lib, a\nminor weakness in Linux\u0027s ASLR that coincidentally affects Step 1\n(Clash) of our stack-clash exploits:\n\nhttps://cybersecurity.upv.es/attacks/offset2lib/offset2lib.html\nhttps://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1fd836dcf00d2028c700c7e44d2c23404062c90\n\nIf we set RLIMIT_STACK to RLIM_INFINITY, the kernel still switches to\nthe legacy bottom-up mmap() layout, and the libraries are randomized in\nthe 1MB range above the address 0x40000000, but Exim\u0027s PIE is randomized\nin the 1MB range above the address 0x80000000 and the heap is randomized\nin the 32MB range above the PIE\u0027s .bss section. As a result:\n\n- the heap is always able to reach the stack, because its growth is\n  never blocked by the libraries -- the theoretical probability of\n  gaining eip control is 1/16, the probability calculated by our helper\n  program;\n\n- the heap clashes with the stack around the address 0xA0000000, because\n  the initial heap-stack distance is 1GB (0xC0000000-0x80000000) and can\n  be covered with 512MB of heap memory and 512MB of stack memory. \n\nRemote exploitation\n\nExim\u0027s string_sprintf() or glibc\u0027s vfprintf() can be used to remotely\ncomplete Steps 3 and 4 of the stack-clash; and the 256KB group_list[] in\nExim\u0027s main() naturally consumes the 128KB of initial stack expansion in\nStep 2; but another 256KB group_list[] in Exim\u0027s exim_setugid() further\ndecreases the start address of the stack and prevents us from remotely\ncompleting Step 2 and exploiting Exim. \n\n========================================================================\nIV.1.2. Sudo\n========================================================================\n\nIntroduction\n\nWe discovered a vulnerability in Sudo\u0027s get_process_ttyname() for Linux:\nthis function opens \"/proc/[pid]/stat\" (man proc) and reads the device\nnumber of the tty from field 7 (tty_nr). Unfortunately, these fields are\nspace-separated and field 2 (comm, the filename of the command) can\ncontain spaces (CVE-2017-1000367). \n\nFor example, if we execute Sudo through the symlink \"./     1 \",\nget_process_ttyname() calls sudo_ttyname_dev() to search for the\nnon-existent tty device number \"1\" in the built-in search_devs[]. \n\nNext, sudo_ttyname_dev() calls the recursive function\nsudo_ttyname_scan() to search for this non-existent tty device number\n\"1\" in a breadth-first traversal of \"/dev\". \n\nLast, we exploit this recursive function during its traversal of the\nworld-writable \"/dev/shm\", and allocate hundreds of megabytes of heap\nmemory from the filesystem (directory pathnames) instead of the stack\n(the command-line arguments and environment variables allocated by our\nother stack-clash exploits). \n\nStep 1: Clash the stack with the heap\n\nsudo_ttyname_scan() strdup()licates the pathnames of the directories and\nsub-directories that it traverses, but does not free() them until it\nreturns. Each one of these \"memleak-chunks\" allocates at most 4KB\n(PATH_MAX) of heap memory. \n\nStep 2: Move the stack-pointer to the start of the stack\n\nThe recursive calls to sudo_ttyname_scan() allocate 4KB (PATH_MAX)\nstack-frames that naturally consume the 128KB of initial stack\nexpansion. \n\nStep 3: Jump over the stack guard-page and into the heap\n\nIf the length of a directory pathname reaches 4KB (PATH_MAX),\nsudo_ttyname_scan() calls warning(), which calls strerror() and _(),\nwhich call gettext() and allow us to jump over the stack guard-page with\nan alloca() of up to 128KB (the LANGUAGE environment variable), as\nexplained in II.3.3. \n\nStep 4a: Smash the stack with the heap\n\nThe self-contained gettext() exploitation method malloc()ates and\nmemcpy()es a \"smashing-chunk\" of up to 128KB (the OUTPUT_CHARSET\nenvironment variable) that smashes memcpy()\u0027s stack-frame and\nreturn-address, as explained in II.3.4. \n\nDebian 8.5\n\nStep 1: Clash the stack with the heap\n\nDebian 8.5 is vulnerable to CVE-2016-3672: if we set RLIMIT_STACK to\nRLIM_INFINITY, the kernel switches to the legacy bottom-up mmap() layout\nand disables the ASLR of Sudo\u0027s PIE and libraries, but still the initial\nheap-stack distance is randomized and roughly 2GB (0xC0000000-0x40000000\n-- the start of the heap is randomized in a 32MB range above 0x40000000,\nand the end of the stack is randomized in the 8MB range below\n0xC0000000). \n\nTo reach the start of the stack with the end of the heap, we allocate\nhundreds of megabytes of heap memory from the filesystem (directory\npathnames), and:\n\n- the heap must be able to reach the stack -- on Debian 8.5, Sudo\u0027s\n  libraries occupy about 3MB and hence block the growth of the heap with\n  a probability of 3MB/32MB ~= 1/11;\n\n- when not blocked by the libraries, the heap must always reach the\n  stack, even when the initial heap-stack distance is maximal (as\n  detailed in IV.1.1.);\n\n- we cover half of the initial heap-stack distance with 1GB of heap\n  memory (the memleak-chunks, strdup()licated directory pathnames);\n\n- we cover the other half of this distance with 1GB of stack memory (the\n  maximum permitted by the kernel\u0027s 1/4 limit on the argument and\n  environment strings) and thus reduce our on-disk inode usage;\n\n- we redirect sudo_ttyname_scan()\u0027s traversal of /dev to /var/tmp\n  (through a symlink planted in /dev/shm) to work around the small\n  number of inodes available in /dev/shm. \n\nAfter the heap reaches the stack and malloc() switches from brk() to\nmmap()s of 1MB:\n\n- the size of the free chunk left over at the end of the heap is a\n  random variable in the [0B,4KB] range -- 4KB (PATH_MAX) is the\n  approximate size of a memleak-chunk;\n\n- the final heap-stack distance (between the end of the heap and the\n  start of the stack) is a random variable in the [8KB,4KB+128KB=132KB]\n  range -- the size of a memleak-chunk plus 128KB (DEFAULT_TOP_PAD);\n\n- sudo_ttyname_scan() recurses a few more times and therefore allocates\n  more stack memory, but this stack expansion is blocked by the heap and\n  crashes into the stack guard-page after 16 recursions on average\n  (132KB/4KB/2, where 132KB is the maximum final heap-stack distance,\n  and 4KB is the size of sudo_ttyname_scan()\u0027s stack-frame). \n\nTo solve this unexpected problem, we:\n\n- first, redirect sudo_ttyname_scan() to a directory tree \"A\" in\n  /var/tmp that recurses and allocates stack memory, but does not\n  allocate heap memory (each directory level contains only one entry,\n  the sub-directory that is connected to the next directory level);\n\n- second, redirect sudo_ttyname_scan() to a directory tree \"B\" in\n  /var/tmp that recurses and allocates heap memory (each directory level\n  contains many entries), but does not allocate more stack memory (it\n  simply consumes the stack memory that was already allocated by the\n  directory tree \"A\"): it does not further expand the stack, and does\n  not crash into the guard-page. \n\nFinally, we increase the speed of our exploit and avoid thousands of\nuseless recursions:\n\n- in each directory level traversed by sudo_ttyname_scan(), we randomly\n  modify the names of its sub-directories until the first call to\n  readdir() returns the only sub-directory that is connected to the next\n  level of the directory tree (all other sub-directories allocate heap\n  memory but are otherwise empty);\n\n- we dup2() Sudo\u0027s stdout and stderr to a pipe with no readers that\n  terminates Sudo with a SIGPIPE if sudo_ttyname_scan() calls warning()\n  and sudo_printf() (a failed exploit attempt, usually because the final\n  heap-stack distance is much longer or shorter than the guard-page\n  jump). \n\nStep 2: Move the stack-pointer to the start of the stack\n\nsudo_ttyname_scan() allocates a 4KB (PATH_MAX) stack-based pathbuf[]\nthat naturally consumes the 128KB of initial stack expansion in fewer\nthan 128KB/4KB=32 recursive calls. \n\nThe recursive calls to sudo_ttyname_scan() allocate less than 8MB of\nstack memory: the maximum number of recursions (PATH_MAX / strlen(\"/a\")\n= 2K) multiplied by the size of sudo_ttyname_scan()\u0027s stack-frame (4KB). \n\nStep 3: Jump over the stack guard-page and into the heap\n\nThe length of the guard-page jump in gettext() is the length of the\nLANGUAGE environment variable (at most 128KB, MAX_ARG_STRLEN): we take a\n64KB jump, well within the range of the final heap-stack distance; this\njump then lands into the free chunk at the end of the heap, where the\nsmashing-chunk will be allocated in Step 4a, with a probability of\n(smashing-chunk / (memleak-chunk + DEFAULT_TOP_PAD)). \n\nIf available, we assign \"C.UTF-8\" to the LC_ALL environment variable,\nand prepend \"be\" to our 64KB LANGUAGE environment variable, because\nthese minimal locales do not interfere with our heap feng-shui. \n\nStep 4a: Smash the stack with the heap\n\nIn gettext(), the smashing-chunk (a malloc() and memcpy() of the\nOUTPUT_CHARSET environment variable) must be allocated into the free\nchunk at the end of the heap, where the stack-frame of memcpy() is also\nallocated. \n\nFirst, if the size of our memleak-chunks is exactly 4KB+8B\n(PATH_MAX+MALLOC_ALIGNMENT), then:\n\n- the size of the free chunk at the end of the heap is a random variable\n  in the [0B,4KB] range;\n\n- the size of the free chunks left over at the end of the 1MB mmap()s is\n  roughly 1MB%(4KB+8B)=2KB. \n\nSecond, if the size of our smashing-chunk is about 2KB+256B\n(PATH_MAX/2+NAME_MAX), then:\n\n- it is always larger than (and never allocated into) the free chunks at\n  the end of the 1MB mmap()s;\n\n- it is smaller than (and allocated into) the free chunk at the end of\n  the heap with a probability of roughly 1-(2KB+256B)/4KB. \n\nLast, in each level of our directory tree \"B\", sudo_ttyname_scan()\nmalloc()ates and realloc()ates an array of pointers to sub-directories,\nbut these realloc()s prevent the smashing-chunk from being allocated\ninto the free chunk at the end of the heap:\n\n- they create holes in the heap, where the smashing-chunk may be\n  allocated to;\n\n- they may allocate the free chunk at the end of the heap, where the\n  smashing-chunk should be allocated to. \n\nTo solve these problems, we carefully calculate the number of\nsub-directories in each level of our directory tree \"B\":\n\n- we limit the size of the realloc()s -- and hence the size of the holes\n  that they create -- to 4KB+2KB:\n\n  . either a memleak-chunk is allocated into such a hole, and the\n    remainder is smaller than the smashing-chunk (\"not a fit\");\n\n  . or such a hole is not allocated, but it is larger than the largest\n    free chunk at the end of the heap (\"a worse fit\");\n\n- we gradually reduce the final size of the realloc()s in the last\n  levels of our directory tree \"B\", and hence re-allocate the holes\n  created in the previous levels. \n\nIn theory, on Debian 8.5, the probability of gaining control of eip is\napproximately 1/148, the product of:\n\n- (Step 1) the probability of reaching the stack with the heap:\n  1-3MB/32MB;\n\n- (Step 3) the probability of jumping over the stack guard-page and into\n  the free chunk at the end of the heap: (2KB+256B) / (4KB+8B + 128KB);\n\n- (Step 4a) the probability of allocating the smashing-chunk into the\n  free chunk at the end of the heap: 1-(2KB+256B)/4KB. \n\nIn practice, on Debian 8.5, this Sudo exploit:\n\n- gains eip control in 1 run out of 200, on average;\n\n- takes 2.8 seconds per run (on a 4GB Virtual Machine);\n\n- has a good chance of obtaining a root-shell after 200 * 2.8 seconds =\n  9 minutes;\n\n- uses 2GB of memory. \n\nNote: we do not return-into-libc\u0027s system() in Step 4a because /bin/sh\nmay be bash, which drops our escalated root privileges upon execution. \nInstead, we:\n\n- either return-into-libc\u0027s __gconv_find_shlib() function through\n  find_module(), which loads this function\u0027s argument from -0x20(%ebp);\n\n- or return-into-libc\u0027s __libc_dlopen_mode() function through\n  nss_load_library(), which loads this function\u0027s argument from\n  -0x1c(%ebp);\n\n- search the libc for a relative pathname that contains a slash\n  character (for example, \"./fork.c\") and pass its address to\n  __gconv_find_shlib() or __libc_dlopen_mode();\n\n- symlink() our PIE exploit to this pathname, and let Sudo execute our\n  _init() constructor as root, upon successful exploitation. \n\nDebian 8.6\n\nUnlike Debian 8.5, Debian 8.6 is not vulnerable to CVE-2016-3672: Sudo\u0027s\nPIE and libraries are always randomized, even if we set RLIMIT_STACK to\nRLIM_INFINITY; the probability of successfully returning-into-libc,\nafter gaining eip control in Step 4a (Smash), is 1/256. \n\nHowever, Debian 8.6 is still vulnerable to offset2lib, the minor\nweakness in Linux\u0027s ASLR that coincidentally affects Step 1 (Clash) of\nour stack-clash exploits:\n\n- if we set RLIMIT_STACK to 136MB (MIN_GAP) or less (the default is\n  8MB), then the initial heap-stack distance (between the start of the\n  heap and the end of the stack) is minimal, a random variable in the\n  [96MB,137MB] range;\n\n- instead of allocating 1GB of heap memory and 1GB of stack memory to\n  clash the stack with the heap, we merely allocate 137MB of heap memory\n  (directory pathnames from our directory tree \"B\") and no stack memory. \n\nIn theory, on Debian 8.6, the probability of gaining eip control is\n1/134 (instead of 1/148 on Debian 8.5) because the growth of the heap is\nnever blocked by Sudo\u0027s libraries; and in practice, this Sudo exploit\ntakes only 0.15 second per run (instead of 2.8 on Debian 8.5). \n\nIndependent exploitation\n\nThe vulnerability that we discovered in Sudo\u0027s get_process_ttyname()\nfunction for Linux (CVE-2017-1000367) is exploitable independently of\nits stack-clash repercussions: through this vulnerability, a local user\ncan pretend that his tty is any character device on the filesystem, and\nafter two race conditions, he can pretend that his tty is any file on\nthe filesystem. \n\nOn an SELinux-enabled system, if a user is Sudoer for a command that\ndoes not grant him full root privileges, he can overwrite any file on\nthe filesystem (including root-owned files) with this command\u0027s output,\nbecause relabel_tty() (in src/selinux.c) calls open(O_RDWR|O_NONBLOCK)\non his tty and dup2()s it to the command\u0027s stdin, stdout, and stderr. \n\nTo exploit this vulnerability, we:\n\n- create a directory \"/dev/shm/_tmp\" (to work around\n  /proc/sys/fs/protected_symlinks), and a symlink \"/dev/shm/_tmp/_tty\"\n  to a non-existent pty \"/dev/pts/57\", whose device number is 34873;\n\n- run Sudo through a symlink \"/dev/shm/_tmp/     34873 \" that spoofs the\n  device number of this non-existent pty;\n\n- set the flag CD_RBAC_ENABLED through the command-line option \"-r role\"\n  (where \"role\" can be our current role, for example \"unconfined_r\");\n\n- monitor our directory \"/dev/shm/_tmp\" (for an IN_OPEN inotify event)\n  and wait until Sudo opendir()s it (because sudo_ttyname_dev() cannot\n  find our non-existent pty in \"/dev/pts/\");\n\n- SIGSTOP Sudo, call openpty() until it creates our non-existent pty,\n  and SIGCONT Sudo;\n\n- monitor our directory \"/dev/shm/_tmp\" (for an IN_CLOSE_NOWRITE inotify\n  event) and wait until Sudo closedir()s it;\n\n- SIGSTOP Sudo, replace the symlink \"/dev/shm/_tmp/_tty\" to our\n  now-existent pty with a symlink to the file that we want to overwrite\n  (for example \"/etc/passwd\"), and SIGCONT Sudo;\n\n- control the output of the command executed by Sudo (the output that\n  overwrites \"/etc/passwd\"):\n\n  . either through a command-specific method;\n\n  . or through a general method such as \"--\\nHELLO\\nWORLD\\n\" (by\n    default, getopt() prints an error message to stderr if it does not\n    recognize an option character). \n\nTo reliably win the two SIGSTOP races, we preempt the Sudo process: we\nsetpriority() it to the lowest priority, sched_setscheduler() it to\nSCHED_IDLE, and sched_setaffinity() it to the same CPU as our exploit. \n\n[john@localhost ~]$ head -n 8 /etc/passwd\nroot:x:0:0:root:/root:/bin/bash\nbin:x:1:1:bin:/bin:/sbin/nologin\ndaemon:x:2:2:daemon:/sbin:/sbin/nologin\nadm:x:3:4:adm:/var/adm:/sbin/nologin\nlp:x:4:7:lp:/var/spool/lpd:/sbin/nologin\nsync:x:5:0:sync:/sbin:/bin/sync\nshutdown:x:6:0:shutdown:/sbin:/sbin/shutdown\nhalt:x:7:0:halt:/sbin:/sbin/halt\n\n[john@localhost ~]$ sudo -l\n[sudo] password for john:\n... \nUser john may run the following commands on localhost:\n    (ALL) /usr/bin/sum\n\n[john@localhost ~]$ ./Linux_sudo_CVE-2017-1000367 /usr/bin/sum $\u0027--\\nHELLO\\nWORLD\\n\u0027\n[sudo] password for john:\n\n[john@localhost ~]$ head -n 8 /etc/passwd\n/usr/bin/sum: unrecognized option \u0027--\nHELLO\nWORLD\n\u0027\nTry \u0027/usr/bin/sum --help\u0027 for more information. \nogin\nadm:x:3:4:adm:/var/adm:/sbin/nologin\nlp:x:4:7:lp:/var/spool/lpd:/sbin/nologin\n\n========================================================================\nIV.1.3. ld.so \"hwcap\" exploit\n========================================================================\n\n\"ld.so and ld-linux.so* find and load the shared libraries needed by a\nprogram, prepare the program to run, and then run it.\" (man ld.so)\n\nThrough ld.so, most SUID and SGID binaries on most i386 Linux\ndistributions are exploitable. For example: Debian 7, 8, 9, 10; Fedora\n23, 24, 25; CentOS 5, 6, 7. \n\nDebian 8.5\n\nStep 1: Clash the stack with anonymous mmap()s\n\nThe minimal malloc() implementation in ld.so calls mmap(), not brk(), to\nobtain memory from the system, and it never calls munmap(). To reach the\nstart of the stack with anonymous mmap()s, we:\n\n- set RLIMIT_STACK to RLIM_INFINITY and switch from the default top-down\n  mmap() layout to the legacy bottom-up mmap() layout;\n\n- cover half of the initial mmap-stack distance\n  (0xC0000000-0x40000000=2GB) with 1GB of stack memory (the maximum\n  permitted by the kernel\u0027s 1/4 limit on the argument and environment\n  strings);\n\n- cover the other half of this distance with 1GB of anonymous mmap()s,\n  through multiple LD_AUDIT environment variables that permanently leak\n  millions of audit_list structures (CVE-2017-1000366) in\n  process_envvars() and process_dl_audit() (elf/rtld.c). \n\nStep 2: Move the stack-pointer to the start of the stack\n\nTo consume the 128KB of initial stack expansion, we simply pass 128KB of\nargv[] and envp[] pointers to execve(), as explained in II.3.2. \n\nStep 3: Jump over the stack guard-page and into the anonymous mmap()s\n\n_dl_init_paths() (elf/dl-load.c), which is called by dl_main() after\nprocess_envvars(), alloca()tes llp_tmp, a stack-based buffer large\nenough to hold the LD_LIBRARY_PATH environment variable and any\ncombination of Dynamic String Token (DST) replacement strings. To\ncalculate the size of llp_tmp, _dl_init_paths() must:\n\n- first, scan LD_LIBRARY_PATH and count all DSTs ($LIB, $PLATFORM, and\n  $ORIGIN);\n\n- second, multiply the number of DSTs by the length of the longest DST\n  replacement string (on Debian, $LIB is replaced by the 18-char-long\n  \"lib/i386-linux-gnu\", $PLATFORM by \"i386\" or \"i686\", and $ORIGIN by\n  the pathname of the program\u0027s directory, for example \"/bin\" or\n  \"/usr/sbin\" -- the longest DST replacement string is usually\n  \"lib/i386-linux-gnu\");\n\n- last, add the length of the original LD_LIBRARY_PATH. \n\nConsequently, if LD_LIBRARY_PATH contains many DSTs that are replaced by\nthe shortest DST replacement string, then llp_tmp is large but not fully\nwritten to, and can be used to jump over the stack guard-page and into\nthe anonymous mmap()s. \n\nOur ld.so exploits do not use $ORIGIN because it is ignored by several\ndistributions and glibc versions; for example:\n\n2010-12-09  Andreas Schwab  \u003cschwab@redhat.com\u003e\n\n        * elf/dl-object.c (_dl_new_object): Ignore origin of privileged\n        program. \n\nIndex: glibc-2.12-2-gc4ccff1/elf/dl-object.c\n===================================================================\n--- glibc-2.12-2-gc4ccff1.orig/elf/dl-object.c\n+++ glibc-2.12-2-gc4ccff1/elf/dl-object.c\n@@ -214,6 +214,9 @@ _dl_new_object (char *realname, const ch\n     out:\n       new-\u003el_origin = origin;\n     }\n+  else if (INTUSE(__libc_enable_secure) \u0026\u0026 type == lt_executable)\n+    /* The origin of a privileged program cannot be trusted.  */\n+    new-\u003el_origin = (char *) -1;\n\n   return new;\n }\n\nStep 4b: Smash an anonymous mmap() with the stack\n\nBefore _dl_init_paths() returns to dl_main() and jumps back from the\nanonymous mmap()s into the stack, we overwrite the block of mmap()ed\nmemory malloc()ated by _dl_important_hwcaps() with the contents of the\nstack-based buffer llp_tmp. \n\n- The block of memory malloc()ated by _dl_important_hwcaps() is divided\n  in two:\n\n  . The first part (the \"hwcap-pointers\") is an array of r_strlenpair\n    structures that point to the hardware-capability strings stored in\n    the second part of this memory block. The second part (the \"hwcap-strings\") contains strings of\n    hardware-capabilities that are appended to the pathnames of trusted\n    directories, such as \"/lib/\" and \"/lib/i386-linux-gnu/\", when\n    open_path() searches for audit libraries (LD_AUDIT), preload\n    libraries (LD_PRELOAD), or dependent libraries (DT_NEEDED). \n\n    For example, on Debian, when open_path() finds \"libc.so.6\" in\n    \"/lib/i386-linux-gnu/i686/cmov/\", \"i686/cmov/\" is such a\n    hardware-capability string. \n\n- To overwrite the block of memory malloc()ated by\n  _dl_important_hwcaps() with the contents of the stack-based buffer\n  llp_tmp, we divide our LD_LIBRARY_PATH environment variable in two:\n\n  . The first, static part (our \"good-write\") overwrites the first\n    hardware-capability string with characters that we do control. The second, dynamic part (our \"bad-write\") overwrites the last\n    hardware-capability strings with characters that we do not control\n    (the short DST replacement strings that enlarge llp_tmp and allow us\n    to jump over the stack guard-page). \n\nIf our 16-byte-aligned good-write overwrites the 8-byte-aligned first\nhardware-capability string with the 8-byte pattern \"/../tmp/\", and if we\nappend the trusted directory \"/lib\" to our LD_LIBRARY_PATH, then (after\n_dl_init_paths() returns to dl_main()):\n\n- dlmopen_doit() tries to load an LD_AUDIT library \"a\" (our memory leak\n  from Step 1);\n\n- _dl_map_object() searches for \"a\" in the trusted directory \"/lib\" from\n  our LD_LIBRARY_PATH;\n\n- open_path() finds our library \"a\" in \"/lib//../tmp//../tmp//../tmp/\"\n  because we overwrote the first hardware-capability string with the\n  pattern \"/../tmp/\";\n\n- dl_open_worker() executes our library\u0027s _init() constructor, as root. \n\nIn theory, this exploit\u0027s probability of success depends on:\n\n- (event A) the size of rtld_search_dirs.dirs[0], an array of\n  r_search_path_elem structures that are malloc()ated by\n  _dl_init_paths() after the _dl_important_hwcaps(), and must be\n  allocated above the stack (below 0xC0000000), not below the stack\n  where it would interfere with Steps 3 (Jump) and 4b (Smash):\n\nP(A) = 1 - size of rtld_search_dirs.dirs[0] / max stack randomization\n\n- (event B) the size of the hwcap-pointers and the size of our\n  good-write, which must overwrite the first hardware-capability string,\n  but not the first hardware-capability pointer (to this string):\n\nP(B|A) = MIN(size of hwcap-pointers, size of good-write) /\n          (max stack randomization - size of rtld_search_dirs.dirs[0])\n\n- (event C) the size of the hwcap-strings and the size of our bad-write,\n  which must not write past the end of hwcap-strings; but we guarantee\n  that size of hwcap-strings \u003e= size of good-write + size of bad-write:\n\nP(C|B) = 1\n\nIn practice, we use the LD_HWCAP_MASK environment variable to maximize\nthis exploit\u0027s probability of success, because:\n\n- the size of the hwcap-pointers -- which act as a cushion that absorbs\n  the excess of good-write without crashing,\n\n- the size of the hwcap-strings -- which act as a cushion that absorbs\n  the excess of good-write and bad-write without crashing,\n\n- and the size of rtld_search_dirs.dirs[0],\n\nare all proportional to 2^N, where N is the number of supported\nhardware-capabilities that we enable in LD_HWCAP_MASK. \n\nFor example, on Debian 8.5, this exploit:\n\n- has a 1/151 probability of success;\n\n- takes 5.5 seconds per run (on a 4GB Virtual Machine);\n\n- has a good chance of obtaining a root-shell after 151 * 5.5 seconds =\n  14 minutes. \n\nDebian 8.6\n\nUnlike Debian 8.5, Debian 8.6 is not vulnerable to CVE-2016-3672, but\nour ld.so \"hwcap\" exploit is a data-only attack and is not affected by\nthe ASLR of the libraries and PIEs. \n\nDebian 9 and 10\n\nUnlike Debian 8, Debian 9 and 10 are not vulnerable to offset2lib: if we\nset RLIMIT_STACK to RLIM_INFINITY, the libraries are randomized above\nthe address 0x40000000, but the PIE is randomized above 0x80000000\n(instead of 0x40000000 before the offset2lib patch). \n\nUnfortunately, we discovered a vulnerability in the offset2lib patch\n(CVE-2017-1000370): if the PIE is execve()d with 1GB of argument or\nenvironment strings (the maximum permitted by the kernel\u0027s 1/4 limit)\nthen the stack occupies the address 0x80000000, and the PIE is mapped\nabove the address 0x40000000 instead, directly below the libraries. \nThis vulnerability effectively nullifies the offset2lib patch, and\nallows us to reuse our Debian 8 exploit against Debian 9 and 10. \n\n$ ./Linux_offset2lib\nRun #1... \nCVE-2017-1000370 triggered\n40076000-40078000 r-xp 00000000 00:26 25041      /tmp/Linux_offset2lib\n40078000-40079000 r--p 00001000 00:26 25041      /tmp/Linux_offset2lib\n40079000-4009b000 rw-p 00002000 00:26 25041      /tmp/Linux_offset2lib\n4009b000-400c0000 r-xp 00000000 fd:00 8463588    /usr/lib/ld-2.24.so\n400c0000-400c1000 r--p 00024000 fd:00 8463588    /usr/lib/ld-2.24.so\n400c1000-400c2000 rw-p 00025000 fd:00 8463588    /usr/lib/ld-2.24.so\n400c2000-400c4000 r--p 00000000 00:00 0          [vvar]\n400c4000-400c6000 r-xp 00000000 00:00 0          [vdso]\n400c6000-400c8000 rw-p 00000000 00:00 0\n400cf000-402a3000 r-xp 00000000 fd:00 8463595    /usr/lib/libc-2.24.so\n402a3000-402a4000 ---p 001d4000 fd:00 8463595    /usr/lib/libc-2.24.so\n402a4000-402a6000 r--p 001d4000 fd:00 8463595    /usr/lib/libc-2.24.so\n402a6000-402a7000 rw-p 001d6000 fd:00 8463595    /usr/lib/libc-2.24.so\n402a7000-402aa000 rw-p 00000000 00:00 0\n7fcf1000-bfcf2000 rw-p 00000000 00:00 0          [stack]\n\nCaveats\n\n- On Fedora and CentOS, this ld.so \"hwcap\" exploit fails against\n  /usr/bin/passwd and /usr/bin/chage (but it works against all other\n  SUID-root binaries) because of SELinux:\n\ntype=AVC msg=audit(1492091008.983:414): avc:  denied  { execute } for  pid=2169 comm=\"passwd\" path=\"/var/tmp/a\" dev=\"dm-0\" ino=12828063 scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file permissive=0\n\ntype=AVC msg=audit(1492092997.581:487): avc:  denied  { execute } for  pid=2648 comm=\"chage\" path=\"/var/tmp/a\" dev=\"dm-0\" ino=12828063 scontext=unconfined_u:unconfined_r:passwd_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=file permissive=0\n\n- It fails against recent versions of Sudo that specify an RPATH such as\n  \"/usr/lib/sudo\": _dl_map_object() first searches for our LD_AUDIT\n  library in RPATH, but open_path() fails to find our library in\n  \"/usr/lib/sudo//../tmp/\" and crashes as soon as it reaches an\n  overwritten hwcap-pointer. \n\n  This problem can be solved by a 16-byte pattern \"///../../../tmp/\"\n  (instead of the 8-byte pattern \"/../tmp/\") but the exploit\u0027s\n  probability of success would be divided by two. \n\n- On Ubuntu, this ld.so \"hwcap\" exploit always fails, because of the\n  following patch:\n\nDescription: pro-actively disable LD_AUDIT for setuid binaries, regardless\n of where the libraries are loaded from. This is to try to make sure that\n CVE-2010-3856 cannot sneak back in. Upstream is unlikely to take this,\n since it limits the functionality of LD_AUDIT. \nAuthor: Kees Cook \u003ckees@ubuntu.com\u003e\n\nIndex: eglibc-2.15/elf/rtld.c\n===================================================================\n--- eglibc-2.15.orig/elf/rtld.c 2012-05-09 10:05:29.456899131 -0700\n+++ eglibc-2.15/elf/rtld.c      2012-05-09 10:38:53.952009069 -0700\n@@ -2529,7 +2529,7 @@\n   while ((p = (strsep) (\u0026str, \":\")) != NULL)\n     if (p[0] != \u0027\\0\u0027\n        \u0026\u0026 (__builtin_expect (! __libc_enable_secure, 1)\n-           || strchr (p, \u0027/\u0027) == NULL))\n+       ))\n       {\n        /* This is using the local malloc, not the system malloc.  The\n           memory can never be freed.  */\n\n========================================================================\nIV.1.4. ld.so \".dynamic\" exploit\n========================================================================\n\nTo exploit ld.so without the LD_AUDIT memory leak, we rely on a second\nvulnerability that we discovered in the offset2lib patch\n(CVE-2017-1000371):\n\nif we set RLIMIT_STACK to RLIM_INFINITY, and allocate nearly 1GB of\nstack memory (the maximum permitted by the kernel\u0027s 1/4 limit on the\nargument and environment strings) then the stack grows down to almost\n0x80000000, and because the PIE is mapped above 0x80000000, the minimum\ndistance between the end of the PIE\u0027s read-write segment and the start\nof the stack is 4KB (the stack guard-page). \n\n$ ./Linux_offset2lib 0x3f800000\nRun #1... \nRun #2... \nRun #3... \nRun #796... \nRun #797... \nRun #798... \nCVE-2017-1000371 triggered\n4007b000-400a0000 r-xp 00000000 fd:00 8463588    /usr/lib/ld-2.24.so\n400a0000-400a1000 r--p 00024000 fd:00 8463588    /usr/lib/ld-2.24.so\n400a1000-400a2000 rw-p 00025000 fd:00 8463588    /usr/lib/ld-2.24.so\n400a2000-400a4000 r--p 00000000 00:00 0          [vvar]\n400a4000-400a6000 r-xp 00000000 00:00 0          [vdso]\n400a6000-400a8000 rw-p 00000000 00:00 0\n400af000-40283000 r-xp 00000000 fd:00 8463595    /usr/lib/libc-2.24.so\n40283000-40284000 ---p 001d4000 fd:00 8463595    /usr/lib/libc-2.24.so\n40284000-40286000 r--p 001d4000 fd:00 8463595    /usr/lib/libc-2.24.so\n40286000-40287000 rw-p 001d6000 fd:00 8463595    /usr/lib/libc-2.24.so\n40287000-4028a000 rw-p 00000000 00:00 0\n8000a000-8000c000 r-xp 00000000 00:26 25041      /tmp/Linux_offset2lib\n8000c000-8000d000 r--p 00001000 00:26 25041      /tmp/Linux_offset2lib\n8000d000-8002f000 rw-p 00002000 00:26 25041      /tmp/Linux_offset2lib\n80030000-bf831000 rw-p 00000000 00:00 0          [heap]\n\nNote: in this example, the \"[stack]\" is incorrectly displayed as the\n\"[heap]\" by show_map_vma() (in fs/proc/task_mmu.c). \n\nThis completes Step 1: we clash the stack with the PIE\u0027s read-write\nsegment; we complete the remaining steps as in the \"hwcap\" exploit:\n\n- Step 2: we consume the initial stack expansion with 128KB of argv[]\n  and envp[] pointers;\n\n- Step 3: we jump over the stack guard-page and into the PIE\u0027s\n  read-write segment with llp_tmp\u0027s alloca() (in _dl_init_paths());\n\n- Step 4b: we smash the PIE\u0027s read-write segment with llp_tmp\u0027s\n  good-write and bad-write (in _dl_init_paths()); we can smash the\n  following sections:\n\n  + .data and .bss: but we discarded this application-specific approach;\n\n  + .got: although protected by Full RELRO (Full RELocate Read-Only,\n    GNU_RELRO and BIND_NOW) the .got is still writable when we smash it\n    in _dl_init_paths(); however, within ld.so, the .got is written to\n    but never read from, and we therefore discarded this approach;\n\n  + .dynamic: our favored approach. \n\nOn i386, the .dynamic section is an array of Elf32_Dyn structures (an\nint32 d_tag, and the union of uint32 d_val and uint32 d_ptr) that\ncontains entries such as:\n\n- DT_STRTAB, a pointer to the PIE\u0027s .dynstr section (a read-only string\n  table): its d_tag (DT_STRTAB) is read (by elf_get_dynamic_info())\n  before we smash it in _dl_init_paths(), but its d_ptr is read (by\n  _dl_map_object_deps()) after we smash it in _dl_init_paths();\n\n- DT_NEEDED, an offset into the .dynstr section: the pathname of a\n  dependent library that must be loaded by _dl_map_object_deps(). \n\nIf we overwrite the entire .dynamic section with the following 8-byte\npattern (an Elf32_Dyn structure):\n\n- a DT_NEEDED d_tag,\n\n- a d_val equal to half the address of our own string table on the stack\n  (16MB of argument strings, enough to defeat the 8MB stack\n  randomization),\n\nthen _dl_map_object_deps() reads the pathname of this dependent library\nfrom DT_STRTAB.d_ptr + DT_NEEDED.d_val = our_strtab/2 + our_strtab/2 =\nour_strtab, and loads our own library, as root. This 8-byte pattern is\nsimple, but poses two problems:\n\n- DT_NEEDED is an int32 equal to 1, but we smash the .dynamic section\n  with a string copy that cannot contain null-bytes: to solve this first\n  problem we use DT_AUXILIARY instead, which is equivalent but equal to\n  0x7ffffffd;\n\n- ld.so crashes before it returns from dl_main() (before it calls\n  _dl_init() and executes our library\u0027s _init() constructor):\n\n  . in _dl_map_object_deps() because of our DT_AUXILIARY entry;\n\n  . in version_check_doit() because we overwrote the DT_VERNEED entry;\n\n  . in _dl_relocate_object() because we overwrote the DT_REL, DT_RELSZ,\n    and DT_RELCOUNT entries. \n\nTo solve this second problem, we could overwrite the .dynamic section\nwith a more complicated pattern that repairs these entries, but our\nexploit\u0027s probability of success would decrease significantly. \n\nInstead, we take control of ld.so\u0027s execution flow as soon as\n_dl_map_object_deps() loads our library:\n\n- our library contains three executable LOAD segments,\n\n- but only the first and last segments are sanity-checked by\n  _dl_map_object_from_fd() and _dl_map_segments(),\n\n- and all segments except the first are mmap()ed with MAP_FIXED by\n  _dl_map_segments(),\n\n- so we can mmap() our second segment anywhere -- we mmap() it on top of\n  ld.so\u0027s executable segment,\n\n- and return into our own code (instead of ld.so\u0027s) as soon as this\n  second mmap() system-call returns. \n\nProbabilities\n\nThe \"hwcap\" exploit taught us that this \".dynamic\" exploit\u0027s probability\nof success depends on:\n\n- the size of the cushion below the .dynamic section, which can absorb\n  the excess of \"good-write\" without crashing: the padding bytes between\n  the start of the PIE\u0027s read-write segment and the start of its first\n  read-write section;\n\n- the size of the cushion above the .dynamic section, which can absorb\n  the excess of \"good-write\" and \"bad-write\" without crashing: the .got,\n  .data, and .bss sections. \n\nIf we guarantee that (cushion above .dynamic \u003e good-write + bad-write),\nthen the theoretical probability of success is approximately:\n\nMIN(cushion below .dynamic, good-write) / max stack randomization\n\nThe maximum size of the cushion below the .dynamic section is 4KB (one\npage) and hence the maximum probability of success is 4KB/8MB=1/2048. \nIn practice, on Ubuntu 16.04.2:\n\n- the highest probability is 1/2589 (/bin/su) and the lowest probability\n  is 1/9225 (/usr/lib/eject/dmcrypt-get-device);\n\n- each run uses 1GB of memory and takes 1.5 seconds (on a 4GB Virtual\n  Machine);\n\n- this ld.so \".dynamic\" exploit has a good chance of obtaining a\n  root-shell after 2589 * 1.5 seconds ~= 1 hour. \n\n========================================================================\nIV.1.5. /bin/su\n========================================================================\n\nAs we were drafting this advisory, we discovered a general method for\ncompleting Step 1 (Clash) of the stack-clash exploitation: the Linux\nkernel limits the size of the command-line arguments and environment\nvariables to 1/4 of the RLIMIT_STACK, but it imposes this limit on the\nargument and environment strings, not on the argv[] and envp[] pointers\nto these strings (CVE-2017-1000365). \n\nOn i386, if we set RLIMIT_STACK to RLIM_INFINITY, the maximum number of\nargv[] and envp[] pointers is 1G (1/4 of the RLIMIT_STACK, divided by\n1B, the minimum size of an argument or environment string). In theory,\nthe maximum size of the initial stack is therefore 1G*(1B+4B)=5GB. In\npractice, this would exhaust the address-space and allows us to clash\nthe stack with the memory region that is mapped below, without an\napplication-specific memory leak. \n\nThis discovery allowed us to write alternative versions of our\nstack-clash exploits; for example:\n\n- an ld.so \"hwcap\" exploit against Ubuntu: we replace the LD_AUDIT\n  memory leak with 2GB of stack memory (1GB of argument and environment\n  strings, and 1GB of argv[] and envp[] pointers) and replace the\n  LD_AUDIT library with an LD_PRELOAD library;\n\n- an ld.so \".dynamic\" exploit against systems vulnerable to offset2lib:\n  we reach the end of the PIE\u0027s read-write segment with only 128MB of\n  stack memory (argument and environment strings and pointers). \n\nThese proofs-of-concept demonstrate a general method for completing Step\n1 (Clash), but they are much slower than their original versions (10-20\nseconds per run) because they pass millions of argv[] and envp[]\npointers to execve(). \n\nMoreover, this discovery allowed us to exploit SUID binaries through\ngeneral methods that do not depend on application-specific or ld.so\nvulnerabilities; if a SUID binary calls setlocale(LC_ALL, \"\"); and\ngettext() (or a derivative such as strerror() or _()), then it is\nexploitable:\n\n- Step 1: we clash the stack with the heap through millions of argument\n  and environment strings and pointers;\n\n- Step 2: we consume the initial stack expansion with 128KB of argument\n  and environment pointers;\n\n- Step 3: we jump over the stack guard-page and into the heap with the\n  alloca()tion of the LANGUAGE environment variable in gettext();\n\n- Step 4a: we smash the stack with the malloc()ation of the\n  OUTPUT_CHARSET environment variable in gettext() and thus gain control\n  of eip. \n\nFor example, we exploited Debian\u0027s /bin/su (from the shadow-utils): its\nmain() function calls setlocale() and save_caller_context(), which calls\ngettext() (through _()) if its stdin is not a tty. \n\nDebian 8.5\n\nDebian 8.5 is vulnerable to CVE-2016-3672: we set RLIMIT_STACK to\nRLIM_INFINITY and disable ASLR, clash the stack with the heap through\n2GB of argument and environment strings and pointers (1GB of strings,\n1GB of pointers), and return-into-libc\u0027s system() or __libc_dlopen():\n\n- the system() version uses 4GB of memory (2GB in the /bin/su process,\n  and 2GB in the process fork()ed by system());\n\n- the __libc_dlopen() version uses only 2GB of memory, but ebp must\n  point to our smashed data on the stack. \n\nDebian 8.6\n\nDebian 8.6 is vulnerable to offset2lib but not to CVE-2016-3672: we must\nbrute-force the libc\u0027s ASLR (8 bits of entropy), but we clash the stack\nwith the heap through only 128MB of argument and environment strings and\npointers -- this /bin/su exploit can be parallelized. \n\n========================================================================\nIV.1.6. Grsecurity/PaX\n========================================================================\n\nhttps://grsecurity.net/\n\nIn 2010, grsecurity/PaX introduced a configurable stack guard-page: its\nsize can be modified through /proc/sys/vm/heap_stack_gap and is 64KB by\ndefault (unlike the hard-coded 4KB stack guard-page in the vanilla\nkernel). \n\nUnfortunately, a 64KB stack guard-page is not large enough, and can be\njumped over with ld.so or gettext() (CVE-2017-1000377); for example, we\nwere able to gain eip control against Sudo, but we were unable to obtain\na root-shell or gain eip control against another application, because\ngrsecurity/PaX imposes the following security measures:\n\n- it restricts the RLIMIT_STACK of SUID binaries to 8MB, which prevents\n  us from switching to the legacy bottom-up mmap() layout (Step 1);\n\n- it restricts the argument and environment strings to 512KB, which\n  prevents us from clashing the stack through megabytes of command-line\n  arguments and environment variables (Step 1);\n\n- it randomizes the PIE and libraries with 16 bits of entropy (instead\n  of 8 bits in vanilla), which prevents us from brute-forcing the ASLR\n  and returning-into-libc (Step 4a);\n\n- it implements /proc/sys/kernel/grsecurity/deter_bruteforce (enabled by\n  default), which limits the number of SUID crashes to 1 every 15\n  minutes (all Steps) and makes exploitation impossible. \n\nSudo\n\nThe vulnerability that we discovered in Sudo\u0027s get_process_ttyname()\n(CVE-2017-1000367) allows us to:\n\n- Step 1: clash the stack with 3GB of heap memory from the filesystem\n  (directory pathnames) and bypass grsecurity/PaX\u0027s 512KB limit on the\n  argument and environment strings;\n\n- Step 2: consume the 128KB of initial stack expansion with 3MB of\n  recursive function calls and avoid grsecurity/PaX\u0027s 8MB restriction on\n  the RLIMIT_STACK;\n\n- Step 3: jump over grsecurity/PaX\u0027s 64KB stack guard-page with a 128KB\n  (MAX_ARG_STRLEN) alloca()tion of the LANGUAGE environment variable in\n  gettext();\n\n- Step 4a: smash the stack with a 128KB (MAX_ARG_STRLEN) malloc()ation\n  of the OUTPUT_CHARSET environment variable in gettext() -- the\n  \"smashing-chunk\" -- and thus gain control of eip. \n\nIn Step 1, we nearly exhaust the address-space until finally malloc()\nswitches from brk() to 1MB mmap()s and reaches the start of the stack\nwith the very last 1MB mmap() that we allocate. The exact amount of\nmemory that we must allocate to reach the stack with our last 1MB mmap()\ndepends on the sum of three random variables: the 256MB randomization of\nthe stack, the 64MB randomization of the heap, and the 1MB randomization\nof the NULL region. \n\nTo maximize the probability of jumping over the stack guard-page, into\nour last 1MB mmap() below the stack, and overwriting a return-address on\nthe stack with our smashing-chunk:\n\n- (Step 1) we must allocate the mean amount of memory to reach the stack\n  with our last 1MB mmap(): the sum of three uniform random variables is\n  not uniform (https://en.wikipedia.org/wiki/Irwin-Hall_distribution),\n  but the values within the 256MB-64MB-1MB=191MB plateau at the center\n  of this bell-shaped probability distribution occur with a uniform and\n  maximum probability of (1MB*64MB)/(1MB*64MB*256MB)=1/256MB;\n\n- (Step 1) the end of our last 1MB mmap() must be allocated at a\n  distance within [stack guard-page (64KB), guard-page jump (128KB)]\n  below the start of the stack: the guard-page jump (Step 3) then lands\n  at a distance d within [0, guard-page jump - stack guard-page (64KB)]\n  below the end of our last 1MB mmap();\n\n- (Step 4a) the end of our smashing-chunk must be allocated at the end\n  of our last 1MB mmap(), above the landing-point of the guard-page\n  jump: our smashing-chunk then overwrites a return-address on the\n  stack, below the landing-point of the guard-page jump. \n\nIn theory, this probability is roughly:\n\nSUM(d = 1; d \u003c guard-page jump - stack guard-page; d++) d / (256MB*1MB)\n\n          ~= ((guard-page jump - stack guard-page)^2 / 2) / (256MB*1MB)\n\n          ~= 1 / 2^17\n\nIn practice, we tested this Sudo proof-of-concept on an i386 Debian 8.6\nprotected by the linux-grsec package from the jessie-backports, but we\nmanually disabled /proc/sys/kernel/grsecurity/deter_bruteforce:\n\n- it uses 3GB of memory, and 800K on-disk inodes;\n\n- it takes 5.5 seconds per run (on a 4GB Virtual Machine);\n\n- it has a good chance of gaining eip control after 2^17 * 5.5 seconds =\n  200 hours; in our test:\n\nPAX: From 192.168.56.1: execution attempt in: \u003cheap\u003e, 1b068000-a100d000 1b068000\nPAX: terminating task: /usr/bin/sudo(     1 ):25465, uid/euid: 1000/0, PC: 41414141, SP: b8844f30\nPAX: bytes at PC: 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41 41\nPAX: bytes at SP-4: 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141 41414141\n\nHowever, brute-forcing the ASLR to obtain a root-shell would take ~1500\nyears and makes exploitation impossible. \n\nMoreover, if we enable /proc/sys/kernel/grsecurity/deter_bruteforce,\ngaining eip control would take ~1365 days, and obtaining a root-shell\nwould take thousands of years. \n\n========================================================================\nIV.1.7. 64-bit exploitation\n========================================================================\n\nIntroduction\n\nThe address-space of a 64-bit process is so vast that we initially\nthought it was impossible to clash the stack with another memory region;\nwe were wrong. \n\nLinux\u0027s execve() first randomizes the end of the mmap region (which\ngrows top-down by default) and then randomizes the end of the stack\nregion (which grows down, on x86). On amd64, the initial mmap-stack\ndistance (between the end of the mmap region and the end of the stack\nregion) is minimal when RLIMIT_STACK is lower than or equal to MIN_GAP\n(mmap_base() in arch/x86/mm/mmap.c), and then:\n\n- the end of the mmap region is equal to (as calculated by\n  arch_pick_mmap_layout() in arch/x86/mm/mmap.c):\n\n  mmap_end = TASK_SIZE - MIN_GAP - arch_mmap_rnd()\n\n  where:\n\n  . TASK_SIZE is the highest address of the user-space (0x7ffffffff000)\n\n  . MIN_GAP = 128MB + stack_maxrandom_size()\n\n  . stack_maxrandom_size() is ~16GB (or ~4GB if the kernel is vulnerable\n    to CVE-2015-1593, but we do not consider this case here)\n\n  . arch_mmap_rnd() is a random variable in the [0B,1TB] range\n\n- the end of the stack region is equal to (as calculated by\n  randomize_stack_top() in fs/binfmt_elf.c):\n\n  stack_end = TASK_SIZE - \"stack_rand\"\n\n  where:\n\n  . \"stack_rand\" is a random variable in the [0, stack_maxrandom_size()]\n    range\n\n- the initial mmap-stack distance is therefore equal to:\n\n  stack_end - mmap_end = MIN_GAP + arch_mmap_rnd() - \"stack_rand\"\n\n    = 128MB + stack_maxrandom_size() - \"stack_rand\" + arch_mmap_rnd()\n\n    = 128MB + StackRand + MmapRand\n\n  where:\n\n  . StackRand = stack_maxrandom_size() - \"stack_rand\", a random variable\n    in the [0B,16GB] range\n\n  . MmapRand = arch_mmap_rnd(), a random variable in the [0B,1TB] range\n\nConsequently, the minimum initial mmap-stack distance is only 128MB\n(CVE-2017-1000379), and:\n\n- On kernels vulnerable to offset2lib, the heap of a PIE (which is\n  mapped at the end of the mmap region) is mapped below and close to the\n  stack with a good probability (~1/700). We can therefore clash the\n  stack with the heap in Step 1, jump over the stack guard-page and into\n  the heap in Step 3, and smash the stack with the heap and gain control\n  of rip in Step 4a (after 6 hours on average). However, because the\n  addresses of all executable regions contain null-bytes, and because\n  most of our stack-smashes in Step 4a are string operations (except the\n  getaddrinfo() method), we were unable to transform such a rip control\n  into arbitrary code execution. \n\n- On all kernels, either a PIE or ld.so is mapped directly below the\n  stack with a good probability (~1/17000) -- the end of the PIE\u0027s or\n  ld.so\u0027s read-write segment is then equal to the start of the stack\n  guard-page. We can therefore adapt our ld.so \"hwcap\" exploit to amd64\n  and obtain root privileges through most SUID binaries on most Linux\n  distributions (after 5 hours on average). \n\nKernels vulnerable to offset2lib, local Exim proof-of-concept\n\nExim\u0027s binary is usually a PIE, mapped at the end of the mmap region;\nand the heap, which always grows up and is randomized above the end of\nthe binary, is therefore randomized above the end of the mmap region\n(arch_randomize_brk() in arch/x86/kernel/process.c):\n\n  heap_start = mmap_end + \"heap_rand\"\n\nwhere \"heap_rand\" is a random variable in the [0B,32MB] range\n(negligible and ignored here). For example, on Debian 8.5:\n\n# cat /proc/\"`pidof -s /usr/sbin/exim4`\"/maps\n... \n7fa6410d6000-7fa6411c8000 r-xp 00000000 08:01 14574                      /usr/sbin/exim4\n7fa6413b4000-7fa6413bd000 rw-p 00000000 00:00 0\n7fa6413c5000-7fa6413c7000 rw-p 00000000 00:00 0\n7fa6413c7000-7fa6413c9000 r--p 000f1000 08:01 14574                      /usr/sbin/exim4\n7fa6413c9000-7fa6413d2000 rw-p 000f3000 08:01 14574                      /usr/sbin/exim4\n7fa6413d2000-7fa6413d7000 rw-p 00000000 00:00 0\n7fa641b34000-7fa641b76000 rw-p 00000000 00:00 0                          [heap]\n7ffdf3e53000-7ffdf3ed6000 rw-p 00000000 00:00 0                          [stack]\n7ffdf3f3c000-7ffdf3f3e000 r-xp 00000000 00:00 0                          [vdso]\n7ffdf3f3e000-7ffdf3f40000 r--p 00000000 00:00 0                          [vvar]\nffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]\n\nTo reach the start of the stack with the end of the heap (through the -p\nmemory leak in Exim) in Step 1 of our stack-clash, we must minimize the\ninitial heap-stack distance, and hence the initial mmap-stack distance,\nand set RLIMIT_STACK to MIN_GAP (~16GB). This limits the size of our -p\nargument strings on the stack to 16GB/4=4GB, and because we then leak\nthe same amount of heap memory through -p, the initial heap-stack\ndistance must be:\n\n- longer than 4GB (the stack must be able to contain the -p argument\n  strings);\n\n- shorter than 8GB (the end of the heap must be able to reach the start\n  of the stack during the -p memory leak). \n\nThe initial heap-stack distance (approximately the initial mmap-stack\ndistance, 128MB + StackRand + MmapRand, but we ignore the 128MB term\nhere) follows a trapezoidal Irwin-Hall distribution, and the [4GB,8GB]\nrange is within the first non-uniform area of this trapezoid, so the\nprobability that the initial heap-stack distance is in this range is:\n\n  SUM(d = 4GB; d \u003c 8GB; d++) d / (16GB * 1TB)\n\n  = SUM(d = 0; d \u003c 4GB; d++) (4GB + d) / (16GB * 1TB)\n\n  = SUM(d = 0; d \u003c 2^32; d++) (2^32 + d) / (2^34 * 2^40)\n\n  ~= ((2^32)*(2^32) + (2^32)*(2^32) / 2) / (2^74)\n\n  ~= 3 / 2^11\n\n  ~= 1 / 682\n\nThe probability of gaining rip control after the heap reaches the stack\nis ~1/16 (as calculated by a 64-bit version of the small helper program\npresented in IV.1.1.), and the final probability of gaining rip control\nwith our local Exim proof-of-concept is:\n\n  (3 / 2^11) * (1/16) ~= 1 / 10922\n\nOn our 8GB Debian 8.7 test machine, this proof-of-concept takes roughly\n2 seconds per run, and has a good chance of gaining rip control after\n10922 * 2 seconds ~= 6 hours:\n\n# gdb /usr/sbin/exim4 core.6049\nGNU gdb (Debian 7.7.1+dfsg-5) 7.7.1\n... \nThis GDB was configured as \"x86_64-linux-gnu\". \nCore was generated by `/usr/sbin/exim4 -p0000000000000000000000000000000000000000000000000000000000000\u0027. \nProgram terminated with signal SIGSEGV, Segmentation fault. \n#0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:41\n41      ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory. \n(gdb) x/i $rip\n=\u003e 0x7ffab1be7061 \u003c__memcpy_sse2_unaligned+65\u003e: retq\n(gdb) x/xg $rsp\n0x7ffb9b294a48: 0x4141414141414141\n\nKernels vulnerable to offset2lib, ld.so \".dynamic\" exploit\n\nSince kernels vulnerable to offset2lib map PIEs below and close to the\nstack, we tried to adapt our ld.so \".dynamic\" exploit to amd64. MIN_GAP\nguarantees a minimum distance of 128MB between the theoretical end of\nthe mmap region and the end of the stack, but the stack then grows down\nto store the argument and environment strings, and may therefore occupy\nthe theoretical end of the mmap region (where nothing has been mapped\nyet). Consequently, the end of the mmap region (where the PIE will be\nmapped) slides down to the first available address, directly below the\nstack guard-page and the initial stack expansion (described in II.3.2.):\n\n7ffbb7e51000-7ffbb7e53000 r-xp 00000000 fd:03 4465810                    /tmp/test64\n... \n7ffbb8053000-7ffbb808c000 rw-p 00002000 fd:03 4465810                    /tmp/test64\n7ffbb808d000-7ffc180ae000 rw-p 00000000 00:00 0                          [heap]\nffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]\n\nNote: in this example, the \"[stack]\" is, again, incorrectly displayed as\nthe \"[heap]\" by show_map_vma() (in fs/proc/task_mmu.c). \n\nThis layout is ideal for our stack-clash exploits, but poses an\nunexpected problem: because the PIE is mapped directly below the stack,\nthe stack cannot grow anymore, and the only free stack space is the\ninitial stack expansion (128KB) minus the argv[] and envp[] pointers\n(which are stored there, as mentioned in II.3.2.):\n\n- on the one hand, many argv[] and envp[] pointers, and hence many\n  argument and environment strings, result in a higher probability of\n  mapping the PIE directly below the stack;\n\n- on the other hand, many argv[] and envp[] pointers consume most of the\n  initial stack expansion and do not leave enough free stack space for\n  ld.so to operate. \n\nIn practice, we pass 96KB of argv[] pointers to execve(), thus leaving\n32KB of free stack space for ld.so, and since the size of a pointer is\n8B, and the maximum size of an argument string is 128KB, we also pass\n96KB/8B*128KB=1.5GB of argument strings to execve(). The resulting\nprobability of mapping the PIE directly below the stack is:\n\n  SUM(s = 0; s \u003c 1.5GB - 128MB; s++) s / (16GB * 1TB)\n\n            ~= ((1.5GB - 128MB)^2 / 2) / (16GB * 1TB)\n\n            ~= 1 / 17331\n\nOn a 4GB Virtual Machine, each run takes 1 second, and 17331 runs take\nroughly 5 hours. But we cannot add more uncertainty to this exploit, and\nbecause of the problems discussed in IV.1.4. (null-bytes in DT_NEEDED,\nbut also in DT_AUXILIARY on 64-bit, etc), we were unable to overwrite\nthe .dynamic section with a pattern that does not significantly decrease\nthis exploit\u0027s probability of success. \n\nAll kernels, ld.so \"hwcap\" exploit\n\nDespite this failure, we had an intuition: when the PIE is mapped\ndirectly below the stack, the stack layout should be deterministic --\nrsp should point into the 128KB of initial stack expansion, at a 32KB\noffset above the start of the stack, and the only entropy should be the\n8KB of sub-page randomization within the stack (arch_align_stack() in\narch/x86/kernel/process.c). The following output of our small test\nprogram confirmed this intuition (the fourth field is the distance\nbetween the start of the stack and our main()\u0027s rsp when the PIE is\nmapped directly below the stack):\n\n$ grep -w sp test64.out | sort -nk4\nsp 0x7ffbc271ff38 -\u003e 28472\nsp 0x7ffbb95ccff8 -\u003e 28664\nsp 0x7ffbaf062678 -\u003e 30328\nsp 0x7ffbb08736e8 -\u003e 30440\nsp 0x7ffbbc616d18 -\u003e 32024\nsp 0x7ffbc1a0fdb8 -\u003e 32184\nsp 0x7ffbb9c28ff8 -\u003e 32760\nsp 0x7ffbdbf4c178 -\u003e 33144\nsp 0x7ffbb39bc1c8 -\u003e 33224\nsp 0x7ffbebb86838 -\u003e 34872\n\nSurprisingly, the output of this test program contained additional\nvaluable information:\n\n7ffbb7e51000-7ffbb7e53000 r-xp 00000000 fd:03 4465810                    /tmp/test64\n7ffbb8034000-7ffbb8037000 rw-p 00000000 00:00 0\n7ffbb804d000-7ffbb804e000 rw-p 00000000 00:00 0\n7ffbb804e000-7ffbb8050000 r--p 00000000 00:00 0                          [vvar]\n7ffbb8050000-7ffbb8052000 r-xp 00000000 00:00 0                          [vdso]\n7ffbb8052000-7ffbb8053000 r--p 00001000 fd:03 4465810                    /tmp/test64\n7ffbb8053000-7ffbb808c000 rw-p 00002000 fd:03 4465810                    /tmp/test64\n7ffbb808d000-7ffc180ae000 rw-p 00000000 00:00 0                          [heap]\nffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]\n\n- the distance between the end of the read-execute segment of our test\n  program and the start of its read-only and read-write segments is\n  approximately 2MB; indeed, for every ELF on amd64:\n\n$ readelf -a /usr/bin/su | grep -wA1 LOAD\n  LOAD           0x0000000000000000 0x0000000000000000 0x0000000000000000\n                 0x00000000000061b4 0x00000000000061b4  R E    200000\n  LOAD           0x0000000000006888 0x0000000000206888 0x0000000000206888\n                 0x0000000000000798 0x00000000000007d0  RW     200000\n\n$ readelf -a /lib64/ld-linux-x86-64.so.2 | grep -wA1 LOAD\n  LOAD           0x0000000000000000 0x0000000000000000 0x0000000000000000\n                 0x000000000001fad0 0x000000000001fad0  R E    200000\n  LOAD           0x000000000001fb60 0x000000000021fb60 0x000000000021fb60\n                 0x000000000000141c 0x00000000000015e8  RW     200000\n\n- several objects are actually mapped inside this ~2MB hole: [vdso],\n  [vvar], and two anonymous mappings (7ffbb804d000-7ffbb804e000 and\n  7ffbb8034000-7ffbb8037000). \n\nThis discovery allowed us to adapt our ld.so \"hwcap\" exploit to amd64:\n\n- we choose hardware-capabilities that are small enough to be mapped\n  inside this ~2MB hole, but large enough to defeat the 8KB sub-page\n  randomization of the stack;\n\n- we jump over the stack guard-page, and over the read-only and\n  read-write segments of the PIE, and exploit ld.so as we did on i386. \n\nThis exploit\u0027s probability of success is therefore 1 when the PIE is\nmapped directly below the stack, and its final probability of success is\n~1/17331: it takes 1 second per run, and has a good chance of obtaining\na root-shell after 5 hours. Moreover, it works on all kernels: if a SUID\nbinary is not a PIE, or if the kernel is not vulnerable to offset2lib,\nwe simply jump over ld.so\u0027s read-write segment, instead of the PIE\u0027s. \nFor example, on Fedora 25, when the exploit succeeds and loads our own\nlibrary /var/tmp/a (the 7ffbabbef000-7ffbabca7000 mapping contains the\nhardware-capabilities that we smash):\n\n55a0c9e8d000-55a0c9e91000 r-xp 00000000 fd:00 112767                     /usr/libexec/cockpit-polkit\n55a0ca091000-55a0ca093000 rw-p 00004000 fd:00 112767                     /usr/libexec/cockpit-polkit\n7ffbab603000-7ffbab604000 r-xp 00000000 fd:00 4866583                    /var/tmp/a\n7ffbab604000-7ffbab803000 ---p 00001000 fd:00 4866583                    /var/tmp/a\n7ffbab803000-7ffbab804000 r--p 00000000 fd:00 4866583                    /var/tmp/a\n7ffbab804000-7ffbaba86000 rw-p 00000000 00:00 0\n7ffbaba86000-7ffbabaab000 r-xp 00000000 fd:00 4229637                    /usr/lib64/ld-2.24.so\n7ffbabbef000-7ffbabca7000 rw-p 00000000 00:00 0\n7ffbabca7000-7ffbabca9000 r--p 00000000 00:00 0                          [vvar]\n7ffbabca9000-7ffbabcab000 r-xp 00000000 00:00 0                          [vdso]\n7ffbabcab000-7ffbabcad000 rw-p 00025000 fd:00 4229637                    /usr/lib64/ld-2.24.so\n7ffbabcad000-7ffbabcae000 rw-p 00000000 00:00 0\n7ffbabcaf000-7ffc0bcf0000 rw-p 00000000 00:00 0                          [stack]\nffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]\n\n========================================================================\nIV.2. OpenBSD\n========================================================================\n\n========================================================================\nIV.2.1. Maximum RLIMIT_STACK vulnerability (CVE-2017-1000372)\n========================================================================\n\nThe OpenBSD kernel limits the maximum size of the user-space stack\n(RLIMIT_STACK) to MAXSSIZ (32MB); the execve() system-call allocates a\nMAXSSIZ memory region for the stack and divides it in two:\n\n- the second part, effectively the user-space stack, is mapped\n  PROT_READ|PROT_WRITE at the end of this stack memory region, and\n  occupies RLIMIT_STACK bytes (by default 8MB for root processes, and\n  4MB for user processes);\n\n- the first part, effectively a large stack guard-page, is mapped\n  PROT_NONE at the start of this stack memory region, and occupies\n  MAXSSIZ - RLIMIT_STACK bytes. \n\nUnfortunately, we discovered that if an attacker sets RLIMIT_STACK to\nMAXSSIZ, he eliminates the PROT_NONE part of the stack region, and hence\nthe stack guard-page itself (CVE-2017-1000372). For example:\n\n# sh -c \u0027ulimit -S -s; procmap -a -P\u0027\n8192\nStart    End         Size  Offset   rwxpc  RWX  I/W/A Dev     Inode - File\n... \n14cf6000-14cfafff      20k 00000000 r-xp+ (rwx) 1/0/0 00:03   52375 - /usr/sbin/procmap [0xdb29ce10]\n... \n84a7b000-84a7bfff       4k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ anon ]\ncd7db000-cefdafff   24576k 00000000 ---p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\ncefdb000-cf7cffff    8148k 00000000 rw-p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\ncf7d0000-cf7dafff      44k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ stack ]\n total              10348k\n\n# sh -c \u0027ulimit -S -s `ulimit -H -s`; procmap -a -P\u0027\nStart    End         Size  Offset   rwxpc  RWX  I/W/A Dev     Inode - File\n... \n1a47f000-1a483fff      20k 00000000 r-xp+ (rwx) 1/0/0 00:03   52375 - /usr/sbin/procmap [0xdb29ce10]\n... \n8a3c8000-8a3c9fff       8k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ anon ]\ncd7c9000-cf7bffff   32732k 00000000 rw-p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\ncf7c0000-cf7c8fff      36k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ stack ]\n total              33992k\n\nA remote attacker cannot exploit this vulnerability, because he cannot\nmodify RLIMIT_STACK; but a local attacker can set RLIMIT_STACK to\nMAXSSIZ, and:\n\n- Step 1: malloc()ate almost 2GB of heap memory, until the heap reaches\n  the start of the stack region;\n\n- Steps 2 and 3: consume MAXSSIZ (32MB) of stack memory, until the\n  stack-pointer reaches the start of the stack region (Step 2) and moves\n  into the heap (Step 3);\n\n- Step 4: smash the stack with the heap (Step 4a) or smash the heap with\n  the stack (Step 4b). \n\n========================================================================\nIV.2.2. Recursive qsort() vulnerability (CVE-2017-1000373)\n========================================================================\n\nTo complete Step 2, a recursive function is needed, and the first\npossibly recursive function that we investigated is qsort(). On the one\nhand, glibc\u0027s _quicksort() function (in stdlib/qsort.c) is non-recursive\n(iterative): it uses a small, specialized stack of partition structures\n(two pointers, low and high), and guarantees that no more than 32\npartitions (on i386) or 64 partitions (on amd64) are pushed onto this\nstack, because it always pushes the larger of two sub-partitions and\niterates on the smaller partition. \n\nOn the other hand, BSD\u0027s qsort() function is recursive: it always\nrecurses on the first sub-partition, and iterates on the second\nsub-partition; but instead, it should always recurse on the smaller\nsub-partition, and iterate on the larger sub-partition (CVE-2017-1000373\nin OpenBSD, CVE-2017-1000378 in NetBSD, and CVE-2017-1082 in FreeBSD). \n\nIn theory, because BSD\u0027s qsort() is not randomized, an attacker can\nconstruct a pathological input array of N elements that causes qsort()\nto deterministically recurse N times. In practice, because this qsort()\nuses the median-of-three medians-of-three selection of a pivot element\n(the \"ninther\"), our attack constructs an input array of N elements that\ncauses qsort() to recurse N/4 times. \n\n========================================================================\nIV.2.3. /usr/bin/at proof-of-concept\n========================================================================\n\n/usr/bin/at is SGID-crontab (which can be escalated to full root\nprivileges) because it must be able to create (\"at -t\"), list (\"at -l\"),\nand remove (\"at -r\") job-files in the /var/cron/atjobs directory:\n\n-r-xr-sr-x  4 root  crontab  31376 Jul 26  2016 /usr/bin/at\ndrwxrwx--T  2 root  crontab    512 Jul 26  2016 /var/cron/atjobs\n\nTo demonstrate that OpenBSD\u0027s RLIMIT_STACK and qsort() vulnerabilities\ncan be transformed into powerful primitives such as heap corruption, we\ndeveloped a proof-of-concept against \"at -l\" (the list_jobs() function):\n\n- Step 1 (Clash): first, list_jobs() malloc()ates an atjob structure for\n  each file in /var/cron/atjobs -- if we create 40M job-files, then the\n  heap reaches the stack, but we do not exhaust the address-space;\n\n- Steps 2 and 3 (Run and Jump): second, list_jobs() qsort()s the\n  malloc()ated jobs -- if we construct their time-stamps with our\n  qsort() attack, then we can cause qsort() to recurse 40M/4=10M times\n  and consume at least 10M*4B=40MB of stack memory (each recursive call\n  to qsort() consumes at least 4B, the return-address) and move the\n  stack-pointer into the heap;\n\n- Step 4b (Smash the heap with the stack): last, list_jobs() free()s the\n  malloc()ated jobs, and abort()s with an error message -- OpenBSD\u0027s\n  hardened malloc() implementation detects that the heap has been\n  corrupted by the last recursive calls to qsort(). \n\nThis naive version of our /usr/bin/at proof-of-concept poses two major\nproblems:\n\n- Our pathological input array of N=40M elements cannot be sorted (Step\n  2 never finishes because it exhibits qsort()\u0027s worst-case behavior,\n  N^2). To solve this problem, we divide the input array in two:\n\n  . the first, pathological part contains only n=(33MB/176B)*4=768K\n    elements that are needed to complete Steps 2 and 3, and cause\n    qsort() to recurse n/4 times and consume (n/4)*176B=33MB of stack\n    memory (MAXSSIZ+1MB) as each recursive call to qsort() consumes 176B\n    of stack memory;\n\n  . the second, innocuous part contains the remaining N-n=39M elements\n    that are needed to complete Step 1, but not Steps 2 and 3, and are\n    therefore swapped into the second, iterative partition of the first\n    recursive call to qsort(). \n\n- We were unable to create 40M files in /var/cron/atjobs: after one\n  week, OpenBSD\u0027s default filesystem (ffs) had created only 4M files,\n  and the rate of file creation had dropped from 25 files/second to 4\n  files/second. We did not solve this problem, but nevertheless wanted\n  to validate our proof-of-concept:\n\n  . we transformed it into an LD_PRELOAD library that intercepts calls\n    to readdir() and fstatat(), and pretends that our 40M files in\n    /var/cron/atjobs exist;\n\n  . we made /var/cron/atjobs world-readable and LD_PRELOADed our library\n    into a non-SGID copy of /usr/bin/at;\n\n  . after about an hour, \"at\" reports random heap corruptions:\n\n# chmod o+r /var/cron/atjobs\n# chmod o+r /var/cron/at.deny\n\n$ ulimit -c 0\n$ ulimit -S -d `ulimit -H -d`\n$ ulimit -S -s `ulimit -H -s`\n$ ulimit -S -a\n... \ncoredump(blocks)     0\ndata(kbytes)         3145728\nstack(kbytes)        32768\n... \n$ cp /usr/bin/at . \n\n$ LD_PRELOAD=./OpenBSD_at.so ./at -l -v -q x \u003e /dev/null\ninitializing jobkeys\nfinalizing jobkeys\nreading jobs\n10%\n20%\n30%\n40%\n50%\n60%\n70%\n80%\n90%\n100%\nsorting jobs\nat(78717) in free(): error: chunk info corrupted\nAbort trap\n\n$ LD_PRELOAD=./OpenBSD_at.so ./at -l -v -q x \u003e /dev/null\ninitializing jobkeys\nfinalizing jobkeys\nreading jobs\n10%\n20%\n30%\n40%\n50%\n60%\n70%\n80%\n90%\n100%\nsorting jobs\nat(14184) in free(): error: modified chunk-pointer 0xcd6d0120\nAbort trap\n\n========================================================================\nIV.3. NetBSD\n========================================================================\n\nLike OpenBSD, NetBSD is vulnerable to the maximum RLIMIT_STACK\nvulnerability (CVE-2017-1000374): if a local attacker sets RLIMIT_STACK\nto MAXSSIZ, he eliminates the PROT_NONE part of the stack region -- the\nstack guard-page itself. Unlike OpenBSD, however, NetBSD:\n\n- defines MAXSSIZ to 64MB on i386 (128MB on amd64);\n\n- maps the run-time link-editor ld.so directly below the stack region,\n  even if ASLR is enabled (CVE-2017-1000375):\n\n$ sh -c \u0027ulimit -S -s; pmap -a -P\u0027\n2048\nStart    End         Size  Offset   rwxpc  RWX  I/W/A Dev     Inode - File\n08048000-0804dfff      24k 00000000 r-xp+ (rwx) 1/0/0 00:00   21706 - /usr/bin/pmap [0xc5c8f0b8]\n... \nbbbee000-bbbfefff      68k 00000000 r-xp+ (rwx) 1/0/0 00:00  107525 - /libexec/ld.elf_so [0xc535f580]\nbbbff000-bbbfffff       4k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ anon ]\nbbc00000-bf9fffff   63488k 00000000 ---p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\nbfa00000-bfbeffff    1984k 00000000 rw-p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\nbfbf0000-bfbfffff      64k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ stack ]\n total               9528k\n\n$ sh -c \u0027ulimit -S -s `ulimit -H -s`; pmap -a -P\u0027\nStart    End         Size  Offset   rwxpc  RWX  I/W/A Dev     Inode - File\n08048000-0804dfff      24k 00000000 r-xp+ (rwx) 1/0/0 00:00   21706 - /usr/bin/pmap [0xc5c8f0b8]\n... \nbbbee000-bbbfefff      68k 00000000 r-xp+ (rwx) 1/0/0 00:00  107525 - /libexec/ld.elf_so [0xc535f580]\nbbbff000-bbbfffff       4k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ anon ]\nbbc00000-bfbeffff   65472k 00000000 rw-p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\nbfbf0000-bfbfffff      64k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ stack ]\n total              73016k\n\n# cp /usr/bin/pmap . \n# paxctl +A ./pmap\n# sh -c \u0027ulimit -S -s `ulimit -H -s`; ./pmap -a -P\u0027\nStart    End         Size  Offset   rwxpc  RWX  I/W/A Dev     Inode - File\n08048000-0804dfff      24k 00000000 r-xp+ (rwx) 1/0/0 00:00  172149 - /tmp/pmap [0xc5cb3c64]\n... \nbbbee000-bbbfefff      68k 00000000 r-xp+ (rwx) 1/0/0 00:00  107525 - /libexec/ld.elf_so [0xc535f580]\nbbbff000-bbbfffff       4k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ anon ]\nbbc00000-bf1bffff   55040k 00000000 rw-p+ (rwx) 1/0/0 00:00       0 -   [ stack ]\nbf1c0000-bf1cefff      60k 00000000 rw-p- (rwx) 1/0/0 00:00       0 -   [ stack ]\n total              62580k\n\nConsequently, a local attacker can set RLIMIT_STACK to MAXSSIZ,\neliminate the stack guard-page, and:\n\n- skip Step 1, because ld.so\u0027s read-write segment is naturally mapped\n  directly below the stack region;\n\n- Steps 2 and 3: consume 64MB (MAXSSIZ) of stack memory (for example,\n  through the recursive qsort() vulnerability, CVE-2017-1000378) until\n  the stack-pointer reaches the start of the stack region (Step 2) and\n  moves into ld.so\u0027s read-write segment (Step 3);\n\n- Step 4b: smash ld.so\u0027s read-write segment with the stack. \n\nWe did not try to exploit this vulnerability, nor did we search for a\nvulnerable SUID or SGID binary, but we wrote a simple proof-of-concept,\nand some of the following crashes may be exploitable:\n\n$ sh -c \u0027ulimit -S -s `ulimit -H -s`; ./NetBSD_CVE-2017-1000375 0x04000000\u0027\n[1]   Segmentation fault      ./NetBSD_CVE-201... \n\n$ sh -c \u0027ulimit -S -s `ulimit -H -s`; ./NetBSD_CVE-2017-1000375 0x03000000\u0027\n\n... \n\n$ sh -c \u0027ulimit -S -s `ulimit -H -s`; ./NetBSD_CVE-2017-1000375 0x03ec5000\u0027\n\n$ sh -c \u0027ulimit -S -s `ulimit -H -s`; ./NetBSD_CVE-2017-1000375 0x03ec5400\u0027\n[1]   Segmentation fault      ./NetBSD_CVE-201... \n\n$ sh -c \u0027ulimit -S -s `ulimit -H -s`; gdb ./NetBSD_CVE-2017-1000375\u0027\nGNU gdb (GDB) 7.7.1\n... \n(gdb) run 0x03ec5400\nProgram received signal SIGSEGV, Segmentation fault. \n0xbbbf448d in _rtld_symlook_default () from /usr/libexec/ld.elf_so\n(gdb) x/i $eip\n=\u003e 0xbbbf448d \u003c_rtld_symlook_default+185\u003e:      mov    %edx,(%esi,%edi,4)\n(gdb) info registers\nesi            0xbabae890       -1162155888\nedi            0x0      0\n... \n(gdb) run 0x03ec5800\nProgram received signal SIGSEGV, Segmentation fault. \n0xbbbf4465 in _rtld_symlook_default () from /usr/libexec/ld.elf_so\n(gdb) x/i $eip\n=\u003e 0xbbbf4465 \u003c_rtld_symlook_default+145\u003e:      mov    0x4(%ecx),%edx\n(gdb) info registers\necx            0x41414141       1094795585\n... \n(gdb) run 0x03ec5c00\nProgram received signal SIGSEGV, Segmentation fault. \n0xbbbf4408 in _rtld_symlook_default () from /usr/libexec/ld.elf_so\n(gdb) x/i $eip\n=\u003e 0xbbbf4408 \u003c_rtld_symlook_default+52\u003e:       mov    (%eax),%esi\n(gdb) info registers\neax            0x41414141       1094795585\n... \n\n========================================================================\nIV.4. FreeBSD\n========================================================================\n\n========================================================================\nIV.4.1. setrlimit() RLIMIT_STACK vulnerability (CVE-2017-1085)\n========================================================================\n\nFreeBSD\u0027s kern_proc_setrlimit() function contains the following comment\nand code:\n\n                /*\n                 * Stack is allocated to the max at exec time with only\n                 * \"rlim_cur\" bytes accessible.  If stack limit is going\n                 * up make more accessible, if going down make inaccessible. \n                 */\n                if (limp-\u003erlim_cur != oldssiz.rlim_cur) {\n                        ... \n                        if (limp-\u003erlim_cur \u003e oldssiz.rlim_cur) {\n                                prot = p-\u003ep_sysent-\u003esv_stackprot;\n                                size = limp-\u003erlim_cur - oldssiz.rlim_cur;\n                                addr = p-\u003ep_sysent-\u003esv_usrstack -\n                                    limp-\u003erlim_cur;\n                        } else {\n                                prot = VM_PROT_NONE;\n                                size = oldssiz.rlim_cur - limp-\u003erlim_cur;\n                                addr = p-\u003ep_sysent-\u003esv_usrstack -\n                                    oldssiz.rlim_cur;\n                        }\n                        ... \n                        (void)vm_map_protect(\u0026p-\u003ep_vmspace-\u003evm_map,\n                            addr, addr + size, prot, FALSE);\n                }\n\nOpenBSD\u0027s and NetBSD\u0027s dosetrlimit() function contains the same comment,\nwhich accurately describes the layout of their user-space stack region. \nUnfortunately, FreeBSD\u0027s kern_proc_setrlimit() comment and code are\nincorrect, as hinted at in exec_new_vmspace():\n\n/*\n * Destroy old address space, and allocate a new stack\n *      The new stack is only SGROWSIZ large because it is grown\n *      automatically in trap.c. \n */\n\nand vm_map_stack_locked():\n\n        /*\n         * We initially map a stack of only init_ssize.  We will grow as\n         * needed later. \n\nwhere init_ssize is SGROWSIZ (128KB), not MAXSSIZ (64MB on i386),\nbecause \"init_ssize = (max_ssize \u003c growsize) ? max_ssize : growsize;\"\n(and max_ssize is MAXSSIZ, and growsize is SGROWSIZ). \n\nAs a result, if a program calls setrlimit() to increase RLIMIT_STACK,\nvm_map_protect() may turn a read-only memory region below the stack into\na read-write region (CVE-2017-1085), as demonstrated by the following\nproof-of-concept:\n\n% ./FreeBSD_CVE-2017-1085\nSegmentation fault\n\n% ./FreeBSD_CVE-2017-1085 setrlimit to the max\nchar at 0xbd155000: 41\n\n========================================================================\nIV.4.2. Stack guard-page disabled by default (CVE-2017-1083)\n========================================================================\n\nThe FreeBSD kernel implements a 4KB stack guard-page, and recent\nversions of the FreeBSD Installer offer it as a system hardening option. \nUnfortunately, it is disabled by default (CVE-2017-1083):\n\n% sysctl security.bsd.stack_guard_page\nsecurity.bsd.stack_guard_page: 0\n\n========================================================================\nIV.4.3. Stack guard-page vulnerabilities (CVE-2017-1084)\n========================================================================\n\n- If FreeBSD\u0027s stack guard-page is enabled, its entire logic is\n  implemented in vm_map_growstack(): this function guarantees a minimum\n  distance of 4KB (the stack guard-page) between the start of the stack\n  and the end of the memory region that is mapped below (but the stack\n  guard-page is not physically mapped into the address-space). \n\n  Unfortunately, this guarantee is given only when the stack grows down\n  and clashes with the memory region mapped below, but not if the memory\n  region mapped below grows up and clashes with the stack: this\n  vulnerability effectively eliminates the stack guard-page\n  (CVE-2017-1084). In our proof-of-concept:\n\n  . we allocate anonymous mmap()s of 4KB, until the end of an anonymous\n    mmap() reaches the start of the stack [Step 1];\n\n  . we call a recursive function until the stack-pointer reaches the\n    start of the stack and moves into the anonymous mmap() directly\n    below [Step 2];\n\n  . but we do not jump over the stack guard-page, because each call to\n    the recursive function allocates (and fully writes to) a 1KB\n    stack-based buffer [Step 3];\n\n  . and we do not crash into the stack guard-page, because CVE-2017-1084\n    has effectively eliminated the stack guard-page in Step 1. \n\n# sysctl security.bsd.stack_guard_page=1\nsecurity.bsd.stack_guard_page: 0 -\u003e 1\n\n% ./FreeBSD_CVE-2017-FGPU\nchar at 0xbfbde000: 41\n\n- vm_map_growstack() implements most of the stack guard-page logic in\n  the following code:\n\n                /*\n                 * Growing downward. \n                 */\n                /* Get the preliminary new entry start value */\n                addr = stack_entry-\u003estart - grow_amount;\n\n                /*\n                 * If this puts us into the previous entry, cut back our\n                 * growth to the available space. Also, see the note above. \n                 */\n                if (addr \u003c end) {\n                        stack_entry-\u003eavail_ssize = max_grow;\n                        addr = end;\n                        if (stack_guard_page)\n                                addr += PAGE_SIZE;\n                }\n\n  where:\n\n  . addr is the new start of the stack;\n\n  . stack_entry-\u003estart is the old start of the stack;\n\n  . grow_amount is the size of the stack expansion;\n\n  . end is the end of the memory region below the stack. \n\n  Unfortunately, the \"addr \u003c end\" test should be \"addr \u003c= end\": if addr,\n  the new start of the stack, is equal to end, the end of the memory\n  region mapped below, then the stack guard-page is eliminated\n  (CVE-2017-1084). In our proof-of-concept:\n\n  . we allocate anonymous mmap()s of 4KB, until the end of an anonymous\n    mmap() reaches a randomly chosen distance below the start of the\n    stack [Step 1];\n\n  . we call a recursive function until the stack-pointer reaches the\n    start of the stack, and the stack expansion reaches the end of the\n    anonymous mmap() below [Step 2];\n\n  . we do not jump over the stack guard-page, because each call to the\n    recursive function allocates (and fully writes to) a 1KB stack-based\n    buffer [Step 3];\n\n  . and we crash into the stack guard-page most of the time;\n\n  . but we survive with a probability of 4KB/128KB=1/32 (grow_amount is\n    always a multiple of SGROWSIZ, 128KB) because CVE-2017-1084 has\n    effectively eliminated the stack guard-page in Step 2. \n\n% sysctl security.bsd.stack_guard_page\nsecurity.bsd.stack_guard_page: 1\n\n% sh -c \u0027while true; do ./FreeBSD_CVE-2017-FGPE; done\u0027\nSegmentation fault\nchar at 0xbe45e000: 41; final dist 6097 (24778705)\nSegmentation fault\nSegmentation fault\nSegmentation fault\n... \nSegmentation fault\nSegmentation fault\nSegmentation fault\nchar at 0xbd25e000: 41; final dist 7036 (43654012)\nSegmentation fault\nSegmentation fault\nSegmentation fault\n... \nSegmentation fault\nSegmentation fault\nSegmentation fault\nchar at 0xbd29e000: 41; final dist 5331 (43390163)\nSegmentation fault\nSegmentation fault\nSegmentation fault\n... \n\n  In contrast, if FreeBSD\u0027s stack guard-page is disabled, our\n  proof-of-concept always survives:\n\n# sysctl security.bsd.stack_guard_page=0\nsecurity.bsd.stack_guard_page: 1 -\u003e 0\n\n% sh -c \u0027while true; do ./FreeBSD_CVE-2017-FGPE; done\u0027\nchar at 0xbe969000: 41; final dist 89894 (19488550)\nchar at 0xbfa6d000: 41; final dist 74525 (1647389)\nchar at 0xbf4df000: 41; final dist 78 (7471182)\nchar at 0xbe9e4000: 41; final dist 112397 (18986765)\nchar at 0xbf693000: 41; final dist 49811 (5685907)\nchar at 0xbf533000: 41; final dist 51037 (7128925)\nchar at 0xbd799000: 41; final dist 26043 (38167995)\nchar at 0xbd54b000: 11; final dist 83754 (40585002)\nchar at 0xbe176000: 41; final dist 36992 (27824256)\nchar at 0xbfa91000: 41; final dist 57449 (1499241)\nchar at 0xbd1b9000: 41; final dist 26115 (44328451)\nchar at 0xbd1c8000: 41; final dist 94852 (44266116)\nchar at 0xbf73a000: 41; final dist 22276 (5003012)\nchar at 0xbe6b1000: 41; final dist 58854 (22341094)\nchar at 0xbeb81000: 41; final dist 124727 (17295159)\nchar at 0xbfb35000: 41; final dist 43174 (829606)\n... \n\n- FreeBSD\u0027s thread library (libthr) mmap()s a secondary PROT_NONE stack\n  guard-page at a distance RLIMIT_STACK below the end of the stack:\n\n# sysctl security.bsd.stack_guard_page=1\nsecurity.bsd.stack_guard_page: 0 -\u003e 1\n\n% sh -c \u0027exec procstat -v $$\u0027\n  PID      START        END PRT  RES PRES REF SHD FLAG TP PATH\n 2779  0x8048000  0x8050000 r-x    8    8   1   0 CN-- vn /usr/bin/procstat\n... \n 2779 0x28400000 0x28800000 rw-   22   35   2   0 ---- df\n 2779 0xbfbdf000 0xbfbff000 rwx    3    3   1   0 ---D df\n 2779 0xbfbff000 0xbfc00000 r-x    1    1  23   0 ---- ph\n\n% sh -c \u0027LD_PRELOAD=libthr.so exec procstat -v $$\u0027\n  PID      START        END PRT  RES PRES REF SHD FLAG TP PATH\n 2798  0x8048000  0x8050000 r-x    8    8   1   0 CN-- vn /usr/bin/procstat\n... \n 2798 0x28400000 0x28800000 rw-   23   35   2   0 ---- df\n 2798 0xbbbfe000 0xbbbff000 ---    0    0   0   0 ---- --\n 2798 0xbfbdf000 0xbfbff000 rwx    3    3   1   0 ---D df\n 2798 0xbfbff000 0xbfc00000 r-x    1    1  23   0 ---- ph\n\n  Unfortunately, this secondary stack guard-page does not mitigate the\n  vulnerabilities that we discovered in FreeBSD\u0027s stack guard-page\n  implementation:\n\n% sysctl security.bsd.stack_guard_page\nsecurity.bsd.stack_guard_page: 1\n\n% sh -c \u0027LD_PRELOAD=libthr.so ./FreeBSD_CVE-2017-FGPU\u0027\nchar at 0xbfbde000: 41\n\n% sh -c \u0027while true; do LD_PRELOAD=libthr.so ./FreeBSD_CVE-2017-FGPE; done\u0027\nSegmentation fault\nSegmentation fault\nSegmentation fault\n... \nSegmentation fault\nSegmentation fault\nSegmentation fault\nchar at 0xbda5e000: 41; final dist 3839 (35262207)\nSegmentation fault\nSegmentation fault\nSegmentation fault\n... \nSegmentation fault\nSegmentation fault\nSegmentation fault\nchar at 0xbdb1e000: 41; final dist 3549 (34475485)\nSegmentation fault\nSegmentation fault\nSegmentation fault\n... \n\n========================================================================\nIV.4.4. Remote exploitation\n========================================================================\n\nBecause FreeBSD\u0027s stack guard-page is disabled by default, we tried (and\nfailed) to remotely exploit a test service vulnerable to:\n\n- an unlimited memory leak that allows us to malloc()ate gigabytes of\n  memory;\n\n- a limited recursion that allows us to allocate up to 1MB of stack\n  memory. \n\nFreeBSD\u0027s malloc() implementation (jemalloc) mmap()s 4MB chunks of\nanonymous memory that are aligned on multiples of 4MB. The first 4MB\nmmap() chunk starts at 0x28400000, and the last 4MB mmap() chunk ends at\n0xbf800000, because the stack itself already ends at 0xbfc00000; but it\nis impossible to cover this final mmap-stack distance (almost 4MB) with\nthe limited recursion (1MB) of our test service. \nbreak(0x80499b0)                 = 0 (0x0)\nbreak(0x8400000)                 = 0 (0x0)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 672845824 (0x281ad000)\nmmap(0x285ad000,2437120,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 677040128 (0x285ad000)\nmunmap(0x281ad000,2437120)           = 0 (0x0)\nmmap(0x0,8388608,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 679477248 (0x28800000)\nmunmap(0x28c00000,4194304)           = 0 (0x0)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 683671552 (0x28c00000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 687865856 (0x29000000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 692060160 (0x29400000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 696254464 (0x29800000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 700448768 (0x29c00000)\n... \nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = -1103101952 (0xbe400000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = -1098907648 (0xbe800000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = -1094713344 (0xbec00000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = -1090519040 (0xbf000000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = -1086324736 (0xbf400000)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) ERR#12 \u0027Cannot allocate memory\u0027\nbreak(0x8800000)                 = 0 (0x0)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) ERR#12 \u0027Cannot allocate memory\u0027\nbreak(0x8c00000)                 = 0 (0x0)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) ERR#12 \u0027Cannot allocate memory\u0027\nbreak(0x9000000)                 = 0 (0x0)\n... \nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) ERR#12 \u0027Cannot allocate memory\u0027\nbreak(0x27c00000)                = 0 (0x0)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) ERR#12 \u0027Cannot allocate memory\u0027\nbreak(0x28000000)                = 0 (0x0)\nmmap(0x0,4194304,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) ERR#12 \u0027Cannot allocate memory\u0027\nbreak(0x28400000)                ERR#12 \u0027Cannot allocate memory\u0027\n\n========================================================================\nIV.5. Solaris \u003e= 11.1\n========================================================================\n\n========================================================================\nIV.5.1. Minimal RLIMIT_STACK vulnerability (CVE-2017-3630)\n========================================================================\n\nOn Solaris, ASLR can be enabled or disabled for each ELF binary with the\nSUNW_ASLR dynamic section entry (man elfedit):\n\n$ elfdump /usr/bin/rsh | egrep \u0027ASLR|NX\u0027\n     [39]  SUNW_ASLR       0x2        ENABLE\n     [40]  SUNW_NXHEAP     0x2        ENABLE\n     [41]  SUNW_NXSTACK    0x2        ENABLE\n\nWithout ASLR\n\nIf ASLR is disabled:\n\n- a stack region of size RLIMIT_STACK is reserved in the address-space;\n\n- a 4KB stack guard-page is mapped directly below this stack region;\n\n- the runtime linker ld.so is mapped directly below this stack\n  guard-page. \n\n$ cp /usr/bin/sleep . \n$ chmod u+w ./sleep\n$ elfedit -e \u0027dyn:sunw_aslr disable\u0027 ./sleep\n\n$ sh -c \u0027ulimit -S -s; ./sleep 3 \u0026 pmap -r ${!}\u0027\n8192\n7176:   ./sleep 3\n... \nFE7B1000     228K r-x----  /lib/ld.so.1\nFE7FA000       8K rwx----  /lib/ld.so.1\nFE7FC000       8K rwx----  /lib/ld.so.1\nFE7FF000    8192K rw-----    [ stack ]\n total     17148K\n\n$ sh -c \u0027ulimit -S -s 64; ./sleep 3 \u0026 pmap -r ${!}\u0027\n7244:   ./sleep 3\n... \nFEFA1000     228K r-x----  /lib/ld.so.1\nFEFEA000       8K rwx----  /lib/ld.so.1\nFEFEC000       8K rwx----  /lib/ld.so.1\nFEFEF000      64K rw-----    [ stack ]\n total      9020K\n\nOn the one hand, a local attacker can exploit this simplified\nstack-clash:\n\n- Step 1 (Clash) is not needed, because ld.so is naturally mapped\n  directly below the stack (the distance between the end of ld.so\u0027s\n  read-write segment and the start of the stack is 4KB, the stack\n  guard-page);\n\n- Step 2 (Run) is not needed, because a local attacker can set\n  RLIMIT_STACK to just a few kilobytes, reserve a very small stack\n  region, and hence shorten the distance between the stack-pointer and\n  the start of the stack (and the end of ld.so\u0027s read-write segment);\n\n- Step 3 (Jump) can be completed with a large stack-based buffer that is\n  not fully written to;\n\n- Step 4b (Smash) can be completed by overwriting the function pointers\n  in ld.so\u0027s read-write segment with the contents of a stack-based\n  buffer. \n\nSuch a simplified stack-clash exploit was first mentioned in Gael\nDelalleau\u0027s 2005 presentation (slide 30). \n\nOn the other hand, a remote attacker cannot modify RLIMIT_STACK and must\ncomplete Step 2 (Run) with a recursive function that consumes the 8MB\n(the default RLIMIT_STACK) between the stack-pointer and the start of\nthe stack. \n\nWith ASLR\n\nIf ASLR is enabled:\n\n- a stack region of size RLIMIT_STACK is reserved in the address-space;\n\n- a 4KB stack guard-page is mapped directly below this stack region;\n\n- the runtime linker ld.so is mapped below this stack guard-page, but at\n  a random distance (within a [4KB,128MB] range) -- effectively a large,\n  secondary stack guard-page. \n\nOn the one hand, a local attacker can run the simplified \"Without ASLR\"\nstack-clash exploit until the ld.so-stack distance is minimal -- with a\nprobability of 4KB/128MB=1/32K, the distance between the end of ld.so\u0027s\nread-write segment and the start of the stack is exactly 8KB: the stack\nguard-page plus the minimum distance between the stack guard-page and\nld.so (CVE-2017-3629). \n\nOn the other hand, a remote attacker must complete Step 2 (Run) with a\nrecursive function, and:\n\n- has a good chance of exploiting this stack-clash after 32K connections\n  (when the ld.so-stack distance is minimal) if the remote service\n  re-execve()s (re-randomizes the ld.so-stack distance for each new\n  connection);\n\n- cannot exploit this stack-clash if the remote service does not\n  re-execve() (does not re-randomize the ld.so-stack distance for each\n  new connection) unless the attacker is able to restart the service,\n  reboot the server, or target a 32K-server farm. \n\n========================================================================\nIV.5.2. /usr/bin/rsh exploit\n========================================================================\n\n/usr/bin/rsh is SUID-root and its main() function allocates a 50KB\nstack-based buffer that is not written to and can be used to jump over\nthe stack guard-page, into ld.so\u0027s read-write segment, in Step 3 of our\nsimplified stack-clash exploit. \n\nNext, we discovered a general method for gaining eip control in Step 4b:\nsetlocale(LC_ALL, \"\"), called by the main() function of /usr/bin/rsh and\nother SUID binaries, copies the LC_ALL environment variable to several\nstack-based buffers and thus smashes ld.so\u0027s read-write segment and\noverwrites some of ld.so\u0027s function pointers. \n\nLast, we execute our own shell-code: we return-into-binary (/usr/bin/rsh\nis not a PIE), to an instruction that reliably jumps into a copy of our\nLC_ALL environment variable in ld.so\u0027s read-write segment, which is in\nfact read-write-executable. For example, after we gain control of eip:\n\n- on Solaris 11.1, we return to a \"pop; pop; ret\" instruction, because a\n  pointer to our shell-code is stored at an 8-byte offset from esp;\n\n- on Solaris 11.3, we return to a \"call *0xc(%ebp)\" instruction, because\n  a pointer to our shell-code is stored at a 12-byte offset from ebp. \n\nOur Solaris exploit brute-forces the random ld.so-stack distance and two\nparameters:\n\n- the RLIMIT_STACK;\n\n- the length of the LC_ALL environment variable. \n\n========================================================================\nIV.5.3. Forced-Privilege vulnerability (CVE-2017-3631)\n========================================================================\n\n/usr/bin/rsh is SUID-root, but the shell that we obtained in Step 4b of\nour stack-clash exploit did not grant us full root privileges, only\nnet_privaddr, the privilege to bind to a privileged port number. \nDisappointed by this result, we investigated and found:\n\n$ ggrep -r /usr/bin/rsh /etc 2\u003e/dev/null\n/etc/security/exec_attr.d/core-os:Forced Privilege:solaris:cmd:RO::/usr/bin/rsh:privs=net_privaddr\n\n$ /usr/bin/rsh -h\n/usr/bin/rsh: illegal option -- h\nusage: rsh [ -PN / -PO ] [ -l login ] [ -n ] [ -k realm ] [ -a ] [ -x ] [ -f / -F ] host command\n       rsh [ -PN / -PO ] [ -l login ] [ -k realm ] [ -a ] [ -x ] [ -f / -F ] host\n\n# cat truss.out\n... \n7319:   execve(\"/usr/bin/rsh\", 0xA9479C548, 0xA94792808)  argc = 2\n7319:       *** FPRIV: P/E: net_privaddr ***\n... \n\nUnfortunately, this Forced-Privilege protection is based on the pathname\nof SUID-root binaries, which can be execve()d through hard-links, under\ndifferent pathnames (CVE-2017-3631). For example, we discovered that\nreadable SUID-root binaries can be execve()d through hard-links in\n/proc:\n\n$ sleep 3 \u003c /usr/bin/rsh \u0026 /proc/${!}/fd/0 -h\n[1] 7333\n/proc/7333/fd/0: illegal option -- h\nusage: rsh [ -PN / -PO ] [ -l login ] [ -n ] [ -k realm ] [ -a ] [ -x ] [ -f / -F ] host command\n       rsh [ -PN / -PO ] [ -l login ] [ -k realm ] [ -a ] [ -x ] [ -f / -F ] host\n\n# cat truss.out\n... \n7335:   execve(\"/proc/7333/fd/0\", 0xA947CA508, 0xA94792808)  argc = 2\n7335:       *** SUID: ruid/euid/suid = 100 / 0 / 0  ***\n... \n\nThis vulnerability allows us to bypass the Forced-Privilege protection\nand obtain full root privileges with our /usr/bin/rsh exploit. \n\n\n========================================================================\nV. Acknowledgments\n========================================================================\n\nWe thank the members of the distros list, Oracle/Solaris, Exim, Sudo,\nsecurity@kernel.org, grsecurity/PaX, and OpenBSD. Description:\n\nRed Hat Container Development Kit is a platform for developing\ncontainerized applicationsaaait is a set of tools that enables developers\nto quickly and easily set up an environment for developing and testing\ncontainerized applications on the Red Hat Enterprise Linux platform. An attacker could use this flaw to crash a server\napplication compiled against the NSS library. Solution:\n\nThe References section of this erratum contains a link to download CDK\n3.0.0-2 (you must log in to download the update). \n==========================================================================\nUbuntu Security Notice USN-3323-2\nJune 29, 2017\n\neglibc vulnerability\n==========================================================================\n\nA security issue affects these releases of Ubuntu and its derivatives:\n\n- Ubuntu 12.04 ESM\n\nSummary:\n\nGnu C library could be made to run programs as an administrator. \n\nSoftware Description:\n- eglibc: GNU C Library\n\nDetails:\n\nUSN-3323-1 fixed a vulnerability in the GNU C Library. This update provides the\ncorresponding update for Ubuntu 12.04 ESM. \n\nUpdate instructions:\n\nThe problem can be corrected by updating your system to the following\npackage versions:\n\nUbuntu 12.04 ESM:\n  libc6                           2.15-0ubuntu10.20\n\nAfter a standard system update you need to reboot your computer to make\nall the necessary changes",
    "sources": [
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "BID",
        "id": "99127"
      },
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "PACKETSTORM",
        "id": "142990"
      },
      {
        "db": "PACKETSTORM",
        "id": "142999"
      },
      {
        "db": "PACKETSTORM",
        "id": "142992"
      },
      {
        "db": "PACKETSTORM",
        "id": "143016"
      },
      {
        "db": "PACKETSTORM",
        "id": "143096"
      },
      {
        "db": "PACKETSTORM",
        "id": "143196"
      }
    ],
    "trust": 2.61
  },
  "exploit_availability": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/exploit_availability#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "reference": "https://vulmon.com/exploitdetails?qidtp=exploitdb\u0026qid=42276",
        "trust": 0.3,
        "type": "exploit"
      },
      {
        "reference": "https://www.scap.org.cn/vuln/vhn-100094",
        "trust": 0.1,
        "type": "unknown"
      }
    ],
    "sources": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "external_ids": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/external_ids#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "db": "NVD",
        "id": "CVE-2017-1000366",
        "trust": 3.5
      },
      {
        "db": "BID",
        "id": "99127",
        "trust": 2.1
      },
      {
        "db": "MCAFEE",
        "id": "SB10205",
        "trust": 2.1
      },
      {
        "db": "EXPLOIT-DB",
        "id": "42274",
        "trust": 1.8
      },
      {
        "db": "EXPLOIT-DB",
        "id": "42276",
        "trust": 1.8
      },
      {
        "db": "EXPLOIT-DB",
        "id": "42275",
        "trust": 1.8
      },
      {
        "db": "PACKETSTORM",
        "id": "154361",
        "trust": 1.8
      },
      {
        "db": "SECTRACK",
        "id": "1038712",
        "trust": 1.8
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209",
        "trust": 0.8
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808",
        "trust": 0.7
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2019.3313",
        "trust": 0.6
      },
      {
        "db": "PACKETSTORM",
        "id": "142990",
        "trust": 0.2
      },
      {
        "db": "PACKETSTORM",
        "id": "142992",
        "trust": 0.2
      },
      {
        "db": "PACKETSTORM",
        "id": "142999",
        "trust": 0.2
      },
      {
        "db": "PACKETSTORM",
        "id": "143196",
        "trust": 0.2
      },
      {
        "db": "PACKETSTORM",
        "id": "143205",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143001",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143207",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143005",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143201",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143225",
        "trust": 0.1
      },
      {
        "db": "VULHUB",
        "id": "VHN-100094",
        "trust": 0.1
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143016",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "143096",
        "trust": 0.1
      }
    ],
    "sources": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "BID",
        "id": "99127"
      },
      {
        "db": "PACKETSTORM",
        "id": "142990"
      },
      {
        "db": "PACKETSTORM",
        "id": "142999"
      },
      {
        "db": "PACKETSTORM",
        "id": "142992"
      },
      {
        "db": "PACKETSTORM",
        "id": "143016"
      },
      {
        "db": "PACKETSTORM",
        "id": "143096"
      },
      {
        "db": "PACKETSTORM",
        "id": "143196"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "id": "VAR-201706-0334",
  "iot": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/iot#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": true,
    "sources": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      }
    ],
    "trust": 0.01
  },
  "last_update_date": "2025-12-22T22:38:08.762000Z",
  "patch": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/patch#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "title": "CVE-2017-1000366",
        "trust": 0.8,
        "url": "https://access.redhat.com/security/cve/CVE-2017-1000366"
      },
      {
        "title": "CVE-2017-1000366",
        "trust": 0.8,
        "url": "https://www.suse.com/security/cve/CVE-2017-1000366/"
      },
      {
        "title": "SUSE products and a new security bug class referred to as \"Stack Clash\".",
        "trust": 0.8,
        "url": "https://www.suse.com/support/kb/doc/?id=7020973"
      },
      {
        "title": "glibc Security vulnerabilities",
        "trust": 0.6,
        "url": "http://www.cnnvd.org.cn/web/xxk/bdxqById.tag?id=71084"
      },
      {
        "title": "Red Hat: Important: glibc security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20171480 - Security Advisory"
      },
      {
        "title": "Red Hat: Important: glibc security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20171481 - Security Advisory"
      },
      {
        "title": "Red Hat: Important: glibc security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20171479 - Security Advisory"
      },
      {
        "title": "Red Hat: Important: Red Hat Container Development Kit 3.0.0 security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20171567 - Security Advisory"
      },
      {
        "title": "Ubuntu Security Notice: eglibc, glibc vulnerability",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3323-1"
      },
      {
        "title": "Ubuntu Security Notice: eglibc vulnerability",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3323-2"
      },
      {
        "title": "Debian Security Advisories: DSA-3887-1 glibc -- security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_security_advisories\u0026qid=09de7cf27f70b4503f183a914f8b80ac"
      },
      {
        "title": "Red Hat: Important: Red Hat 3scale API Management Platform 2.0.0 security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20171712 - Security Advisory"
      },
      {
        "title": "Amazon Linux AMI: ALAS-2017-844",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=amazon_linux_ami\u0026qid=ALAS-2017-844"
      },
      {
        "title": "Arch Linux Advisories: [ASA-201706-22] lib32-glibc: privilege escalation",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=arch_linux_advisories\u0026qid=ASA-201706-22"
      },
      {
        "title": "Arch Linux Advisories: [ASA-201706-23] glibc: privilege escalation",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=arch_linux_advisories\u0026qid=ASA-201706-23"
      },
      {
        "title": "Red Hat: CVE-2017-1000366",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_cve_database\u0026qid=CVE-2017-1000366"
      },
      {
        "title": "Arch Linux Issues: ",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=arch_linux_issues\u0026qid=CVE-2017-1000366"
      },
      {
        "title": "Red Hat: Moderate: glibc security, bug fix, and enhancement update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20180805 - Security Advisory"
      },
      {
        "title": "Brocade Security Advisories: BSA-2017-355",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=brocade_security_advisories\u0026qid=ceec973689010b3f9fce9a7f3e1542a1"
      },
      {
        "title": "Oracle VM Server for x86 Bulletins: Oracle VM Server for x86 Bulletin - July 2017",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=oracle_vm_server_for_x86_bulletins\u0026qid=f1373f5dee274fec5bdcbc4c7e701395"
      },
      {
        "title": "IBM: IBM Security Bulletin: Vyatta 5600 vRouter Software Patches \u2013 Release 1801-za",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ibm_psirt_blog\u0026qid=8710e4e233940f7482a6adad4643a7a8"
      },
      {
        "title": "Oracle Linux Bulletins: Oracle Linux Bulletin - July 2017",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=oracle_linux_bulletins\u0026qid=549dc795290b298746065b62b4bb7928"
      },
      {
        "title": "ansible-everyday",
        "trust": 0.1,
        "url": "https://github.com/kaosagnt/ansible-everyday "
      },
      {
        "title": "Exp101tsArchiv30thers",
        "trust": 0.1,
        "url": "https://github.com/nu11secur1ty/Exp101tsArchiv30thers "
      },
      {
        "title": "awesome-cve-poc_qazbnm456",
        "trust": 0.1,
        "url": "https://github.com/xbl3/awesome-cve-poc_qazbnm456 "
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      }
    ]
  },
  "problemtype_data": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "problemtype": "CWE-119",
        "trust": 1.9
      }
    ],
    "sources": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "references": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/references#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "trust": 2.4,
        "url": "http://www.securityfocus.com/bid/99127"
      },
      {
        "trust": 2.4,
        "url": "http://www.debian.org/security/2017/dsa-3887"
      },
      {
        "trust": 2.4,
        "url": "http://packetstormsecurity.com/files/154361/cisco-device-hardcoded-credentials-gnu-glibc-busybox.html"
      },
      {
        "trust": 2.3,
        "url": "https://access.redhat.com/security/cve/cve-2017-1000366"
      },
      {
        "trust": 2.2,
        "url": "https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt"
      },
      {
        "trust": 1.9,
        "url": "https://www.exploit-db.com/exploits/42276/"
      },
      {
        "trust": 1.9,
        "url": "https://access.redhat.com/errata/rhsa-2017:1479"
      },
      {
        "trust": 1.9,
        "url": "https://access.redhat.com/errata/rhsa-2017:1480"
      },
      {
        "trust": 1.9,
        "url": "https://access.redhat.com/errata/rhsa-2017:1567"
      },
      {
        "trust": 1.8,
        "url": "https://seclists.org/bugtraq/2019/sep/7"
      },
      {
        "trust": 1.8,
        "url": "https://www.suse.com/security/cve/cve-2017-1000366/"
      },
      {
        "trust": 1.8,
        "url": "https://www.suse.com/support/kb/doc/?id=7020973"
      },
      {
        "trust": 1.8,
        "url": "https://www.exploit-db.com/exploits/42274/"
      },
      {
        "trust": 1.8,
        "url": "https://www.exploit-db.com/exploits/42275/"
      },
      {
        "trust": 1.8,
        "url": "http://seclists.org/fulldisclosure/2019/sep/7"
      },
      {
        "trust": 1.8,
        "url": "https://security.gentoo.org/glsa/201706-19"
      },
      {
        "trust": 1.8,
        "url": "https://access.redhat.com/errata/rhsa-2017:1481"
      },
      {
        "trust": 1.8,
        "url": "https://access.redhat.com/errata/rhsa-2017:1712"
      },
      {
        "trust": 1.8,
        "url": "http://www.securitytracker.com/id/1038712"
      },
      {
        "trust": 1.7,
        "url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=sb10205"
      },
      {
        "trust": 1.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000366"
      },
      {
        "trust": 0.8,
        "url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2017-1000366"
      },
      {
        "trust": 0.6,
        "url": "https://www.ibm.com/support/docview.wss?uid=ibm10960426"
      },
      {
        "trust": 0.6,
        "url": "https://www.ibm.com/support/docview.wss?uid=ibm10887793"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2019.3313/"
      },
      {
        "trust": 0.6,
        "url": "https://www-01.ibm.com/support/docview.wss?uid=ibm10960426"
      },
      {
        "trust": 0.3,
        "url": "https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=efa26d9c13a6fabd34a05139e1d8b2e441b2fae9"
      },
      {
        "trust": 0.3,
        "url": "http://www.gnu.org/software/libc/"
      },
      {
        "trust": 0.3,
        "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1452543"
      },
      {
        "trust": 0.3,
        "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=cve-2017-1000366"
      },
      {
        "trust": 0.3,
        "url": "https://www.oracle.com/technetwork/topics/security/linuxbulletinjul2017-3832368.html"
      },
      {
        "trust": 0.3,
        "url": "https://www.oracle.com/technetwork/topics/security/ovmbulletinjul2017-3832369.html"
      },
      {
        "trust": 0.3,
        "url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=sb10205\u0026actp=null\u0026viewlocale=en_us\u0026showdraft=false\u0026platinum_status=false\u0026locale=en_us"
      },
      {
        "trust": 0.2,
        "url": "https://www.ubuntu.com/usn/usn-3323-1"
      },
      {
        "trust": 0.2,
        "url": "https://www.redhat.com/mailman/listinfo/rhsa-announce"
      },
      {
        "trust": 0.2,
        "url": "https://bugzilla.redhat.com/):"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/team/contact/"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/updates/classification/#important"
      },
      {
        "trust": 0.1,
        "url": "https://kc.mcafee.com/corporate/index?page=content\u0026amp;id=sb10205"
      },
      {
        "trust": 0.1,
        "url": "https://cwe.mitre.org/data/definitions/119.html"
      },
      {
        "trust": 0.1,
        "url": "https://usn.ubuntu.com/3323-1/"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov"
      },
      {
        "trust": 0.1,
        "url": "https://tools.cisco.com/security/center/viewalert.x?alertid=54249"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.24-3ubuntu2.2"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu9"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.13"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.24-9ubuntu2.2"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/vulnerabilities/stackguard"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/team/key/"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/articles/11258"
      },
      {
        "trust": 0.1,
        "url": "https://www.debian.org/security/"
      },
      {
        "trust": 0.1,
        "url": "https://www.debian.org/security/faq"
      },
      {
        "trust": 0.1,
        "url": "https://googleprojectzero.blogspot.com/2016/06/exploiting-recursion-in-linux-kernel_20.html"
      },
      {
        "trust": 0.1,
        "url": "https://grsecurity.net/"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000370"
      },
      {
        "trust": 0.1,
        "url": "http://cansecwest.com/core05/memory_vulns_delalleau.pdf"
      },
      {
        "trust": 0.1,
        "url": "https://cybersecurity.upv.es/attacks/offset2lib/offset2lib.html"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000373"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000371"
      },
      {
        "trust": 0.1,
        "url": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d1fd836dcf00d2028c700c7e44d2c23404062c90"
      },
      {
        "trust": 0.1,
        "url": "https://en.wikipedia.org/wiki/irwin-hall_distribution),"
      },
      {
        "trust": 0.1,
        "url": "https://grsecurity.net/features.php);"
      },
      {
        "trust": 0.1,
        "url": "https://bugzilla.redhat.com/show_bug.cgi?id=cve-2010-2240"
      },
      {
        "trust": 0.1,
        "url": "https://jon.oberheide.org/files/infiltrate12-thestackisback.pdf"
      },
      {
        "trust": 0.1,
        "url": "http://phrack.org/issues/63/14.html"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2010-2240"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000365"
      },
      {
        "trust": 0.1,
        "url": "http://www.gnu.org/software/cflow/);"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000376"
      },
      {
        "trust": 0.1,
        "url": "http://blog.exodusintel.com/2013/01/07/who-was-phone/"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-3672"
      },
      {
        "trust": 0.1,
        "url": "https://jon.oberheide.org/blog/2010/11/29/exploiting-stack-overflows-in-the-linux-kernel/"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000369"
      },
      {
        "trust": 0.1,
        "url": "http://www.invisiblethingslab.com/resources/misc-2010/xorg-large-memory-attacks.pdf"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1083"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000372"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1082"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-1000364"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-7502"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2017-1000364"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2017-7502"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/downloads/content/293/"
      },
      {
        "trust": 0.1,
        "url": "https://www.ubuntu.com/usn/usn-3323-2"
      }
    ],
    "sources": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "BID",
        "id": "99127"
      },
      {
        "db": "PACKETSTORM",
        "id": "142990"
      },
      {
        "db": "PACKETSTORM",
        "id": "142999"
      },
      {
        "db": "PACKETSTORM",
        "id": "142992"
      },
      {
        "db": "PACKETSTORM",
        "id": "143016"
      },
      {
        "db": "PACKETSTORM",
        "id": "143096"
      },
      {
        "db": "PACKETSTORM",
        "id": "143196"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "sources": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "db": "BID",
        "id": "99127"
      },
      {
        "db": "PACKETSTORM",
        "id": "142990"
      },
      {
        "db": "PACKETSTORM",
        "id": "142999"
      },
      {
        "db": "PACKETSTORM",
        "id": "142992"
      },
      {
        "db": "PACKETSTORM",
        "id": "143016"
      },
      {
        "db": "PACKETSTORM",
        "id": "143096"
      },
      {
        "db": "PACKETSTORM",
        "id": "143196"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "sources_release_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2017-06-19T00:00:00",
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "date": "2017-06-19T00:00:00",
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "date": "2017-06-19T00:00:00",
        "db": "BID",
        "id": "99127"
      },
      {
        "date": "2017-06-19T23:52:57",
        "db": "PACKETSTORM",
        "id": "142990"
      },
      {
        "date": "2017-06-19T23:54:30",
        "db": "PACKETSTORM",
        "id": "142999"
      },
      {
        "date": "2017-06-19T23:53:10",
        "db": "PACKETSTORM",
        "id": "142992"
      },
      {
        "date": "2017-06-20T00:36:06",
        "db": "PACKETSTORM",
        "id": "143016"
      },
      {
        "date": "2017-06-21T22:27:41",
        "db": "PACKETSTORM",
        "id": "143096"
      },
      {
        "date": "2017-06-30T06:41:55",
        "db": "PACKETSTORM",
        "id": "143196"
      },
      {
        "date": "2017-06-20T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "date": "2017-07-21T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "date": "2017-06-19T16:29:00.310000",
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "sources_update_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2020-10-15T00:00:00",
        "db": "VULHUB",
        "id": "VHN-100094"
      },
      {
        "date": "2020-10-15T00:00:00",
        "db": "VULMON",
        "id": "CVE-2017-1000366"
      },
      {
        "date": "2017-09-05T20:13:00",
        "db": "BID",
        "id": "99127"
      },
      {
        "date": "2019-09-06T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      },
      {
        "date": "2017-07-21T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      },
      {
        "date": "2025-04-20T01:37:25.860000",
        "db": "NVD",
        "id": "CVE-2017-1000366"
      }
    ]
  },
  "threat_type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/threat_type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "local",
    "sources": [
      {
        "db": "BID",
        "id": "99127"
      },
      {
        "db": "PACKETSTORM",
        "id": "142990"
      },
      {
        "db": "PACKETSTORM",
        "id": "142992"
      },
      {
        "db": "PACKETSTORM",
        "id": "143196"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      }
    ],
    "trust": 1.2
  },
  "title": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/title#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "glibc Buffer error vulnerability",
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2017-005209"
      }
    ],
    "trust": 0.8
  },
  "type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "buffer error",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-201706-808"
      }
    ],
    "trust": 0.6
  }
}

{
  "@context": {
    "@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
    "affected_products": {
      "@id": "https://www.variotdbs.pl/ref/affected_products"
    },
    "configurations": {
      "@id": "https://www.variotdbs.pl/ref/configurations"
    },
    "credits": {
      "@id": "https://www.variotdbs.pl/ref/credits"
    },
    "cvss": {
      "@id": "https://www.variotdbs.pl/ref/cvss/"
    },
    "description": {
      "@id": "https://www.variotdbs.pl/ref/description/"
    },
    "exploit_availability": {
      "@id": "https://www.variotdbs.pl/ref/exploit_availability/"
    },
    "external_ids": {
      "@id": "https://www.variotdbs.pl/ref/external_ids/"
    },
    "iot": {
      "@id": "https://www.variotdbs.pl/ref/iot/"
    },
    "iot_taxonomy": {
      "@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
    },
    "patch": {
      "@id": "https://www.variotdbs.pl/ref/patch/"
    },
    "problemtype_data": {
      "@id": "https://www.variotdbs.pl/ref/problemtype_data/"
    },
    "references": {
      "@id": "https://www.variotdbs.pl/ref/references/"
    },
    "sources": {
      "@id": "https://www.variotdbs.pl/ref/sources/"
    },
    "sources_release_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_release_date/"
    },
    "sources_update_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_update_date/"
    },
    "threat_type": {
      "@id": "https://www.variotdbs.pl/ref/threat_type/"
    },
    "title": {
      "@id": "https://www.variotdbs.pl/ref/title/"
    },
    "type": {
      "@id": "https://www.variotdbs.pl/ref/type/"
    }
  },
  "@id": "https://www.variotdbs.pl/vuln/VAR-201509-0438",
  "affected_products": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/affected_products#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "model": "linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "debian",
        "version": "7.0"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "12.04"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "15.04"
      },
      {
        "model": "glibc",
        "scope": "lte",
        "trust": 1.0,
        "vendor": "gnu",
        "version": "2.21"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "14.04"
      },
      {
        "model": "linux enterprise debuginfo",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "11"
      },
      {
        "model": "linux enterprise server",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "11"
      },
      {
        "model": "linux enterprise desktop",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "suse",
        "version": "11"
      },
      {
        "model": "c library",
        "scope": "lt",
        "trust": 0.8,
        "vendor": "gnu",
        "version": "2.22"
      },
      {
        "model": "suse linux enterprise debuginfo",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp3"
      },
      {
        "model": "suse linux enterprise debuginfo",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp4"
      },
      {
        "model": "suse linux enterprise desktop",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp3"
      },
      {
        "model": "suse linux enterprise desktop",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp4"
      },
      {
        "model": "suse linux enterprise server",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp3"
      },
      {
        "model": "suse linux enterprise server",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp4"
      },
      {
        "model": "suse linux enterprise server",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "for vmware 11-sp3"
      },
      {
        "model": "suse linux enterprise software development kit",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp3"
      },
      {
        "model": "suse linux enterprise software development kit",
        "scope": "eq",
        "trust": 0.8,
        "vendor": "novell",
        "version": "11-sp4"
      },
      {
        "model": "linux enterprise desktop",
        "scope": "eq",
        "trust": 0.6,
        "vendor": "suse",
        "version": "11.0"
      },
      {
        "model": "linux enterprise debuginfo",
        "scope": "eq",
        "trust": 0.6,
        "vendor": "suse",
        "version": "11.0"
      },
      {
        "model": "linux enterprise server",
        "scope": "eq",
        "trust": 0.6,
        "vendor": "suse",
        "version": "11.0"
      },
      {
        "model": "security network intrusion prevention system gv200",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx7412-05",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2.0.3"
      },
      {
        "model": "security network intrusion prevention system gx5108-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx5008-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx7412",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx5208",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx5208-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "power hmc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "8.3.0.0"
      },
      {
        "model": "security network intrusion prevention system gx4002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx4004",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "linux arm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gx5108",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gv1000",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "linux ia-64",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gx5108",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "6.2"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.3.0"
      },
      {
        "model": "security network intrusion prevention system gx3002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "enterprise linux server",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "6"
      },
      {
        "model": "powerkvm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.1"
      },
      {
        "model": "ds8700",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "76.31.143.0"
      },
      {
        "model": "security network intrusion prevention system gx5008",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx5208-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx7412-10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gv200",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "datapower gateways",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "6.0.1.11"
      },
      {
        "model": "security network intrusion prevention system gx5108-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx5008-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx7412-05",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "proventia network enterprise scanner",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.3"
      },
      {
        "model": "security virtual server protection for vmware",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.1"
      },
      {
        "model": "power hmc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "8.1.0.0"
      },
      {
        "model": "security network intrusion prevention system gx5008-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2.0.1"
      },
      {
        "model": "security network intrusion prevention system gx5208",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx7800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "smartcloud entry appliance fp",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1.0.4"
      },
      {
        "model": "enterprise linux workstation",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "6"
      },
      {
        "model": "security network intrusion prevention system gx7412-10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx6116",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx5108",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "powerkvm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1"
      },
      {
        "model": "security network intrusion prevention system gv1000",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "power hmc sp1",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "8.8.2.0"
      },
      {
        "model": "security network intrusion prevention system gx7412-10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx3002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "smartcloud entry appliance fp",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.4.0.3"
      },
      {
        "model": "security network intrusion prevention system gx5008",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "ds8700",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "87.51.14.x"
      },
      {
        "model": "security network intrusion prevention system gx7412-05",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "datapower gateways",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.1.0.6"
      },
      {
        "model": "security network intrusion prevention system gx5008",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "power hmc sp2",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "8.8.1.0"
      },
      {
        "model": "security network intrusion prevention system gx5208",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx4004-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "ib6131 gb infiniband switch",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "83.4"
      },
      {
        "model": "ds8800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "86.31.167.0"
      },
      {
        "model": "security network intrusion prevention system gx5008-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "tssc",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.5"
      },
      {
        "model": "datapower gateways",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.0.0.9"
      },
      {
        "model": "smartcloud entry appliance fix pack",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.11"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1.0.2"
      },
      {
        "model": "security network intrusion prevention system gx7800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx4002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx6116",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx4004",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "flex system en6131 40gb ethernet switch",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2"
      },
      {
        "model": "security network intrusion prevention system gx7412-10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "linux sparc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gv200",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx4004-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx5108-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx7412",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx5008",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx5208-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1.0.1"
      },
      {
        "model": "datapower gateways",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.2.0.1"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2.0.2"
      },
      {
        "model": "power hmc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "8.2.0.0"
      },
      {
        "model": "security network intrusion prevention system gv200",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx4002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx5108-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1.0.3"
      },
      {
        "model": "security network intrusion prevention system gx4002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx7412",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx4004",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "flex system en6131 40gb ethernet switch",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.5.1000"
      },
      {
        "model": "datapower gateways",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "6.0.0.16"
      },
      {
        "model": "enterprise linux server eus 6.6.z",
        "scope": null,
        "trust": 0.3,
        "vendor": "redhat",
        "version": null
      },
      {
        "model": "security network intrusion prevention system gx5108",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx7412",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx6116",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "smartcloud entry appliance fix pack",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.21"
      },
      {
        "model": "centos",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "centos",
        "version": "6"
      },
      {
        "model": "security network intrusion prevention system gx5208-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "6"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2.0.4"
      },
      {
        "model": "security network intrusion prevention system gx4004",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security virtual server protection for vmware",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.1.0.1"
      },
      {
        "model": "enterprise linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "7"
      },
      {
        "model": "security network intrusion prevention system gv1000",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "tssc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.4"
      },
      {
        "model": "security network intrusion prevention system gx3002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "linux",
        "scope": null,
        "trust": 0.3,
        "vendor": "gentoo",
        "version": null
      },
      {
        "model": "security network intrusion prevention system gx7412-05",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "enterprise linux hpc node",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "6"
      },
      {
        "model": "linux amd64",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gx7412-05",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx4002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx7412",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx6116",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx5208",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "smartcloud entry appliance fix pack",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.44"
      },
      {
        "model": "security network intrusion prevention system gx5108",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "security network intrusion prevention system gx7412-10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx5208",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "smartcloud entry appliance fp",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.3.0.3"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1.0.0"
      },
      {
        "model": "security network intrusion prevention system gx4004",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "power hmc",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "8.8.3.0"
      },
      {
        "model": "security network intrusion prevention system gx4004-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gv1000",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx5008-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx3002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gv1000",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.4.0"
      },
      {
        "model": "ds8800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "0"
      },
      {
        "model": "security network intrusion prevention system gx3002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx7800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx5208-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "flex system en6131 40gb ethernet switch",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.4"
      },
      {
        "model": "datapower gateways",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "6.0.0.15"
      },
      {
        "model": "linux ia-32",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gx5108",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "datapower gateways",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.1.0.5"
      },
      {
        "model": "security network intrusion prevention system gv200",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "linux mips",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gx7412-05",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2.0.0"
      },
      {
        "model": "ib6131 gb infiniband switch",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "83.5.1000"
      },
      {
        "model": "datapower gateways",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.2.0.0"
      },
      {
        "model": "security network intrusion prevention system gx5108-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx5008-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx5008",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gx5208",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx7800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx7412-10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "datapower gateways",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "7.0.0.8"
      },
      {
        "model": "linux",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "oracle",
        "version": "0"
      },
      {
        "model": "security network intrusion prevention system gx4004-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx7800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.2"
      },
      {
        "model": "security network intrusion prevention system gx4004-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gv1000",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "flex system chassis management module 2pet",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "security network intrusion prevention system gx3002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "security network intrusion prevention system gx5208-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "linux s/390",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "security network intrusion prevention system gx5008",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "smartcloud entry appliance fp",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.2.0.4"
      },
      {
        "model": "security network intrusion prevention system gx6116",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "security network intrusion prevention system gv200",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "linux powerpc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "debian",
        "version": "6.0"
      },
      {
        "model": "flex system chassis management module 2pet14c-2.5.5c",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "security network intrusion prevention system gx5108-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "ds8700",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "87.41.17.x"
      },
      {
        "model": "smartcloud entry",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.1.0.4"
      },
      {
        "model": "security network intrusion prevention system gx7412",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.1"
      },
      {
        "model": "security network intrusion prevention system gx7800",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.4"
      },
      {
        "model": "ib6131 gb infiniband switch",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "83.2"
      },
      {
        "model": "security network intrusion prevention system gx6116",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.3"
      },
      {
        "model": "security network intrusion prevention system gx4004",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.5"
      },
      {
        "model": "security network intrusion prevention system gx4004-v2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6.2"
      },
      {
        "model": "enterprise linux desktop",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "6"
      },
      {
        "model": "security virtual server protection for vmware",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.1.1"
      },
      {
        "model": "datapower gateways",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "6.0.1.12"
      },
      {
        "model": "security network intrusion prevention system gx4002",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "4.6"
      },
      {
        "model": "smartcloud entry appliance fp",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.2.0.3"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "0"
      }
    ],
    "sources": [
      {
        "db": "BID",
        "id": "74255"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "configurations": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/configurations#",
      "children": {
        "@container": "@list"
      },
      "cpe_match": {
        "@container": "@list"
      },
      "data": {
        "@container": "@list"
      },
      "nodes": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "cpe_match": [
              {
                "cpe22Uri": "cpe:/a:gnu:glibc",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:novell:suse_linux_enterprise_debuginfo",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:novell:suse_linux_enterprise_desktop",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:novell:suse_linux_enterprise_server",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/a:novell:suse_linux_enterprise_software_development_kit",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      }
    ]
  },
  "credits": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/credits#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "Arjun Shankar of Red Hat",
    "sources": [
      {
        "db": "BID",
        "id": "74255"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      }
    ],
    "trust": 0.9
  },
  "cve": "CVE-2015-1781",
  "cvss": {
    "@context": {
      "cvssV2": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
      },
      "cvssV3": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
      },
      "severity": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/cvss/severity#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/severity"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "cvssV2": [
          {
            "accessComplexity": "MEDIUM",
            "accessVector": "NETWORK",
            "authentication": "NONE",
            "author": "nvd@nist.gov",
            "availabilityImpact": "PARTIAL",
            "baseScore": 6.8,
            "confidentialityImpact": "PARTIAL",
            "exploitabilityScore": 8.6,
            "id": "CVE-2015-1781",
            "impactScore": 6.4,
            "integrityImpact": "PARTIAL",
            "severity": "MEDIUM",
            "trust": 1.9,
            "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P",
            "version": "2.0"
          }
        ],
        "cvssV3": [],
        "severity": [
          {
            "author": "nvd@nist.gov",
            "id": "CVE-2015-1781",
            "trust": 1.0,
            "value": "MEDIUM"
          },
          {
            "author": "NVD",
            "id": "CVE-2015-1781",
            "trust": 0.8,
            "value": "Medium"
          },
          {
            "author": "CNNVD",
            "id": "CNNVD-201505-071",
            "trust": 0.6,
            "value": "MEDIUM"
          },
          {
            "author": "VULMON",
            "id": "CVE-2015-1781",
            "trust": 0.1,
            "value": "MEDIUM"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "description": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/description#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "Buffer overflow in the gethostbyname_r and other unspecified NSS functions in the GNU C Library (aka glibc or libc6) before 2.22 allows context-dependent attackers to cause a denial of service (crash) or execute arbitrary code via a crafted DNS response, which triggers a call with a misaligned buffer. GNU glibc is prone to multiple buffer-overflow vulnerabilities because it fails to properly bounds-check user-supplied data before copying it into an insufficiently sized buffer. \nAn attacker can exploit these issues to execute arbitrary code in the context of the affected application. Failed exploit attempts may crash the application, denying service to legitimate users. \n _______________________________________________________________________\n\n References:\n\n http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7423\n http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1781\n https://rhn.redhat.com/errata/RHSA-2015-0863.html\n _______________________________________________________________________\n\n Updated Packages:\n\n Mandriva Business Server 1/X86_64:\n 92aa475c44c712eaf19898ef76e04183  mbs1/x86_64/glibc-2.14.1-12.12.mbs1.x86_64.rpm\n 606cdd33e041f9853eae18f53c9d73de  mbs1/x86_64/glibc-devel-2.14.1-12.12.mbs1.x86_64.rpm\n 133deb850840d464335e5c659cba1627  mbs1/x86_64/glibc-doc-2.14.1-12.12.mbs1.noarch.rpm\n 7a3d5170647c52cd4a34d2dcda711397  mbs1/x86_64/glibc-doc-pdf-2.14.1-12.12.mbs1.noarch.rpm\n 96c842afb6110ac18a40b843b51548fc  mbs1/x86_64/glibc-i18ndata-2.14.1-12.12.mbs1.x86_64.rpm\n 703e73278d416a53096fe19c7652c95e  mbs1/x86_64/glibc-profile-2.14.1-12.12.mbs1.x86_64.rpm\n 12f09ed16d9c4b0f9a94e931569dacc3  mbs1/x86_64/glibc-static-devel-2.14.1-12.12.mbs1.x86_64.rpm\n 09715361d0af4a4dd5fba44239c5e690  mbs1/x86_64/glibc-utils-2.14.1-12.12.mbs1.x86_64.rpm\n c9a293ac29070d215eb1988bba58aaec  mbs1/x86_64/nscd-2.14.1-12.12.mbs1.x86_64.rpm \n 8d8b74de2d7c0e982e0ad82ac73091b2  mbs1/SRPMS/glibc-2.14.1-12.12.mbs1.src.rpm\n\n Mandriva Business Server 2/X86_64:\n e59cee8712d211add638c1b6c1952fa6  mbs2/x86_64/glibc-2.18-10.2.mbs2.x86_64.rpm\n baf9e44f8c4f82c75a0154d44b6fce72  mbs2/x86_64/glibc-devel-2.18-10.2.mbs2.x86_64.rpm\n f3eb6e3ed435f8a06dcffbfa7a44525b  mbs2/x86_64/glibc-doc-2.18-10.2.mbs2.noarch.rpm\n 5df45f7cae82ef7d354fa14c7ac363c9  mbs2/x86_64/glibc-i18ndata-2.18-10.2.mbs2.x86_64.rpm\n 24ef48d58c7a4114068e7b70dbefad79  mbs2/x86_64/glibc-profile-2.18-10.2.mbs2.x86_64.rpm\n 5f67c12f02dbc3f4cbf78f1a8c7d5ad5  mbs2/x86_64/glibc-static-devel-2.18-10.2.mbs2.x86_64.rpm\n f24e67e1ed1b01e5305c28b3a9b02852  mbs2/x86_64/glibc-utils-2.18-10.2.mbs2.x86_64.rpm\n bae4b399bc43be8af24ddd93257ca31a  mbs2/x86_64/nscd-2.18-10.2.mbs2.x86_64.rpm \n 740d9b3d14292be8847da92243340b62  mbs2/SRPMS/glibc-2.18-10.2.mbs2.src.rpm\n _______________________________________________________________________\n\n To upgrade automatically use MandrivaUpdate or urpmi.  The verification\n of md5 checksums and GPG signatures is performed automatically for you. -----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n=====================================================================\n                   Red Hat Security Advisory\n\nSynopsis:          Moderate: glibc security, bug fix, and enhancement update\nAdvisory ID:       RHSA-2015:2199-07\nProduct:           Red Hat Enterprise Linux\nAdvisory URL:      https://rhn.redhat.com/errata/RHSA-2015-2199.html\nIssue date:        2015-11-19\nCVE Names:         CVE-2013-7423 CVE-2015-1472 CVE-2015-1473 \n                   CVE-2015-1781 \n=====================================================================\n\n1. Summary:\n\nUpdated glibc packages that fix multiple security issues, several bugs, and\nadd one enhancement are now available for Red Hat Enterprise Linux 7. \n\nRed Hat Product Security has rated this update as having Moderate security\nimpact. Common Vulnerability Scoring System (CVSS) base scores, which give\ndetailed severity ratings, are available for each vulnerability from the\nCVE links in the References section. \n\n2. Relevant releases/architectures:\n\nRed Hat Enterprise Linux Client (v. 7) - x86_64\nRed Hat Enterprise Linux Client Optional (v. 7) - x86_64\nRed Hat Enterprise Linux ComputeNode (v. 7) - x86_64\nRed Hat Enterprise Linux ComputeNode Optional (v. 7) - x86_64\nRed Hat Enterprise Linux Server (v. 7) - aarch64, ppc64, ppc64le, s390x, x86_64\nRed Hat Enterprise Linux Server Optional (v. 7) - aarch64, ppc64, ppc64le, s390x, x86_64\nRed Hat Enterprise Linux Workstation (v. 7) - x86_64\nRed Hat Enterprise Linux Workstation Optional (v. 7) - x86_64\n\n3. Description:\n\nThe glibc packages provide the standard C libraries (libc), POSIX thread\nlibraries (libpthread), standard math libraries (libm), and the Name Server\nCaching Daemon (nscd) used by multiple programs on the system. \nWithout these libraries, the Linux system cannot function correctly. \n\nIt was discovered that, under certain circumstances, glibc\u0027s getaddrinfo()\nfunction would send DNS queries to random file descriptors. An attacker\ncould potentially use this flaw to send DNS queries to unintended\nrecipients, resulting in information disclosure or data loss due to the\napplication encountering corrupted data. (CVE-2013-7423)\n\nA buffer overflow flaw was found in the way glibc\u0027s gethostbyname_r() and\nother related functions computed the size of a buffer when passed a\nmisaligned buffer as input. (CVE-2015-1781)\n\nA heap-based buffer overflow flaw and a stack overflow flaw were found in\nglibc\u0027s swscanf() function. (CVE-2015-1472, CVE-2015-1473)\n\nAn integer overflow flaw, leading to a heap-based buffer overflow, was\nfound in glibc\u0027s _IO_wstr_overflow() function. (BZ#1195762)\n\nA flaw was found in the way glibc\u0027s fnmatch() function processed certain\nmalformed patterns. An attacker able to make an application call this\nfunction could use this flaw to crash that application. (BZ#1197730)\n\nThe CVE-2015-1781 issue was discovered by Arjun Shankar of Red Hat. \n\nThese updated glibc packages also include numerous bug fixes and one\nenhancement. Space precludes documenting all of these changes in this\nadvisory. For information on the most significant of these changes, users\nare directed to the following article on the Red Hat Customer Portal:\n\nhttps://access.redhat.com/articles/2050743\n\nAll glibc users are advised to upgrade to these updated packages, which\ncontain backported patches to correct these issues and add these\nenhancements. \n\n4. Solution:\n\nBefore applying this update, make sure all previously released errata\nrelevant to your system have been applied. \n\nFor details on how to apply this update, refer to:\n\nhttps://access.redhat.com/articles/11258\n\n5. Bugs fixed (https://bugzilla.redhat.com/):\n\n1064066 - Test suite failure: test-ldouble\n1098042 - getaddrinfo return EAI_NONAME instead of EAI_AGAIN in case the DNS query times out\n1144133 - calloc in dl-reloc.c computes size incorrectly\n1187109 - CVE-2013-7423 glibc: getaddrinfo() writes DNS queries to random file descriptors under high load\n1188235 - CVE-2015-1472 glibc: heap buffer overflow in glibc swscanf\n1195762 - glibc: _IO_wstr_overflow integer overflow\n1197730 - glibc: potential denial of service in internal_fnmatch()\n1199525 - CVE-2015-1781 glibc: buffer overflow in gethostbyname_r() and related functions with misaligned buffer\n1207032 - glibc deadlock when printing backtrace from memory allocator\n1209105 - CVE-2015-1473 glibc: Stack-overflow in glibc swscanf\n1219891 - Missing define for TCP_USER_TIMEOUT in netinet/tcp.h\n1225490 - [RFE] Unconditionally enable SDT probes in glibc builds. \n\n6. Package List:\n\nRed Hat Enterprise Linux Client (v. 7):\n\nSource:\nglibc-2.17-105.el7.src.rpm\n\nx86_64:\nglibc-2.17-105.el7.i686.rpm\nglibc-2.17-105.el7.x86_64.rpm\nglibc-common-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-devel-2.17-105.el7.i686.rpm\nglibc-devel-2.17-105.el7.x86_64.rpm\nglibc-headers-2.17-105.el7.x86_64.rpm\nglibc-utils-2.17-105.el7.x86_64.rpm\nnscd-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux Client Optional (v. 7):\n\nx86_64:\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-static-2.17-105.el7.i686.rpm\nglibc-static-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux ComputeNode (v. 7):\n\nSource:\nglibc-2.17-105.el7.src.rpm\n\nx86_64:\nglibc-2.17-105.el7.i686.rpm\nglibc-2.17-105.el7.x86_64.rpm\nglibc-common-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-devel-2.17-105.el7.i686.rpm\nglibc-devel-2.17-105.el7.x86_64.rpm\nglibc-headers-2.17-105.el7.x86_64.rpm\nglibc-utils-2.17-105.el7.x86_64.rpm\nnscd-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux ComputeNode Optional (v. 7):\n\nx86_64:\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-static-2.17-105.el7.i686.rpm\nglibc-static-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux Server (v. 7):\n\nSource:\nglibc-2.17-105.el7.src.rpm\n\naarch64:\nglibc-2.17-105.el7.aarch64.rpm\nglibc-common-2.17-105.el7.aarch64.rpm\nglibc-debuginfo-2.17-105.el7.aarch64.rpm\nglibc-devel-2.17-105.el7.aarch64.rpm\nglibc-headers-2.17-105.el7.aarch64.rpm\nglibc-utils-2.17-105.el7.aarch64.rpm\nnscd-2.17-105.el7.aarch64.rpm\n\nppc64:\nglibc-2.17-105.el7.ppc.rpm\nglibc-2.17-105.el7.ppc64.rpm\nglibc-common-2.17-105.el7.ppc64.rpm\nglibc-debuginfo-2.17-105.el7.ppc.rpm\nglibc-debuginfo-2.17-105.el7.ppc64.rpm\nglibc-debuginfo-common-2.17-105.el7.ppc.rpm\nglibc-debuginfo-common-2.17-105.el7.ppc64.rpm\nglibc-devel-2.17-105.el7.ppc.rpm\nglibc-devel-2.17-105.el7.ppc64.rpm\nglibc-headers-2.17-105.el7.ppc64.rpm\nglibc-utils-2.17-105.el7.ppc64.rpm\nnscd-2.17-105.el7.ppc64.rpm\n\nppc64le:\nglibc-2.17-105.el7.ppc64le.rpm\nglibc-common-2.17-105.el7.ppc64le.rpm\nglibc-debuginfo-2.17-105.el7.ppc64le.rpm\nglibc-debuginfo-common-2.17-105.el7.ppc64le.rpm\nglibc-devel-2.17-105.el7.ppc64le.rpm\nglibc-headers-2.17-105.el7.ppc64le.rpm\nglibc-utils-2.17-105.el7.ppc64le.rpm\nnscd-2.17-105.el7.ppc64le.rpm\n\ns390x:\nglibc-2.17-105.el7.s390.rpm\nglibc-2.17-105.el7.s390x.rpm\nglibc-common-2.17-105.el7.s390x.rpm\nglibc-debuginfo-2.17-105.el7.s390.rpm\nglibc-debuginfo-2.17-105.el7.s390x.rpm\nglibc-debuginfo-common-2.17-105.el7.s390.rpm\nglibc-debuginfo-common-2.17-105.el7.s390x.rpm\nglibc-devel-2.17-105.el7.s390.rpm\nglibc-devel-2.17-105.el7.s390x.rpm\nglibc-headers-2.17-105.el7.s390x.rpm\nglibc-utils-2.17-105.el7.s390x.rpm\nnscd-2.17-105.el7.s390x.rpm\n\nx86_64:\nglibc-2.17-105.el7.i686.rpm\nglibc-2.17-105.el7.x86_64.rpm\nglibc-common-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-devel-2.17-105.el7.i686.rpm\nglibc-devel-2.17-105.el7.x86_64.rpm\nglibc-headers-2.17-105.el7.x86_64.rpm\nglibc-utils-2.17-105.el7.x86_64.rpm\nnscd-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional (v. 7):\n\naarch64:\nglibc-debuginfo-2.17-105.el7.aarch64.rpm\nglibc-static-2.17-105.el7.aarch64.rpm\n\nppc64:\nglibc-debuginfo-2.17-105.el7.ppc.rpm\nglibc-debuginfo-2.17-105.el7.ppc64.rpm\nglibc-debuginfo-common-2.17-105.el7.ppc.rpm\nglibc-debuginfo-common-2.17-105.el7.ppc64.rpm\nglibc-static-2.17-105.el7.ppc.rpm\nglibc-static-2.17-105.el7.ppc64.rpm\n\nppc64le:\nglibc-debuginfo-2.17-105.el7.ppc64le.rpm\nglibc-debuginfo-common-2.17-105.el7.ppc64le.rpm\nglibc-static-2.17-105.el7.ppc64le.rpm\n\ns390x:\nglibc-debuginfo-2.17-105.el7.s390.rpm\nglibc-debuginfo-2.17-105.el7.s390x.rpm\nglibc-debuginfo-common-2.17-105.el7.s390.rpm\nglibc-debuginfo-common-2.17-105.el7.s390x.rpm\nglibc-static-2.17-105.el7.s390.rpm\nglibc-static-2.17-105.el7.s390x.rpm\n\nx86_64:\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-static-2.17-105.el7.i686.rpm\nglibc-static-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux Workstation (v. 7):\n\nSource:\nglibc-2.17-105.el7.src.rpm\n\nx86_64:\nglibc-2.17-105.el7.i686.rpm\nglibc-2.17-105.el7.x86_64.rpm\nglibc-common-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-devel-2.17-105.el7.i686.rpm\nglibc-devel-2.17-105.el7.x86_64.rpm\nglibc-headers-2.17-105.el7.x86_64.rpm\nglibc-utils-2.17-105.el7.x86_64.rpm\nnscd-2.17-105.el7.x86_64.rpm\n\nRed Hat Enterprise Linux Workstation Optional (v. 7):\n\nx86_64:\nglibc-debuginfo-2.17-105.el7.i686.rpm\nglibc-debuginfo-2.17-105.el7.x86_64.rpm\nglibc-debuginfo-common-2.17-105.el7.i686.rpm\nglibc-debuginfo-common-2.17-105.el7.x86_64.rpm\nglibc-static-2.17-105.el7.i686.rpm\nglibc-static-2.17-105.el7.x86_64.rpm\n\nThese packages are GPG signed by Red Hat for security.  Our key and\ndetails on how to verify the signature are available from\nhttps://access.redhat.com/security/team/key/\n\n7. References:\n\nhttps://access.redhat.com/security/cve/CVE-2013-7423\nhttps://access.redhat.com/security/cve/CVE-2015-1472\nhttps://access.redhat.com/security/cve/CVE-2015-1473\nhttps://access.redhat.com/security/cve/CVE-2015-1781\nhttps://access.redhat.com/security/updates/classification/#moderate\nhttps://access.redhat.com/articles/2050743\n\n8. Contact:\n\nThe Red Hat security contact is \u003csecalert@redhat.com\u003e. More contact\ndetails at https://access.redhat.com/security/team/contact/\n\nCopyright 2015 Red Hat, Inc. \n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niD8DBQFWTkEYXlSAg2UNWIIRAueyAJ98kB1kgF2zvCkEn5k70+Aq5ynM3QCfS8Lx\nxSL2O69mtC2Sh4D4RYIP+2k=\n=MEoD\n-----END PGP SIGNATURE-----\n\n--\nRHSA-announce mailing list\nRHSA-announce@redhat.com\nhttps://www.redhat.com/mailman/listinfo/rhsa-announce\n. \n\nThe CVE-2015-7547 vulnerability listed below is considered to have\ncritical impact. \n\nCVE-2014-8121\n\n    Robin Hack discovered that the nss_files database did not\n    correctly implement enumeration interleaved with name-based or\n    ID-based lookups.  This could cause the enumeration enter an\n    endless loop, leading to a denial of service.  Most applications are not\n    affected by this vulnerability because they use aligned buffers. \n\nCVE-2015-7547\n\n    The Google Security Team and Red Hat discovered that the eglibc\n    host name resolver function, getaddrinfo, when processing\n    AF_UNSPEC queries (for dual A/AAAA lookups), could mismanage its\n    internal buffers, leading to a stack-based buffer overflow and\n    arbitrary code execution.  This vulnerability affects most\n    applications which perform host name resolution using getaddrinfo,\n    including system services. \n\nCVE-2015-8776\n\n    Adam Nielsen discovered that if an invalid separated time value\n    is passed to strftime, the strftime function could crash or leak\n    information.  Applications normally pass only valid time\n    information to strftime; no affected applications are known. \n\nCVE-2015-8777\n\n    Hector Marco-Gisbert reported that LD_POINTER_GUARD was not\n    ignored for SUID programs, enabling an unintended bypass of a\n    security feature.  This update causes eglibc to always ignore the\n    LD_POINTER_GUARD environment variable. \n\nCVE-2015-8778\n\n    Szabolcs Nagy reported that the rarely-used hcreate and hcreate_r\n    functions did not check the size argument properly, leading to a\n    crash (denial of service) for certain arguments.  No impacted\n    applications are known at this time. \n\nCVE-2015-8779\n\n    The catopen function contains several unbound stack allocations\n    (stack overflows), causing it the crash the process (denial of\n    service).  No applications where this issue has a security impact\n    are currently known. \n\nThe following fixed vulnerabilities currently lack CVE assignment:\n\n    Joseph Myers reported discovered that an integer overflow in the\n    strxfrm can lead to heap-based buffer overflow, possibly allowing\n    arbitrary code execution.  In addition, a fallback path in strxfrm\n    uses an unbounded stack allocation (stack overflow), leading to a\n    crash or erroneous application behavior. \n\n    Kostya Serebryany reported that the fnmatch function could skip\n    over the terminating NUL character of a malformed pattern, causing\n    an application calling fnmatch to crash (denial of service).  On\n    GNU/Linux systems, wide-oriented character streams are rarely\n    used, and no affected applications are known. \n\n    Andreas Schwab reported a memory leak (memory allocation without a\n    matching deallocation) while processing certain DNS answers in\n    getaddrinfo, related to the _nss_dns_gethostbyname4_r function. \n    This vulnerability could lead to a denial of service. \n\nWhile it is only necessary to ensure that all processes are not using\nthe old eglibc anymore, it is recommended to reboot the machines after\napplying the security upgrade. \n\nFor the oldstable distribution (wheezy), these problems have been fixed\nin version 2.13-38+deb7u10. \n\nWe recommend that you upgrade your eglibc packages. 6) - i386, x86_64\n\n3. \n\nThis update also fixes the following bug:\n\n* Previously, the nscd daemon did not properly reload modified data when\nthe user edited monitored nscd configuration files. As a consequence, nscd\nreturned stale data to system processes. This update adds a system of\ninotify-based monitoring and stat-based backup monitoring for nscd\nconfiguration files. As a result, nscd now detects changes to its\nconfiguration files and reloads the data properly, which prevents it from\nreturning stale data. ==========================================================================\nUbuntu Security Notice USN-2985-2\nMay 26, 2016\n\neglibc, glibc regression\n==========================================================================\n\nA security issue affects these releases of Ubuntu and its derivatives:\n\n- Ubuntu 15.10\n- Ubuntu 14.04 LTS\n- Ubuntu 12.04 LTS\n\nSummary:\n\nUSN-2985-1 introduced a regression in the GNU C Library. \n\nSoftware Description:\n- glibc: GNU C Library\n- eglibc: GNU C Library\n\nDetails:\n\nUSN-2985-1 fixed vulnerabilities in the GNU C Library. The fix for\nCVE-2014-9761 introduced a regression which affected applications that\nuse the libm library but were not fully restarted after the upgrade. \nThis update removes the fix for CVE-2014-9761 and a future update\nwill be provided to address this issue. \n\nWe apologize for the inconvenience. \n\nOriginal advisory details:\n\n Martin Carpenter discovered that pt_chown in the GNU C Library did not\n properly check permissions for tty files. A local attacker could use this\n to gain administrative privileges or expose sensitive information. \n (CVE-2013-2207, CVE-2016-2856)\n \n Robin Hack discovered that the Name Service Switch (NSS) implementation in\n the GNU C Library did not properly manage its file descriptors. \n (CVE-2014-8121)\n \n Joseph Myers discovered that the GNU C Library did not properly handle long\n arguments to functions returning a representation of Not a Number (NaN). \n (CVE-2014-9761)\n \n Arjun Shankar discovered that in certain situations the nss_dns code in the\n GNU C Library did not properly account buffer sizes when passed an\n unaligned buffer. (CVE-2015-1781)\n \n Sumit Bose and Lukas Slebodnik discovered that the Name Service\n Switch (NSS) implementation in the GNU C Library did not handle long\n lines in the files databases correctly. (CVE-2015-8776)\n \n Hector Marco and Ismael Ripoll discovered that the GNU C Library allowed\n the pointer-guarding protection mechanism to be disabled by honoring the\n LD_POINTER_GUARD environment variable across privilege boundaries. A local\n attacker could use this to exploit an existing vulnerability more easily. (CVE-2015-8778)\n \n Maksymilian Arciemowicz discovered a stack-based buffer overflow in the\n catopen function in the GNU C Library when handling long catalog names. (CVE-2015-8779)\n \n Florian Weimer discovered that the getnetbyname implementation in the GNU C\n Library did not properly handle long names passed as arguments. (CVE-2016-3075)\n\nUpdate instructions:\n\nThe problem can be corrected by updating your system to the following\npackage versions:\n\nUbuntu 15.10:\n  libc-bin                        2.21-0ubuntu4.3\n  libc6                           2.21-0ubuntu4.3\n  libc6-dev                       2.21-0ubuntu4.3\n\nUbuntu 14.04 LTS:\n  libc-bin                        2.19-0ubuntu6.9\n  libc6                           2.19-0ubuntu6.9\n  libc6-dev                       2.19-0ubuntu6.9\n\nUbuntu 12.04 LTS:\n  libc-bin                        2.15-0ubuntu10.15\n  libc6                           2.15-0ubuntu10.15\n  libc6-dev                       2.15-0ubuntu10.15\n\nAfter a standard system update you need to reboot your computer to\nmake all the necessary changes. \n\nPlease review the CVEs referenced below for additional vulnerabilities\nthat had already been fixed in previous versions of sys-libs/glibc, for\nwhich we have not issued a GLSA before. \n\nWorkaround\n==========\n\nA number of mitigating factors for CVE-2015-7547 have been identified. \nPlease review the upstream advisory and references below. \n\nResolution\n==========\n\nAll GNU C Library users should upgrade to the latest version:\n\n  # emerge --sync\n  # emerge --ask --oneshot --verbose \"\u003e=sys-libs/glibc-2.21-r2\"\n\nIt is important to ensure that no running process uses the old glibc\nanymore. The easiest way to achieve that is by rebooting the machine\nafter updating the sys-libs/glibc package. \n\nNote: Should you run into compilation failures while updating, please\nsee bug 574948. \n\nReferences\n==========\n\n[  1 ] CVE-2013-7423\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-7423\n[  2 ] CVE-2014-0475\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-0475\n[  3 ] CVE-2014-0475\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-0475\n[  4 ] CVE-2014-5119\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-5119\n[  5 ] CVE-2014-6040\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-6040\n[  6 ] CVE-2014-7817\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-7817\n[  7 ] CVE-2014-8121\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8121\n[  8 ] CVE-2014-9402\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-9402\n[  9 ] CVE-2015-1472\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1472\n[ 10 ] CVE-2015-1781\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-1781\n[ 11 ] CVE-2015-7547\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-7547\n[ 12 ] CVE-2015-8776\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8776\n[ 13 ] CVE-2015-8778\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8778\n[ 14 ] CVE-2015-8779\n       http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8779\n[ 15 ] Google Online Security Blog: \"CVE-2015-7547: glibc getaddrinfo\n       stack-based buffer overflow\"\n\nhttps://googleonlinesecurity.blogspot.de/2016/02/cve-2015-7547-glibc-geta=\nddrinfo-stack.html\n\nAvailability\n============\n\nThis GLSA and any updates to it are available for viewing at\nthe Gentoo Security Website:\n\n https://security.gentoo.org/glsa/201602-02\n\nConcerns?\n=========\n\nSecurity is a primary focus of Gentoo Linux and ensuring the\nconfidentiality and security of our users\u0027 machines is of utmost\nimportance to us. Any security concerns should be addressed to\nsecurity@gentoo.org or alternatively, you may file a bug at\nhttps://bugs.gentoo.org. \n\nLicense\n=======\n\nCopyright 2016 Gentoo Foundation, Inc; referenced text\nbelongs to its owner(s). \n\nThe contents of this document are licensed under the\nCreative Commons - Attribution / Share Alike license. \n\nhttp://creativecommons.org/licenses/by-sa/2.5\n",
    "sources": [
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "BID",
        "id": "74255"
      },
      {
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "db": "PACKETSTORM",
        "id": "137200"
      },
      {
        "db": "PACKETSTORM",
        "id": "131697"
      },
      {
        "db": "PACKETSTORM",
        "id": "134444"
      },
      {
        "db": "PACKETSTORM",
        "id": "135793"
      },
      {
        "db": "PACKETSTORM",
        "id": "131539"
      },
      {
        "db": "PACKETSTORM",
        "id": "137208"
      },
      {
        "db": "PACKETSTORM",
        "id": "135810"
      }
    ],
    "trust": 2.61
  },
  "external_ids": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/external_ids#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "db": "NVD",
        "id": "CVE-2015-1781",
        "trust": 3.5
      },
      {
        "db": "BID",
        "id": "74255",
        "trust": 2.0
      },
      {
        "db": "SECTRACK",
        "id": "1032178",
        "trust": 1.7
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995",
        "trust": 0.8
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071",
        "trust": 0.6
      },
      {
        "db": "VULMON",
        "id": "CVE-2015-1781",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "137200",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "131697",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "134444",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "135793",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "131539",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "137208",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "135810",
        "trust": 0.1
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "db": "BID",
        "id": "74255"
      },
      {
        "db": "PACKETSTORM",
        "id": "137200"
      },
      {
        "db": "PACKETSTORM",
        "id": "131697"
      },
      {
        "db": "PACKETSTORM",
        "id": "134444"
      },
      {
        "db": "PACKETSTORM",
        "id": "135793"
      },
      {
        "db": "PACKETSTORM",
        "id": "131539"
      },
      {
        "db": "PACKETSTORM",
        "id": "137208"
      },
      {
        "db": "PACKETSTORM",
        "id": "135810"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "id": "VAR-201509-0438",
  "iot": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/iot#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": true,
    "sources": [
      {
        "db": "VARIoT devices database",
        "id": null
      }
    ],
    "trust": 0.20833333
  },
  "last_update_date": "2025-12-22T22:36:48.237000Z",
  "patch": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/patch#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "title": "SUSE-SU-2015:1424",
        "trust": 0.8,
        "url": " http://lists.opensuse.org/opensuse-security-announce/2015-08/msg00019.html"
      },
      {
        "title": "RHSA-2015:0863",
        "trust": 0.8,
        "url": "https://rhn.redhat.com/errata/RHSA-2015-0863.html"
      },
      {
        "title": "Bug 18287",
        "trust": 0.8,
        "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=18287"
      },
      {
        "title": "The GNU C Library version 2.22 is now available",
        "trust": 0.8,
        "url": "https://www.sourceware.org/ml/libc-alpha/2015-08/msg00609.html"
      },
      {
        "title": "CVE-2015-1781: resolv/nss_dns/dns-host.c buffer overflow [BZ#18287]",
        "trust": 0.8,
        "url": "https://sourceware.org/git/?p=glibc.git;a=commit;h=2959eda9272a03386"
      },
      {
        "title": "GNU C Library Buffer error vulnerability fix",
        "trust": 0.6,
        "url": "http://123.124.177.30/web/xxk/bdxqById.tag?id=232528"
      },
      {
        "title": "Red Hat: Moderate: glibc security, bug fix, and enhancement update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20152199 - Security Advisory"
      },
      {
        "title": "Red Hat: Important: glibc security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20152589 - Security Advisory"
      },
      {
        "title": "Debian CVElist Bug Report Logs: CVE-2015-1781",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=a2c29453eb55cceece213eaabd30c31b"
      },
      {
        "title": "Debian CVElist Bug Report Logs: CVE-2013-2207: Remove pt_chown",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=24f036a1c9b3e11b009511a5ff0119fc"
      },
      {
        "title": "Debian CVElist Bug Report Logs: glibc: multiple overflows in strxfrm()",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=9c45e614f65364c9f36d20f68260e303"
      },
      {
        "title": "Debian CVElist Bug Report Logs: glibc: Three vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=c894c06b98aa71f44dddf17ba757bd22"
      },
      {
        "title": "Red Hat: CVE-2015-1781",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_cve_database\u0026qid=CVE-2015-1781"
      },
      {
        "title": "Debian CVElist Bug Report Logs: libc6: Pointer guarding bypass in dynamic Setuid binaries",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=fd388404d431df3846c2735a9f93c550"
      },
      {
        "title": "Amazon Linux AMI: ALAS-2015-513",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=amazon_linux_ami\u0026qid=ALAS-2015-513"
      },
      {
        "title": "Ubuntu Security Notice: eglibc, glibc regression",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-2985-2"
      },
      {
        "title": "Ubuntu Security Notice: eglibc, glibc vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-2985-1"
      },
      {
        "title": "Amazon Linux AMI: ALAS-2015-617",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=amazon_linux_ami\u0026qid=ALAS-2015-617"
      },
      {
        "title": "Oracle Linux Bulletins: Oracle Linux Bulletin - October 2015",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=oracle_linux_bulletins\u0026qid=435ed9abc2fb1e74ce2a69605a01e326"
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      }
    ]
  },
  "problemtype_data": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "problemtype": "CWE-119",
        "trust": 1.8
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "references": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/references#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "trust": 2.2,
        "url": "https://rhn.redhat.com/errata/rhsa-2015-0863.html"
      },
      {
        "trust": 2.0,
        "url": "http://www.oracle.com/technetwork/topics/security/linuxbulletinoct2015-2719645.html"
      },
      {
        "trust": 1.9,
        "url": "http://www.ubuntu.com/usn/usn-2985-1"
      },
      {
        "trust": 1.8,
        "url": "http://www.ubuntu.com/usn/usn-2985-2"
      },
      {
        "trust": 1.8,
        "url": "https://security.gentoo.org/glsa/201602-02"
      },
      {
        "trust": 1.7,
        "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=18287"
      },
      {
        "trust": 1.7,
        "url": "https://www.sourceware.org/ml/libc-alpha/2015-08/msg00609.html"
      },
      {
        "trust": 1.7,
        "url": "http://lists.opensuse.org/opensuse-security-announce/2015-08/msg00019.html"
      },
      {
        "trust": 1.7,
        "url": "http://www.securityfocus.com/bid/74255"
      },
      {
        "trust": 1.7,
        "url": "http://lists.opensuse.org/opensuse-security-announce/2016-02/msg00036.html"
      },
      {
        "trust": 1.7,
        "url": "http://www.securitytracker.com/id/1032178"
      },
      {
        "trust": 1.7,
        "url": "http://www.debian.org/security/2016/dsa-3480"
      },
      {
        "trust": 1.7,
        "url": "http://lists.fedoraproject.org/pipermail/package-announce/2016-february/177404.html"
      },
      {
        "trust": 1.6,
        "url": "https://sourceware.org/git/?p=glibc.git%3ba=commit%3bh=2959eda9272a03386"
      },
      {
        "trust": 0.9,
        "url": "https://access.redhat.com/security/cve/cve-2015-1781"
      },
      {
        "trust": 0.9,
        "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1199525"
      },
      {
        "trust": 0.9,
        "url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2015-1781"
      },
      {
        "trust": 0.8,
        "url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2015-1781"
      },
      {
        "trust": 0.7,
        "url": "https://access.redhat.com/errata/rhsa-2015:2199"
      },
      {
        "trust": 0.7,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-1781"
      },
      {
        "trust": 0.6,
        "url": "https://access.redhat.com/errata/rhsa-2015:2589"
      },
      {
        "trust": 0.6,
        "url": "https://access.redhat.com/errata/rhsa-2015:0863"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-8121"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8776"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8778"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8779"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2013-7423"
      },
      {
        "trust": 0.3,
        "url": "http://www.gnu.org/software/libc/"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21966788"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=isg3t1022665"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=isg3t1023385"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=ssg1s1005779"
      },
      {
        "trust": 0.3,
        "url": "https://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5099196"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=ssg1s1005255"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=nas8n1020837"
      },
      {
        "trust": 0.3,
        "url": "https://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5099225"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21966209"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21982433"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21988872"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8777"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-9761"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-5277"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-3075"
      },
      {
        "trust": 0.2,
        "url": "https://www.redhat.com/mailman/listinfo/rhsa-announce"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-1472"
      },
      {
        "trust": 0.2,
        "url": "https://bugzilla.redhat.com/):"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/team/key/"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/articles/11258"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/updates/classification/#moderate"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/team/contact/"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2013-7423"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-7547"
      },
      {
        "trust": 0.1,
        "url": "https://cwe.mitre.org/data/definitions/119.html"
      },
      {
        "trust": 0.1,
        "url": "https://sourceware.org/git/?p=glibc.git;a=commit;h=2959eda9272a03386"
      },
      {
        "trust": 0.1,
        "url": "http://tools.cisco.com/security/center/viewalert.x?alertid=38496"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov"
      },
      {
        "trust": 0.1,
        "url": "https://usn.ubuntu.com/2985-2/"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.14"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-2856"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.21-0ubuntu4.2"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.8"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2013-2207"
      },
      {
        "trust": 0.1,
        "url": "http://www.mandriva.com/en/support/security/"
      },
      {
        "trust": 0.1,
        "url": "http://www.mandriva.com/en/support/security/advisories/"
      },
      {
        "trust": 0.1,
        "url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2013-7423"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-1473"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2015-1473"
      },
      {
        "trust": 0.1,
        "url": "https://rhn.redhat.com/errata/rhsa-2015-2199.html"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2015-1472"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/articles/2050743"
      },
      {
        "trust": 0.1,
        "url": "https://www.debian.org/security/faq"
      },
      {
        "trust": 0.1,
        "url": "https://www.debian.org/security/"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/bugs/1585614"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.21-0ubuntu4.3"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.9"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.15"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2014-9402"
      },
      {
        "trust": 0.1,
        "url": "https://security.gentoo.org/"
      },
      {
        "trust": 0.1,
        "url": "https://googleonlinesecurity.blogspot.de/2016/02/cve-2015-7547-glibc-geta="
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-7817"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-9402"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2015-7547"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2014-8121"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2015-1781"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-6040"
      },
      {
        "trust": 0.1,
        "url": "http://creativecommons.org/licenses/by-sa/2.5"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2015-8778"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2014-0475"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2015-8776"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2014-7817"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-5119"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2014-6040"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2015-8779"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2013-7423"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2014-5119"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-0475"
      },
      {
        "trust": 0.1,
        "url": "http://nvd.nist.gov/nvd.cfm?cvename=cve-2015-1472"
      },
      {
        "trust": 0.1,
        "url": "https://bugs.gentoo.org."
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "db": "BID",
        "id": "74255"
      },
      {
        "db": "PACKETSTORM",
        "id": "137200"
      },
      {
        "db": "PACKETSTORM",
        "id": "131697"
      },
      {
        "db": "PACKETSTORM",
        "id": "134444"
      },
      {
        "db": "PACKETSTORM",
        "id": "135793"
      },
      {
        "db": "PACKETSTORM",
        "id": "131539"
      },
      {
        "db": "PACKETSTORM",
        "id": "137208"
      },
      {
        "db": "PACKETSTORM",
        "id": "135810"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "sources": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "db": "BID",
        "id": "74255"
      },
      {
        "db": "PACKETSTORM",
        "id": "137200"
      },
      {
        "db": "PACKETSTORM",
        "id": "131697"
      },
      {
        "db": "PACKETSTORM",
        "id": "134444"
      },
      {
        "db": "PACKETSTORM",
        "id": "135793"
      },
      {
        "db": "PACKETSTORM",
        "id": "131539"
      },
      {
        "db": "PACKETSTORM",
        "id": "137208"
      },
      {
        "db": "PACKETSTORM",
        "id": "135810"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "sources_release_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2015-09-28T00:00:00",
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "date": "2015-04-21T00:00:00",
        "db": "BID",
        "id": "74255"
      },
      {
        "date": "2015-05-26T08:22:22",
        "db": "PACKETSTORM",
        "id": "137200"
      },
      {
        "date": "2015-04-30T15:46:57",
        "db": "PACKETSTORM",
        "id": "131697"
      },
      {
        "date": "2015-11-20T00:41:22",
        "db": "PACKETSTORM",
        "id": "134444"
      },
      {
        "date": "2016-02-16T17:18:17",
        "db": "PACKETSTORM",
        "id": "135793"
      },
      {
        "date": "2015-04-21T16:03:31",
        "db": "PACKETSTORM",
        "id": "131539"
      },
      {
        "date": "2016-05-26T14:33:33",
        "db": "PACKETSTORM",
        "id": "137208"
      },
      {
        "date": "2016-02-17T23:53:39",
        "db": "PACKETSTORM",
        "id": "135810"
      },
      {
        "date": "2015-04-21T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "date": "2015-10-01T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "date": "2015-09-28T20:59:00.093000",
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "sources_update_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2019-06-17T00:00:00",
        "db": "VULMON",
        "id": "CVE-2015-1781"
      },
      {
        "date": "2016-09-09T18:00:00",
        "db": "BID",
        "id": "74255"
      },
      {
        "date": "2023-04-10T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      },
      {
        "date": "2015-10-01T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      },
      {
        "date": "2025-04-12T10:46:40.837000",
        "db": "NVD",
        "id": "CVE-2015-1781"
      }
    ]
  },
  "threat_type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/threat_type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "remote",
    "sources": [
      {
        "db": "PACKETSTORM",
        "id": "135810"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      }
    ],
    "trust": 0.7
  },
  "title": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/title#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "GNU C Library of  gethostbyname_r And other unspecified  NSS Buffer overflow vulnerability in functions",
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2015-004995"
      }
    ],
    "trust": 0.8
  },
  "type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "buffer error",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-201505-071"
      }
    ],
    "trust": 0.6
  }
}

{
  "@context": {
    "@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
    "affected_products": {
      "@id": "https://www.variotdbs.pl/ref/affected_products"
    },
    "configurations": {
      "@id": "https://www.variotdbs.pl/ref/configurations"
    },
    "credits": {
      "@id": "https://www.variotdbs.pl/ref/credits"
    },
    "cvss": {
      "@id": "https://www.variotdbs.pl/ref/cvss/"
    },
    "description": {
      "@id": "https://www.variotdbs.pl/ref/description/"
    },
    "exploit_availability": {
      "@id": "https://www.variotdbs.pl/ref/exploit_availability/"
    },
    "external_ids": {
      "@id": "https://www.variotdbs.pl/ref/external_ids/"
    },
    "iot": {
      "@id": "https://www.variotdbs.pl/ref/iot/"
    },
    "iot_taxonomy": {
      "@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
    },
    "patch": {
      "@id": "https://www.variotdbs.pl/ref/patch/"
    },
    "problemtype_data": {
      "@id": "https://www.variotdbs.pl/ref/problemtype_data/"
    },
    "references": {
      "@id": "https://www.variotdbs.pl/ref/references/"
    },
    "sources": {
      "@id": "https://www.variotdbs.pl/ref/sources/"
    },
    "sources_release_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_release_date/"
    },
    "sources_update_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_update_date/"
    },
    "threat_type": {
      "@id": "https://www.variotdbs.pl/ref/threat_type/"
    },
    "title": {
      "@id": "https://www.variotdbs.pl/ref/title/"
    },
    "type": {
      "@id": "https://www.variotdbs.pl/ref/type/"
    }
  },
  "@id": "https://www.variotdbs.pl/vuln/VAR-202101-0119",
  "affected_products": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/affected_products#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "model": "fedora",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "fedoraproject",
        "version": "32"
      },
      {
        "model": "fedora",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "fedoraproject",
        "version": "33"
      },
      {
        "model": "ontap select deploy administration utility",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "service processor",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "500f",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "debian",
        "version": "10.0"
      },
      {
        "model": "a250",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "fabric operating system",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "broadcom",
        "version": null
      },
      {
        "model": "glibc",
        "scope": "lte",
        "trust": 1.0,
        "vendor": "gnu",
        "version": "2.32"
      },
      {
        "model": "fas/aff baseboard management controller 500f",
        "scope": null,
        "trust": 0.8,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "c library",
        "scope": null,
        "trust": 0.8,
        "vendor": "gnu",
        "version": null
      },
      {
        "model": "fedora",
        "scope": null,
        "trust": 0.8,
        "vendor": "fedora",
        "version": null
      },
      {
        "model": "service processor",
        "scope": null,
        "trust": 0.8,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "fabric operating system",
        "scope": null,
        "trust": 0.8,
        "vendor": "broadcom",
        "version": null
      },
      {
        "model": "ontap select deploy administration utility",
        "scope": null,
        "trust": 0.8,
        "vendor": "netapp",
        "version": null
      },
      {
        "model": "fas/aff baseboard management controller a250",
        "scope": null,
        "trust": 0.8,
        "vendor": "netapp",
        "version": null
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "credits": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/credits#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "Red Hat",
    "sources": [
      {
        "db": "PACKETSTORM",
        "id": "162634"
      },
      {
        "db": "PACKETSTORM",
        "id": "162837"
      },
      {
        "db": "PACKETSTORM",
        "id": "163267"
      },
      {
        "db": "PACKETSTORM",
        "id": "163496"
      },
      {
        "db": "PACKETSTORM",
        "id": "161254"
      },
      {
        "db": "PACKETSTORM",
        "id": "166279"
      },
      {
        "db": "PACKETSTORM",
        "id": "164192"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      }
    ],
    "trust": 1.3
  },
  "cve": "CVE-2019-25013",
  "cvss": {
    "@context": {
      "cvssV2": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
      },
      "cvssV3": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
      },
      "severity": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/cvss/severity#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/severity"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "cvssV2": [
          {
            "accessComplexity": "MEDIUM",
            "accessVector": "NETWORK",
            "authentication": "NONE",
            "author": "nvd@nist.gov",
            "availabilityImpact": "COMPLETE",
            "baseScore": 7.1,
            "confidentialityImpact": "NONE",
            "exploitabilityScore": 8.6,
            "id": "CVE-2019-25013",
            "impactScore": 6.9,
            "integrityImpact": "NONE",
            "severity": "HIGH",
            "trust": 1.9,
            "vectorString": "AV:N/AC:M/Au:N/C:N/I:N/A:C",
            "version": "2.0"
          }
        ],
        "cvssV3": [
          {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "author": "nvd@nist.gov",
            "availabilityImpact": "HIGH",
            "baseScore": 5.9,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "exploitabilityScore": 2.2,
            "id": "CVE-2019-25013",
            "impactScore": 3.6,
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "trust": 2.0,
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          {
            "attackComplexity": "High",
            "attackVector": "Network",
            "author": "NVD",
            "availabilityImpact": "High",
            "baseScore": 5.9,
            "baseSeverity": "Medium",
            "confidentialityImpact": "None",
            "exploitabilityScore": null,
            "id": "CVE-2019-25013",
            "impactScore": null,
            "integrityImpact": "None",
            "privilegesRequired": "None",
            "scope": "Unchanged",
            "trust": 0.8,
            "userInteraction": "None",
            "vectorString": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.0"
          }
        ],
        "severity": [
          {
            "author": "nvd@nist.gov",
            "id": "CVE-2019-25013",
            "trust": 1.0,
            "value": "MEDIUM"
          },
          {
            "author": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            "id": "CVE-2019-25013",
            "trust": 1.0,
            "value": "MEDIUM"
          },
          {
            "author": "NVD",
            "id": "CVE-2019-25013",
            "trust": 0.8,
            "value": "Medium"
          },
          {
            "author": "CNNVD",
            "id": "CNNVD-202101-048",
            "trust": 0.6,
            "value": "MEDIUM"
          },
          {
            "author": "VULMON",
            "id": "CVE-2019-25013",
            "trust": 0.1,
            "value": "HIGH"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "description": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/description#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read. 8) - aarch64, ppc64le, s390x, x86_64\n\n3. \n\nAdditional Changes:\n\nFor detailed information on changes in this release, see the Red Hat\nEnterprise Linux 8.4 Release Notes linked from the References section. Bugs fixed (https://bugzilla.redhat.com/):\n\n1428290 - CVE-2016-10228 glibc: iconv program can hang when invoked with the -c option\n1684057 - CVE-2019-9169 glibc: regular-expression match via proceed_next_node in posix/regexec.c leads to heap-based buffer over-read\n1704868 - CVE-2016-10228 glibc: iconv: Fix converter hangs and front end option parsing for //TRANSLIT and //IGNORE [rhel-8]\n1855790 - glibc: Update Intel CET support from upstream\n1856398 - glibc: Build with -moutline-atomics on aarch64\n1868106 - glibc: Transaction ID collisions cause slow DNS lookups in getaddrinfo\n1871385 - glibc: Improve auditing implementation (including DT_AUDIT, and DT_DEPAUDIT)\n1871387 - glibc: Improve IBM POWER9 architecture performance\n1871394 - glibc: Fix AVX2 off-by-one error in strncmp (swbz#25933)\n1871395 - glibc: Improve IBM Z (s390x) Performance\n1871396 - glibc: Improve use of static TLS surplus for optimizations. Bugs fixed (https://bugzilla.redhat.com/):\n\n1921650 - CVE-2021-3121 gogo/protobuf: plugin/unmarshal/unmarshal.go lacks certain index validation\n\n5. Bugs fixed (https://bugzilla.redhat.com/):\n\n1897635 - CVE-2020-28362 golang: math/big: panic during recursive division of very large numbers\n1918750 - CVE-2021-3114 golang: crypto/elliptic: incorrect operations on the P-224 curve\n\n5. JIRA issues fixed (https://issues.jboss.org/):\n\nTRACING-1725 -  Elasticsearch operator reports x509 errors communicating with ElasticSearch in OpenShift Service Mesh project\n\n6. Relevant releases/architectures:\n\nRed Hat Enterprise Linux Client (v. 7) - x86_64\nRed Hat Enterprise Linux Client Optional (v. 7) - x86_64\nRed Hat Enterprise Linux ComputeNode Optional (v. 7) - x86_64\nRed Hat Enterprise Linux Server (v. 7) - ppc64, ppc64le, s390x, x86_64\nRed Hat Enterprise Linux Server Optional (v. 7) - ppc64, ppc64le, s390x, x86_64\nRed Hat Enterprise Linux Workstation (v. 7) - x86_64\nRed Hat Enterprise Linux Workstation Optional (v. 7) - x86_64\n\n3. Description:\n\nThe glibc packages provide the standard C libraries (libc), POSIX thread\nlibraries (libpthread), standard math libraries (libm), and the name\nservice cache daemon (nscd) used by multiple programs on the system. \nWithout these libraries, the Linux system cannot function correctly. \n\nBug Fix(es):\n\n* glibc: 64bit_strstr_via_64bit_strstr_sse2_unaligned detection fails with\nlarge device and inode numbers (BZ#1883162)\n\n* glibc: Performance regression in ebizzy benchmark (BZ#1889977)\n\n4. Solution:\n\nFor details on how to apply this update, which includes the changes\ndescribed in this advisory, refer to:\n\nhttps://access.redhat.com/articles/11258\n\nFor the update to take effect, all services linked to the glibc library\nmust be restarted, or the system rebooted. Package List:\n\nRed Hat Enterprise Linux Client (v. 7):\n\nSource:\nglibc-2.17-322.el7_9.src.rpm\n\nx86_64:\nglibc-2.17-322.el7_9.i686.rpm\nglibc-2.17-322.el7_9.x86_64.rpm\nglibc-common-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-common-2.17-322.el7_9.x86_64.rpm\nglibc-devel-2.17-322.el7_9.i686.rpm\nglibc-devel-2.17-322.el7_9.x86_64.rpm\nglibc-headers-2.17-322.el7_9.x86_64.rpm\nglibc-utils-2.17-322.el7_9.x86_64.rpm\nnscd-2.17-322.el7_9.x86_64.rpm\n\nRed Hat Enterprise Linux Client Optional (v. 7):\n\nSource:\nglibc-2.17-322.el7_9.src.rpm\n\nx86_64:\nglibc-2.17-322.el7_9.i686.rpm\nglibc-2.17-322.el7_9.x86_64.rpm\nglibc-common-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-common-2.17-322.el7_9.x86_64.rpm\nglibc-devel-2.17-322.el7_9.i686.rpm\nglibc-devel-2.17-322.el7_9.x86_64.rpm\nglibc-headers-2.17-322.el7_9.x86_64.rpm\nglibc-utils-2.17-322.el7_9.x86_64.rpm\nnscd-2.17-322.el7_9.x86_64.rpm\n\nRed Hat Enterprise Linux ComputeNode Optional (v. 7):\n\nx86_64:\nglibc-debuginfo-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-common-2.17-322.el7_9.x86_64.rpm\nglibc-static-2.17-322.el7_9.i686.rpm\nglibc-static-2.17-322.el7_9.x86_64.rpm\n\nRed Hat Enterprise Linux Server (v. 7):\n\nSource:\nglibc-2.17-322.el7_9.src.rpm\n\nppc64:\nglibc-2.17-322.el7_9.ppc.rpm\nglibc-2.17-322.el7_9.ppc64.rpm\nglibc-common-2.17-322.el7_9.ppc64.rpm\nglibc-debuginfo-2.17-322.el7_9.ppc.rpm\nglibc-debuginfo-2.17-322.el7_9.ppc64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.ppc.rpm\nglibc-debuginfo-common-2.17-322.el7_9.ppc64.rpm\nglibc-devel-2.17-322.el7_9.ppc.rpm\nglibc-devel-2.17-322.el7_9.ppc64.rpm\nglibc-headers-2.17-322.el7_9.ppc64.rpm\nglibc-utils-2.17-322.el7_9.ppc64.rpm\nnscd-2.17-322.el7_9.ppc64.rpm\n\nppc64le:\nglibc-2.17-322.el7_9.ppc64le.rpm\nglibc-common-2.17-322.el7_9.ppc64le.rpm\nglibc-debuginfo-2.17-322.el7_9.ppc64le.rpm\nglibc-debuginfo-common-2.17-322.el7_9.ppc64le.rpm\nglibc-devel-2.17-322.el7_9.ppc64le.rpm\nglibc-headers-2.17-322.el7_9.ppc64le.rpm\nglibc-utils-2.17-322.el7_9.ppc64le.rpm\nnscd-2.17-322.el7_9.ppc64le.rpm\n\ns390x:\nglibc-2.17-322.el7_9.s390.rpm\nglibc-2.17-322.el7_9.s390x.rpm\nglibc-common-2.17-322.el7_9.s390x.rpm\nglibc-debuginfo-2.17-322.el7_9.s390.rpm\nglibc-debuginfo-2.17-322.el7_9.s390x.rpm\nglibc-debuginfo-common-2.17-322.el7_9.s390.rpm\nglibc-debuginfo-common-2.17-322.el7_9.s390x.rpm\nglibc-devel-2.17-322.el7_9.s390.rpm\nglibc-devel-2.17-322.el7_9.s390x.rpm\nglibc-headers-2.17-322.el7_9.s390x.rpm\nglibc-utils-2.17-322.el7_9.s390x.rpm\nnscd-2.17-322.el7_9.s390x.rpm\n\nx86_64:\nglibc-2.17-322.el7_9.i686.rpm\nglibc-2.17-322.el7_9.x86_64.rpm\nglibc-common-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-common-2.17-322.el7_9.x86_64.rpm\nglibc-devel-2.17-322.el7_9.i686.rpm\nglibc-devel-2.17-322.el7_9.x86_64.rpm\nglibc-headers-2.17-322.el7_9.x86_64.rpm\nglibc-utils-2.17-322.el7_9.x86_64.rpm\nnscd-2.17-322.el7_9.x86_64.rpm\n\nRed Hat Enterprise Linux Server Optional (v. 7):\n\nppc64:\nglibc-debuginfo-2.17-322.el7_9.ppc.rpm\nglibc-debuginfo-2.17-322.el7_9.ppc64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.ppc.rpm\nglibc-debuginfo-common-2.17-322.el7_9.ppc64.rpm\nglibc-static-2.17-322.el7_9.ppc.rpm\nglibc-static-2.17-322.el7_9.ppc64.rpm\n\nppc64le:\nglibc-debuginfo-2.17-322.el7_9.ppc64le.rpm\nglibc-debuginfo-common-2.17-322.el7_9.ppc64le.rpm\nglibc-static-2.17-322.el7_9.ppc64le.rpm\n\ns390x:\nglibc-debuginfo-2.17-322.el7_9.s390.rpm\nglibc-debuginfo-2.17-322.el7_9.s390x.rpm\nglibc-debuginfo-common-2.17-322.el7_9.s390.rpm\nglibc-debuginfo-common-2.17-322.el7_9.s390x.rpm\nglibc-static-2.17-322.el7_9.s390.rpm\nglibc-static-2.17-322.el7_9.s390x.rpm\n\nx86_64:\nglibc-debuginfo-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-common-2.17-322.el7_9.x86_64.rpm\nglibc-static-2.17-322.el7_9.i686.rpm\nglibc-static-2.17-322.el7_9.x86_64.rpm\n\nRed Hat Enterprise Linux Workstation (v. 7):\n\nSource:\nglibc-2.17-322.el7_9.src.rpm\n\nx86_64:\nglibc-2.17-322.el7_9.i686.rpm\nglibc-2.17-322.el7_9.x86_64.rpm\nglibc-common-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-2.17-322.el7_9.x86_64.rpm\nglibc-debuginfo-common-2.17-322.el7_9.i686.rpm\nglibc-debuginfo-common-2.17-322.el7_9.x86_64.rpm\nglibc-devel-2.17-322.el7_9.i686.rpm\nglibc-devel-2.17-322.el7_9.x86_64.rpm\nglibc-headers-2.17-322.el7_9.x86_64.rpm\nglibc-utils-2.17-322.el7_9.x86_64.rpm\nnscd-2.17-322.el7_9.x86_64.rpm\n\nRed Hat Enterprise Linux Workstation Optional (v.  Our key and\ndetails on how to verify the signature are available from\nhttps://access.redhat.com/security/team/key/\n\n7. -----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\n=====================================================================\n                   Red Hat Security Advisory\n\nSynopsis:          Moderate: OpenShift Container Platform 4.10.3 security update\nAdvisory ID:       RHSA-2022:0056-01\nProduct:           Red Hat OpenShift Enterprise\nAdvisory URL:      https://access.redhat.com/errata/RHSA-2022:0056\nIssue date:        2022-03-10\nCVE Names:         CVE-2014-3577 CVE-2016-10228 CVE-2017-14502 \n                   CVE-2018-20843 CVE-2018-1000858 CVE-2019-8625 \n                   CVE-2019-8710 CVE-2019-8720 CVE-2019-8743 \n                   CVE-2019-8764 CVE-2019-8766 CVE-2019-8769 \n                   CVE-2019-8771 CVE-2019-8782 CVE-2019-8783 \n                   CVE-2019-8808 CVE-2019-8811 CVE-2019-8812 \n                   CVE-2019-8813 CVE-2019-8814 CVE-2019-8815 \n                   CVE-2019-8816 CVE-2019-8819 CVE-2019-8820 \n                   CVE-2019-8823 CVE-2019-8835 CVE-2019-8844 \n                   CVE-2019-8846 CVE-2019-9169 CVE-2019-13050 \n                   CVE-2019-13627 CVE-2019-14889 CVE-2019-15903 \n                   CVE-2019-19906 CVE-2019-20454 CVE-2019-20807 \n                   CVE-2019-25013 CVE-2020-1730 CVE-2020-3862 \n                   CVE-2020-3864 CVE-2020-3865 CVE-2020-3867 \n                   CVE-2020-3868 CVE-2020-3885 CVE-2020-3894 \n                   CVE-2020-3895 CVE-2020-3897 CVE-2020-3899 \n                   CVE-2020-3900 CVE-2020-3901 CVE-2020-3902 \n                   CVE-2020-8927 CVE-2020-9802 CVE-2020-9803 \n                   CVE-2020-9805 CVE-2020-9806 CVE-2020-9807 \n                   CVE-2020-9843 CVE-2020-9850 CVE-2020-9862 \n                   CVE-2020-9893 CVE-2020-9894 CVE-2020-9895 \n                   CVE-2020-9915 CVE-2020-9925 CVE-2020-9952 \n                   CVE-2020-10018 CVE-2020-11793 CVE-2020-13434 \n                   CVE-2020-14391 CVE-2020-15358 CVE-2020-15503 \n                   CVE-2020-25660 CVE-2020-25677 CVE-2020-27618 \n                   CVE-2020-27781 CVE-2020-29361 CVE-2020-29362 \n                   CVE-2020-29363 CVE-2021-3121 CVE-2021-3326 \n                   CVE-2021-3449 CVE-2021-3450 CVE-2021-3516 \n                   CVE-2021-3517 CVE-2021-3518 CVE-2021-3520 \n                   CVE-2021-3521 CVE-2021-3537 CVE-2021-3541 \n                   CVE-2021-3733 CVE-2021-3749 CVE-2021-20305 \n                   CVE-2021-21684 CVE-2021-22946 CVE-2021-22947 \n                   CVE-2021-25215 CVE-2021-27218 CVE-2021-30666 \n                   CVE-2021-30761 CVE-2021-30762 CVE-2021-33928 \n                   CVE-2021-33929 CVE-2021-33930 CVE-2021-33938 \n                   CVE-2021-36222 CVE-2021-37750 CVE-2021-39226 \n                   CVE-2021-41190 CVE-2021-43813 CVE-2021-44716 \n                   CVE-2021-44717 CVE-2022-0532 CVE-2022-21673 \n                   CVE-2022-24407 \n=====================================================================\n\n1. Summary:\n\nRed Hat OpenShift Container Platform release 4.10.3 is now available with\nupdates to packages and images that fix several bugs and add enhancements. \n\nRed Hat Product Security has rated this update as having a security impact\nof Moderate. A Common Vulnerability Scoring System (CVSS) base score, which\ngives a detailed severity rating, is available for each vulnerability from\nthe CVE link(s) in the References section. \n\n2. Description:\n\nRed Hat OpenShift Container Platform is Red Hat\u0027s cloud computing\nKubernetes application platform solution designed for on-premise or private\ncloud deployments. \n\nThis advisory contains the container images for Red Hat OpenShift Container\nPlatform 4.10.3. See the following advisory for the RPM packages for this\nrelease:\n\nhttps://access.redhat.com/errata/RHSA-2022:0055\n\nSpace precludes documenting all of the container images in this advisory. \nSee the following Release Notes documentation, which will be updated\nshortly for this release, for details about these changes:\n\nhttps://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html\n\nSecurity Fix(es):\n\n* gogo/protobuf: plugin/unmarshal/unmarshal.go lacks certain index\nvalidation (CVE-2021-3121)\n* grafana: Snapshot authentication bypass (CVE-2021-39226)\n* golang: net/http: limit growth of header canonicalization cache\n(CVE-2021-44716)\n* nodejs-axios: Regular expression denial of service in trim function\n(CVE-2021-3749)\n* golang: syscall: don\u0027t close fd 0 on ForkExec error (CVE-2021-44717)\n* grafana: Forward OAuth Identity Token can allow users to access some data\nsources (CVE-2022-21673)\n* grafana: directory traversal vulnerability (CVE-2021-43813)\n\nFor more details about the security issue(s), including the impact, a CVSS\nscore, acknowledgments, and other related information, refer to the CVE\npage(s) listed in the References section. \n\nYou may download the oc tool and use it to inspect release image metadata\nas follows:\n\n(For x86_64 architecture)\n\n$ oc adm release info\nquay.io/openshift-release-dev/ocp-release:4.10.3-x86_64\n\nThe image digest is\nsha256:7ffe4cd612be27e355a640e5eec5cd8f923c1400d969fd590f806cffdaabcc56\n\n(For s390x architecture)\n\n  $ oc adm release info\nquay.io/openshift-release-dev/ocp-release:4.10.3-s390x\n\nThe image digest is\nsha256:4cf21a9399da1ce8427246f251ae5dedacfc8c746d2345f9cfe039ed9eda3e69\n\n(For ppc64le architecture)\n\n  $ oc adm release info\nquay.io/openshift-release-dev/ocp-release:4.10.3-ppc64le\n\nThe image digest is\nsha256:4ee571da1edf59dfee4473aa4604aba63c224bf8e6bcf57d048305babbbde93c\n\nAll OpenShift Container Platform 4.10 users are advised to upgrade to these\nupdated packages and images when they are available in the appropriate\nrelease channel. To check for available updates, use the OpenShift Console\nor the CLI oc command. Instructions for upgrading a cluster are available\nat\nhttps://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html\n\n3. Solution:\n\nFor OpenShift Container Platform 4.10 see the following documentation,\nwhich will be updated shortly for this release, for moderate instructions\non how to upgrade your cluster and fully apply this asynchronous errata\nupdate:\n\nhttps://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html\n\nDetails on how to access this content are available at\nhttps://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html\n\n4. Bugs fixed (https://bugzilla.redhat.com/):\n\n1808240 - Always return metrics value for pods under the user\u0027s namespace\n1815189 - feature flagged UI does not always become available after operator installation\n1825034 - e2e: Mock CSI tests fail on IBM ROKS clusters\n1826225 - edge terminated h2 (gRPC) connections need a haproxy template change to work correctly\n1860774 - csr for vSphere egress nodes were not approved automatically during cert renewal\n1878106 - token inactivity timeout is not shortened after oauthclient/oauth config values are lowered\n1878925 - \u0027oc adm upgrade --to ...\u0027 rejects versions which occur only in history, while the cluster-version operator supports history fallback\n1880738 - origin e2e test deletes original worker\n1882983 - oVirt csi driver should refuse to provision RWX and ROX PV\n1886450 - Keepalived router id check not documented for RHV/VMware IPI\n1889488 - The metrics endpoint for the Scheduler is not protected by RBAC\n1894431 - Router pods fail to boot if the SSL certificate applied is missing an empty line at the bottom\n1896474 - Path based routing is broken for some combinations\n1897431 - CIDR support for  additional network attachment with the bridge CNI plug-in\n1903408 - NodePort externalTrafficPolicy does not work for ovn-kubernetes\n1907433 - Excessive logging in image operator\n1909906 - The router fails with PANIC error when stats port already in use\n1911173 - [MSTR-998] Many charts\u0027 legend names show {{}} instead of words\n1914053 - pods assigned with Multus whereabouts IP get stuck in ContainerCreating state after node rebooting. \n1916169 - a reboot while MCO is applying changes leaves the node in undesirable state and MCP looks fine (UPDATED=true)\n1917893 - [ovirt] install fails: due to terraform error \"Cannot attach Virtual Disk: Disk is locked\" on vm resource\n1921627 - GCP UPI installation failed due to exceeding gcp limitation of instance group name\n1921650 - CVE-2021-3121 gogo/protobuf: plugin/unmarshal/unmarshal.go lacks certain index validation\n1926522 - oc adm catalog does not clean temporary files\n1927478 - Default CatalogSources deployed by marketplace do not have toleration for tainted nodes. \n1928141 - kube-storage-version-migrator constantly reporting type \"Upgradeable\" status Unknown\n1928285 - [LSO][OCS][arbiter] OCP Console shows no results while in fact underlying setup of LSO localvolumeset and it\u0027s storageclass is not yet finished, confusing users\n1931594 - [sig-cli] oc --request-timeout works as expected fails frequently on s390x\n1933847 - Prometheus goes unavailable (both instances down) during 4.8 upgrade\n1937085 - RHV UPI inventory playbook missing guarantee_memory\n1937196 - [aws ebs csi driver] events for block volume expansion may cause confusion\n1938236 - vsphere-problem-detector does not support overriding log levels via storage CR\n1939401 - missed labels for CMO/openshift-state-metric/telemeter-client/thanos-querier pods\n1939435 - Setting an IPv6 address in noProxy field causes error in openshift installer\n1939552 - [sig-api-machinery] CustomResourcePublishOpenAPI [Privileged:ClusterAdmin] works for CRD preserving unknown fields in an embedded object [Conformance] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s]\n1942913 - ThanosSidecarUnhealthy isn\u0027t resilient to WAL replays. \n1943363 - [ovn] CNO should gracefully terminate ovn-northd\n1945274 - ostree-finalize-staged.service failed while upgrading a rhcos node to 4.6.17\n1948080 - authentication should not set Available=False APIServices_Error with 503s\n1949262 - Prometheus Statefulsets should have 2 replicas and hard affinity set\n1949672 - [GCP] Update 4.8 UPI template to match ignition version: 3.2.0\n1950827 - [LSO] localvolumediscoveryresult name is not friendly to customer\n1952576 - csv_succeeded metric not present in olm-operator for all successful CSVs\n1953264 - \"remote error: tls: bad certificate\" logs in prometheus-operator container\n1955300 - Machine config operator reports unavailable for 23m during upgrade\n1955489 - Alertmanager Statefulsets should have 2 replicas and hard affinity set\n1955490 - Thanos ruler Statefulsets should have 2 replicas and hard affinity set\n1955544 - [IPI][OSP] densed master-only installation with 0 workers fails due to missing worker security group on masters\n1956496 - Needs SR-IOV Docs Upstream\n1956739 - Permission for authorized_keys for core user changes from core user to root when changed the pull secret\n1956776 - [vSphere] Installer should do pre-check to ensure user-provided network name is valid\n1956964 - upload a boot-source to OpenShift virtualization using the console\n1957547 - [RFE]VM name is not auto filled in dev console\n1958349 - ovn-controller doesn\u0027t release the memory after cluster-density run\n1959352 - [scale] failed to get pod annotation: timed out waiting for annotations\n1960378 - icsp allows mirroring of registry root - install-config imageContentSources does not\n1960674 - Broken test: [sig-imageregistry][Serial][Suite:openshift/registry/serial] Image signature workflow can push a signed image to openshift registry and verify it [Suite:openshift/conformance/serial]\n1961317 - storage ClusterOperator does not declare ClusterRoleBindings in relatedObjects\n1961391 - String updates\n1961509 - DHCP daemon pod should have CPU and memory requests set but not limits\n1962066 - Edit machine/machineset specs not working\n1962206 - openshift-multus/dhcp-daemon set should meet platform requirements for update strategy that have maxUnavailable update of 10 or 33 percent\n1963053 - `oc whoami --show-console` should show the web console URL, not the server api URL\n1964112 - route SimpleAllocationPlugin: host name validation errors: spec.host: Invalid value: ... must be no more than 63 characters\n1964327 - Support containers with name:tag@digest\n1964789 - Send keys and disconnect does not work for VNC console\n1965368 - ClusterQuotaAdmission received non-meta object - message constantly reported in OpenShift Container Platform 4.7\n1966445 - Unmasking a service doesn\u0027t work if it masked using MCO\n1966477 - Use GA version in KAS/OAS/OauthAS to avoid: \"audit.k8s.io/v1beta1\" is deprecated and will be removed in a future release, use \"audit.k8s.io/v1\" instead\n1966521 - kube-proxy\u0027s userspace implementation consumes excessive CPU\n1968364 - [Azure] when using ssh type ed25519 bootstrap fails to come up\n1970021 - nmstate does not persist its configuration due to overlay systemd-connections-merged mount\n1970218 - MCO writes incorrect file contents if compression field is specified\n1970331 - [sig-auth][Feature:SCC][Early] should not have pod creation failures during install [Suite:openshift/conformance/parallel]\n1970805 - Cannot create build when docker image url contains dir structure\n1972033 - [azure] PV region node affinity is failure-domain.beta.kubernetes.io instead of topology.kubernetes.io\n1972827 - image registry does not remain available during upgrade\n1972962 - Should set the minimum value for the `--max-icsp-size` flag of `oc adm catalog mirror`\n1973447 - ovn-dbchecker peak memory spikes to ~500MiB during cluster-density run\n1975826 - ovn-kubernetes host directed traffic cannot be offloaded as CT zone 64000 is not established\n1976301 - [ci] e2e-azure-upi is permafailing\n1976399 - During the upgrade from OpenShift 4.5 to OpenShift 4.6 the election timers for the OVN north and south databases did not change. \n1976674 - CCO didn\u0027t set Upgradeable to False when cco mode is configured to Manual on azure platform\n1976894 - Unidling a StatefulSet does not work as expected\n1977319 - [Hive] Remove stale cruft installed by CVO in earlier releases\n1977414 - Build Config timed out waiting for condition 400: Bad Request\n1977929 - [RFE] Display Network Attachment Definitions from openshift-multus namespace during OCS deployment via UI using Multus\n1978528 - systemd-coredump started and failed intermittently for unknown reasons\n1978581 - machine-config-operator: remove runlevel from mco namespace\n1979562 - Cluster operators: don\u0027t show messages when neither progressing, degraded or unavailable\n1979962 - AWS SDN Network Stress tests have not passed in 4.9 release-openshift-origin-installer-e2e-aws-sdn-network-stress-4.9\n1979966 - OCP builds always fail when run on RHEL7 nodes\n1981396 - Deleting pool inside pool page the pool stays in Ready phase in the heading\n1981549 - Machine-config daemon does not recover from broken Proxy configuration\n1981867 - [sig-cli] oc explain should contain proper fields description for special types [Suite:openshift/conformance/parallel]\n1981941 - Terraform upgrade required in openshift-installer to resolve multiple issues\n1982063 - \u0027Control Plane\u0027  is not translated in Simplified Chinese language in Home-\u003eOverview page\n1982498 - Default registry credential path should be adjusted to use containers/auth.json for oc commands\n1982662 - Workloads - DaemonSets - Add storage: i18n misses\n1982726 - kube-apiserver audit logs show a lot of 404 errors for DELETE \"*/secrets/encryption-config\" on single node clusters\n1983758 - upgrades are failing on disruptive tests\n1983964 - Need Device plugin configuration for the NIC \"needVhostNet\" \u0026 \"isRdma\"\n1984592 - global pull secret not working in OCP4.7.4+ for additional private registries\n1985073 - new-in-4.8 ExtremelyHighIndividualControlPlaneCPU fires on some GCP update jobs\n1985486 - Cluster Proxy not used during installation on OSP with Kuryr\n1985724 - VM Details Page missing translations\n1985838 - [OVN] CNO exportNetworkFlows does not clear collectors when deleted\n1985933 - Downstream image registry recommendation\n1985965 - oVirt CSI driver does not report volume stats\n1986216 - [scale] SNO: Slow Pod recovery due to \"timed out waiting for OVS port binding\"\n1986237 - \"MachineNotYetDeleted\" in Pending state , alert not fired\n1986239 - crictl create fails with \"PID namespace requested, but sandbox infra container invalid\"\n1986302 - console continues to fetch prometheus alert and silences for normal user\n1986314 - Current MTV installation for KubeVirt import flow creates unusable Forklift UI\n1986338 - error creating list of resources in Import YAML\n1986502 - yaml multi file dnd duplicates previous dragged files\n1986819 - fix string typos for hot-plug disks\n1987044 - [OCPV48] Shutoff VM is being shown as \"Starting\" in WebUI when using spec.runStrategy Manual/RerunOnFailure\n1987136 - Declare operatorframework.io/arch.* labels for all operators\n1987257 - Go-http-client user-agent being used for oc adm mirror requests\n1987263 - fsSpaceFillingUpWarningThreshold not aligned to Kubernetes Garbage Collection Threshold\n1987445 - MetalLB integration: All gateway routers in the cluster answer ARP requests for LoadBalancer services IP\n1988406 - SSH key dropped when selecting \"Customize virtual machine\" in UI\n1988440 - Network operator changes ovnkube-config too early causing ovnkube-master pods to crashloop during cluster upgrade\n1988483 - Azure drop ICMP need to frag FRAG when using OVN: openshift-apiserver becomes False after env runs some time due to communication between one master to pods on another master fails with \"Unable to connect to the server\"\n1988879 - Virtual media based deployment fails on Dell servers due to pending Lifecycle Controller jobs\n1989438 - expected replicas is wrong\n1989502 - Developer Catalog is disappearing after short time\n1989843 - \u0027More\u0027 and \u0027Show Less\u0027 functions are not translated on several page\n1990014 - oc debug \u003cpod-name\u003e does not work for Windows pods\n1990190 - e2e testing failed with basic manifest: reason/ExternalProvisioning waiting for a volume to be created\n1990193 - \u0027more\u0027 and \u0027Show Less\u0027  is not being translated on Home -\u003e Search page\n1990255 - Partial or all of the Nodes/StorageClasses don\u0027t appear back on UI after text is removed from search bar\n1990489 - etcdHighNumberOfFailedGRPCRequests fires only on metal env in CI\n1990506 - Missing udev rules in initramfs for /dev/disk/by-id/scsi-* symlinks\n1990556 - get-resources.sh doesn\u0027t honor the no_proxy settings even with no_proxy var\n1990625 - Ironic agent registers with SLAAC address with privacy-stable\n1990635 - CVO does not recognize the channel change if desired version and channel changed at the same time\n1991067 - github.com can not be resolved inside pods where cluster is running on openstack. \n1991573 - Enable typescript strictNullCheck on network-policies files\n1991641 - Baremetal Cluster Operator still Available After Delete Provisioning\n1991770 - The logLevel and operatorLogLevel values do not work with Cloud Credential Operator\n1991819 - Misspelled word \"ocurred\"  in oc inspect cmd\n1991942 - Alignment and spacing fixes\n1992414 - Two rootdisks show on storage step if \u0027This is a CD-ROM boot source\u0027  is checked\n1992453 - The configMap failed to save on VM environment tab\n1992466 - The button \u0027Save\u0027 and \u0027Reload\u0027 are not translated on vm environment tab\n1992475 - The button \u0027Open console in New Window\u0027 and \u0027Disconnect\u0027 are not translated on vm console tab\n1992509 - Could not customize boot source due to source PVC not found\n1992541 - all the alert rules\u0027 annotations \"summary\" and \"description\" should comply with the OpenShift alerting guidelines\n1992580 - storageProfile should stay with the same value by check/uncheck the apply button\n1992592 - list-type missing in oauth.config.openshift.io for identityProviders breaking Server Side Apply\n1992777 - [IBMCLOUD] Default \"ibm_iam_authorization_policy\" is not working as expected in all scenarios\n1993364 - cluster destruction fails to remove router in BYON with Kuryr as primary network (even after BZ 1940159 got fixed)\n1993376 - periodic-ci-openshift-release-master-ci-4.6-upgrade-from-stable-4.5-e2e-azure-upgrade is permfailing\n1994094 - Some hardcodes are detected at the code level in OpenShift console components\n1994142 - Missing required cloud config fields for IBM Cloud\n1994733 - MetalLB: IP address is not assigned to service if there is duplicate IP address in two address pools\n1995021 - resolv.conf and corefile sync slows down/stops after keepalived container restart\n1995335 - [SCALE] ovnkube CNI: remove ovs flows check\n1995493 - Add Secret to workload button and Actions button are not aligned on secret details page\n1995531 - Create RDO-based Ironic image to be promoted to OKD\n1995545 - Project drop-down amalgamates inside main screen while creating storage system for odf-operator\n1995887 - [OVN]After reboot egress node,  lr-policy-list was not correct, some duplicate records or missed internal IPs\n1995924 - CMO should report `Upgradeable: false` when HA workload is incorrectly spread\n1996023 - kubernetes.io/hostname values are larger than filter when create localvolumeset from webconsole\n1996108 - Allow backwards compatibility of shared gateway mode to inject host-based routes into OVN\n1996624 - 100% of the cco-metrics/cco-metrics targets in openshift-cloud-credential-operator namespace are down\n1996630 - Fail to delete the first Authorized SSH Key input box on Advanced page\n1996647 - Provide more useful degraded message in auth operator on DNS errors\n1996736 - Large number of 501 lr-policies in INCI2 env\n1996886 - timedout waiting for flows during pod creation and ovn-controller pegged on worker nodes\n1996916 - Special Resource Operator(SRO) - Fail to deploy simple-kmod on GCP\n1996928 - Enable default operator indexes on ARM\n1997028 - prometheus-operator update removes env var support for thanos-sidecar\n1997059 - Failed to create cluster in AWS us-east-1 region due to a local zone is used\n1997226 - Ingresscontroller reconcilations failing but not shown in operator logs or status of ingresscontroller. \n1997245 - \"Subscription already exists in openshift-storage namespace\" error message is seen while installing odf-operator via UI\n1997269 - Have to refresh console to install kube-descheduler\n1997478 - Storage operator is not available after reboot cluster instances\n1997509 - flake: [sig-cli] oc builds new-build [Skipped:Disconnected] [Suite:openshift/conformance/parallel]\n1997967 - storageClass is not reserved from default wizard to customize wizard\n1998035 - openstack IPI CI: custom var-lib-etcd.mount (ramdisk) unit is racing due to incomplete After/Before order\n1998038 - [e2e][automation] add tests for UI for VM disk hot-plug\n1998087 - Fix CephHealthCheck wrapping contents and add data-tests for HealthItem and SecondaryStatus\n1998174 - Create storageclass gp3-csi  after install ocp cluster on aws\n1998183 - \"r: Bad Gateway\" info is improper\n1998235 - Firefox warning: Cookie \u201ccsrf-token\u201d will be soon rejected\n1998377 - Filesystem table head is not full displayed in disk tab\n1998378 - Virtual Machine is \u0027Not available\u0027 in Home -\u003e Overview -\u003e Cluster inventory\n1998519 - Add fstype when create localvolumeset instance on web console\n1998951 - Keepalived conf ingress peer on in Dual stack cluster contains both IPv6 and IPv4 addresses\n1999076 - [UI] Page Not Found error when clicking on Storage link provided in Overview page\n1999079 - creating pods before sriovnetworknodepolicy sync up succeed will cause node unschedulable\n1999091 - Console update toast notification can appear multiple times\n1999133 - removing and recreating static pod manifest leaves pod in error state\n1999246 - .indexignore is not ingore when oc command load dc configuration\n1999250 - ArgoCD in GitOps operator can\u0027t manage namespaces\n1999255 - ovnkube-node always crashes out the first time it starts\n1999261 - ovnkube-node log spam (and security token leak?)\n1999309 - While installing odf-operator via UI, web console update pop-up navigates to OperatorHub -\u003e Operator Installation page\n1999314 - console-operator is slow to mark Degraded as False once console starts working\n1999425 - kube-apiserver with \"[SHOULD NOT HAPPEN] failed to update managedFields\" err=\"failed to convert new object (machine.openshift.io/v1beta1, Kind=MachineHealthCheck)\n1999556 - \"master\" pool should be updated before the CVO reports available at the new version occurred\n1999578 - AWS EFS CSI tests are constantly failing\n1999603 - Memory Manager allows Guaranteed QoS Pod with hugepages requested is exactly equal to the left over Hugepages\n1999619 - cloudinit is malformatted if a user sets a password during VM creation flow\n1999621 - Empty ssh_authorized_keys entry is added to VM\u0027s cloudinit if created from a customize flow\n1999649 - MetalLB: Only one type of IP address can be assigned to service on dual stack cluster from a address pool that have both IPv4 and IPv6 addresses defined\n1999668 - openshift-install destroy cluster panic\u0027s when given invalid credentials to cloud provider (Azure Stack Hub)\n1999734 - IBM Cloud CIS Instance CRN missing in infrastructure manifest/resource\n1999771 - revert \"force cert rotation every couple days for development\" in 4.10\n1999784 - CVE-2021-3749 nodejs-axios: Regular expression denial of service in trim function\n1999796 - Openshift Console `Helm` tab is not showing helm releases in a namespace when there is high number of deployments in the same namespace. \n1999836 - Admin web-console inconsistent status summary of sparse ClusterOperator conditions\n1999903 - Click \"This is a CD-ROM boot source\" ticking \"Use template size PVC\" on pvc upload form\n1999983 - No way to clear upload error from template boot source\n2000081 - [IPI baremetal]  The metal3 pod failed to restart when switching from Disabled to Managed provisioning without specifying provisioningInterface parameter\n2000096 - Git URL is not re-validated on edit build-config form reload\n2000216 - Successfully imported ImageStreams are not resolved in DeploymentConfig\n2000236 - Confusing usage message from dynkeepalived CLI\n2000268 - Mark cluster unupgradable if vcenter, esxi versions or HW versions are unsupported\n2000430 - bump cluster-api-provider-ovirt version in installer\n2000450 - 4.10: Enable static PV multi-az test\n2000490 - All critical alerts shipped by CMO should have links to a runbook\n2000521 - Kube-apiserver CO degraded due to failed conditional check (ConfigObservationDegraded)\n2000573 - Incorrect StorageCluster CR created and ODF cluster getting installed with 2 Zone OCP cluster\n2000628 - ibm-flashsystem-storage-storagesystem got created without any warning even when the attempt was cancelled\n2000651 - ImageStreamTag alias results in wrong tag and invalid link in Web Console\n2000754 - IPerf2 tests should be lower\n2000846 - Structure logs in the entire codebase of Local Storage Operator\n2000872 - [tracker] container is not able to list on some directories within the nfs after upgrade to 4.7.24\n2000877 - OCP ignores STOPSIGNAL in Dockerfile and sends SIGTERM\n2000938 - CVO does not respect changes to a Deployment strategy\n2000963 - \u0027Inline-volume (default fs)] volumes should store data\u0027 tests are failing on OKD with updated selinux-policy\n2001008 - [MachineSets] CloneMode defaults to linkedClone, but I don\u0027t have snapshot and should be fullClone\n2001240 - Remove response headers for downloads of binaries from OpenShift WebConsole\n2001295 - Remove openshift:kubevirt-machine-controllers decleration from machine-api\n2001317 - OCP Platform Quota Check - Inaccurate MissingQuota error\n2001337 - Details Card in ODF Dashboard mentions OCS\n2001339 - fix text content hotplug\n2001413 - [e2e][automation] add/delete nic and disk to template\n2001441 - Test: oc adm must-gather runs successfully for audit logs -  fail due to startup log\n2001442 - Empty termination.log file for the kube-apiserver has too permissive mode\n2001479 - IBM Cloud DNS unable to create/update records\n2001566 - Enable alerts for prometheus operator in UWM\n2001575 - Clicking on the perspective switcher shows a white page with loader\n2001577 - Quick search placeholder is not displayed properly when the search string is removed\n2001578 - [e2e][automation] add tests for vm dashboard tab\n2001605 - PVs remain in Released state for a long time after the claim is deleted\n2001617 - BucketClass Creation is restricted on 1st page but enabled using side navigation options\n2001620 - Cluster becomes degraded if it can\u0027t talk to Manila\n2001760 - While creating \u0027Backing Store\u0027, \u0027Bucket Class\u0027, \u0027Namespace Store\u0027 user is navigated to \u0027Installed Operators\u0027 page after clicking on ODF\n2001761 - Unable to apply cluster operator storage for SNO on GCP platform. \n2001765 - Some error message in the log  of diskmaker-manager caused confusion\n2001784 - show loading page before final results instead of showing a transient message No log files exist\n2001804 - Reload feature on Environment section in Build Config form does not work properly\n2001810 - cluster admin unable to view BuildConfigs in all namespaces\n2001817 - Failed to load RoleBindings list that will lead to \u2018Role name\u2019 is not able to be selected on Create RoleBinding page as well\n2001823 - OCM controller must update operator status\n2001825 - [SNO]ingress/authentication clusteroperator degraded when enable ccm from start\n2001835 - Could not select image tag version when create app from dev console\n2001855 - Add capacity is disabled for ocs-storagecluster\n2001856 - Repeating event: MissingVersion no image found for operand pod\n2001959 - Side nav list borders don\u0027t extend to edges of container\n2002007 - Layout issue on \"Something went wrong\" page\n2002010 - ovn-kube may never attempt to retry a pod creation\n2002012 - Cannot change volume mode when cloning a VM from a template\n2002027 - Two instances of Dotnet helm chart show as one in topology\n2002075 - opm render does not automatically pulling in the image(s) used in the deployments\n2002121 - [OVN] upgrades failed for IPI  OSP16 OVN  IPSec cluster\n2002125 - Network policy details page heading should be updated to Network Policy details\n2002133 - [e2e][automation] add support/virtualization and improve deleteResource\n2002134 - [e2e][automation] add test to verify vm details tab\n2002215 - Multipath day1 not working on s390x\n2002238 - Image stream tag is not persisted when switching from yaml to form editor\n2002262 - [vSphere] Incorrect user agent in vCenter sessions list\n2002266 - SinkBinding create form doesn\u0027t allow to use subject name, instead of label selector\n2002276 - OLM fails to upgrade operators immediately\n2002300 - Altering the Schedule Profile configurations doesn\u0027t affect the placement of the pods\n2002354 - Missing DU configuration \"Done\" status reporting during ZTP flow\n2002362 - Dynamic Plugin - ConsoleRemotePlugin for webpack doesn\u0027t use commonjs\n2002368 - samples should not go degraded when image allowedRegistries blocks imagestream creation\n2002372 - Pod creation failed due to mismatched pod IP address in CNI and OVN\n2002397 - Resources search is inconsistent\n2002434 - CRI-O leaks some children PIDs\n2002443 - Getting undefined error on create local volume set page\n2002461 - DNS operator performs spurious updates in response to API\u0027s defaulting of service\u0027s internalTrafficPolicy\n2002504 - When the openshift-cluster-storage-operator is degraded because of \"VSphereProblemDetectorController_SyncError\", the insights operator is not sending the logs from all pods. \n2002559 - User preference for topology list view does not follow when a new namespace is created\n2002567 - Upstream SR-IOV worker doc has broken links\n2002588 - Change text to be sentence case to align with PF\n2002657 - ovn-kube egress IP monitoring is using a random port over the node network\n2002713 - CNO: OVN logs should have millisecond resolution\n2002748 - [ICNI2] \u0027ErrorAddingLogicalPort\u0027 failed to handle external GW check: timeout waiting for namespace event\n2002759 - Custom profile should not allow not including at least one required HTTP2 ciphersuite\n2002763 - Two storage systems getting created with external mode RHCS\n2002808 - KCM does not use web identity credentials\n2002834 - Cluster-version operator does not remove unrecognized volume mounts\n2002896 - Incorrect result return when user filter data by name on search page\n2002950 - Why spec.containers.command is not created with \"oc create deploymentconfig \u003cdc-name\u003e --image=\u003cimage\u003e -- \u003ccommand\u003e\"\n2003096 - [e2e][automation] check bootsource URL is displaying on review step\n2003113 - OpenShift Baremetal IPI installer uses first three defined nodes under hosts in install-config for master nodes instead of filtering the hosts with the master role\n2003120 - CI: Uncaught error with ResizeObserver on operand details page\n2003145 - Duplicate operand tab titles causes \"two children with the same key\" warning\n2003164 - OLM, fatal error: concurrent map writes\n2003178 - [FLAKE][knative] The UI doesn\u0027t show updated traffic distribution after accepting the form\n2003193 - Kubelet/crio leaks netns and veth ports in the host\n2003195 - OVN CNI should ensure host veths are removed\n2003204 - Jenkins all new container images (openshift4/ose-jenkins) not supporting \u0027-e JENKINS_PASSWORD=password\u0027  ENV  which was working for old container images\n2003206 - Namespace stuck terminating: Failed to delete all resource types, 1 remaining: unexpected items still remain in namespace\n2003239 - \"[sig-builds][Feature:Builds][Slow] can use private repositories as build input\" tests fail outside of CI\n2003244 - Revert libovsdb client code\n2003251 - Patternfly components with list element has list item bullet when they should not. \n2003252 - \"[sig-builds][Feature:Builds][Slow] starting a build using CLI  start-build test context override environment BUILD_LOGLEVEL in buildconfig\" tests do not work as expected outside of CI\n2003269 - Rejected pods should be filtered from admission regression\n2003357 - QE- Removing the epic tags for gherkin tags related to 4.9 Release\n2003426 - [e2e][automation]  add test for vm details bootorder\n2003496 - [e2e][automation] add test for vm resources requirment settings\n2003641 - All metal ipi jobs are failing in 4.10\n2003651 - ODF4.9+LSO4.8 installation via UI, StorageCluster move to error state\n2003655 - [IPI ON-PREM] Keepalived chk_default_ingress track script failed even though default router pod runs on node\n2003683 - Samples operator is panicking in CI\n2003711 - [UI] Empty file ceph-external-cluster-details-exporter.py downloaded from external cluster \"Connection Details\" page\n2003715 - Error on creating local volume set after selection of the volume mode\n2003743 - Remove workaround keeping /boot RW for kdump support\n2003775 - etcd pod on CrashLoopBackOff after master replacement procedure\n2003788 - CSR reconciler report error constantly when BYOH CSR approved by other Approver\n2003792 - Monitoring metrics query graph flyover panel is useless\n2003808 - Add Sprint 207 translations\n2003845 - Project admin cannot access image vulnerabilities view\n2003859 - sdn emits events with garbage messages\n2003896 - (release-4.10) ApiRequestCounts conditional gatherer\n2004009 - 4.10: Fix multi-az zone scheduling e2e for 5 control plane replicas\n2004051 - CMO can report as being Degraded while node-exporter is deployed on all nodes\n2004059 - [e2e][automation] fix current tests for downstream\n2004060 - Trying to use basic spring boot sample causes crash on Firefox\n2004101 - [UI] When creating storageSystem deployment type dropdown under advanced setting doesn\u0027t close after selection\n2004127 - [flake] openshift-controller-manager event reason/SuccessfulDelete occurs too frequently\n2004203 - build config\u0027s created prior to 4.8 with image change triggers can result in trigger storm in OCM/openshift-apiserver\n2004313 - [RHOCP 4.9.0-rc.0] Failing to deploy Azure cluster from the macOS installer - ignition_bootstrap.ign: no such file or directory\n2004449 - Boot option recovery menu prevents image boot\n2004451 - The backup filename displayed in the RecentBackup message is incorrect\n2004459 - QE - Modified the AddFlow gherkin scripts and automation scripts\n2004508 - TuneD issues with the recent ConfigParser changes. \n2004510 - openshift-gitops operator hooks gets unauthorized (401) errors during jobs executions\n2004542 - [osp][octavia lb] cannot create LoadBalancer type svcs\n2004578 - Monitoring and node labels missing for an external storage platform\n2004585 - prometheus-k8s-0 cpu usage keeps increasing for the first 3 days\n2004596 - [4.10] Bootimage bump tracker\n2004597 - Duplicate ramdisk log containers running\n2004600 - Duplicate ramdisk log containers running\n2004609 - output of \"crictl inspectp\" is not complete\n2004625 - BMC credentials could be logged if they change\n2004632 - When LE takes a large amount of time, multiple whereabouts are seen\n2004721 - ptp/worker custom threshold doesn\u0027t change ptp events threshold\n2004736 - [knative] Create button on new Broker form is inactive despite form being filled\n2004796 - [e2e][automation] add test for vm scheduling policy\n2004814 - (release-4.10) OCM controller - change type of the etc-pki-entitlement secret to opaque\n2004870 - [External Mode] Insufficient spacing along y-axis in RGW Latency Performance Card\n2004901 - [e2e][automation] improve kubevirt devconsole tests\n2004962 - Console frontend job consuming too much CPU in CI\n2005014 - state of ODF StorageSystem is misreported during installation or uninstallation\n2005052 - Adding a MachineSet selector matchLabel causes orphaned Machines\n2005179 - pods status filter is not taking effect\n2005182 - sync list of deprecated apis about to be removed\n2005282 - Storage cluster name is given as title in StorageSystem details page\n2005355 - setuptools 58 makes Kuryr CI fail\n2005407 - ClusterNotUpgradeable Alert should be set to Severity Info\n2005415 - PTP operator with sidecar api configured throws  bind: address already in use\n2005507 - SNO spoke cluster failing to reach coreos.live.rootfs_url is missing url in console\n2005554 - The switch status of the button \"Show default project\" is not revealed correctly in code\n2005581 - 4.8.12 to 4.9 upgrade hung due to cluster-version-operator pod CrashLoopBackOff: error creating clients: invalid configuration: no configuration has been provided, try setting KUBERNETES_MASTER environment variable\n2005761 - QE - Implementing crw-basic feature file\n2005783 - Fix accessibility issues in the \"Internal\" and \"Internal - Attached Mode\" Installation Flow\n2005811 - vSphere Problem Detector operator - ServerFaultCode: InvalidProperty\n2005854 - SSH NodePort service is created for each VM\n2005901 - KS, KCM and KA going Degraded during master nodes upgrade\n2005902 - Current UI flow for MCG only deployment is confusing and doesn\u0027t reciprocate any message to the end-user\n2005926 - PTP operator NodeOutOfPTPSync rule is using max offset from the master instead of openshift_ptp_clock_state metrics\n2005971 - Change telemeter to report the Application Services product usage metrics\n2005997 - SELinux domain container_logreader_t does not have a policy to follow sym links for log files\n2006025 - Description to use an existing StorageClass while creating StorageSystem needs to be re-phrased\n2006060 - ocs-storagecluster-storagesystem details are missing on UI for MCG Only and MCG only in LSO mode deployment types\n2006101 - Power off fails for drivers that don\u0027t support Soft power off\n2006243 - Metal IPI upgrade jobs are running out of disk space\n2006291 - bootstrapProvisioningIP set incorrectly when provisioningNetworkCIDR doesn\u0027t use the 0th address\n2006308 - Backing Store YAML tab on click displays a blank screen on UI\n2006325 - Multicast is broken across nodes\n2006329 - Console only allows Web Terminal Operator to be installed in OpenShift Operators\n2006364 - IBM Cloud: Set resourceGroupId for resourceGroups, not simply resource\n2006561 - [sig-instrumentation] Prometheus when installed on the cluster shouldn\u0027t have failing rules evaluation [Skipped:Disconnected] [Suite:openshift/conformance/parallel]\n2006690 - OS boot failure \"x64 Exception Type 06 - Invalid Opcode Exception\"\n2006714 - add retry for etcd errors in kube-apiserver\n2006767 - KubePodCrashLooping may not fire\n2006803 - Set CoreDNS cache entries for forwarded zones\n2006861 - Add Sprint 207 part 2 translations\n2006945 - race condition can cause crashlooping bootstrap kube-apiserver in cluster-bootstrap\n2006947 - e2e-aws-proxy for 4.10 is permafailing with samples operator errors\n2006975 - clusteroperator/etcd status condition should not change reasons frequently due to EtcdEndpointsDegraded\n2007085 - Intermittent failure mounting /run/media/iso when booting live ISO from USB stick\n2007136 - Creation of BackingStore, BucketClass, NamespaceStore fails\n2007271 - CI Integration for Knative test cases\n2007289 - kubevirt tests are failing in CI\n2007322 - Devfile/Dockerfile import does not work for unsupported git host\n2007328 - Updated patternfly to v4.125.3 and pf.quickstarts to v1.2.3. \n2007379 - Events are not generated for master offset  for ordinary clock\n2007443 - [ICNI 2.0] Loadbalancer pods do not establish BFD sessions with all workers that host pods for the routed namespace\n2007455 - cluster-etcd-operator: render command should fail if machineCidr contains reserved address\n2007495 - Large label value for the metric kubelet_started_pods_errors_total with label message when there is a error\n2007522 - No new local-storage-operator-metadata-container is build for 4.10\n2007551 - No new ose-aws-efs-csi-driver-operator-bundle-container is build for 4.10\n2007580 - Azure cilium installs are failing e2e tests\n2007581 - Too many haproxy processes in default-router pod causing high load average after upgrade from v4.8.3 to v4.8.10\n2007677 - Regression: core container io performance metrics are missing for pod, qos, and system slices on nodes\n2007692 - 4.9 \"old-rhcos\" jobs are permafailing with storage test failures\n2007710 - ci/prow/e2e-agnostic-cmd job is failing on prow\n2007757 - must-gather extracts imagestreams in the \"openshift\" namespace, but not Templates\n2007802 - AWS machine actuator get stuck if machine is completely missing\n2008096 - TestAWSFinalizerDeleteS3Bucket sometimes fails to teardown operator\n2008119 - The serviceAccountIssuer field on Authentication CR is reseted to \u201c\u201d when installation process\n2008151 - Topology breaks on clicking in empty state\n2008185 - Console operator go.mod should use go 1.16.version\n2008201 - openstack-az job is failing on haproxy idle test\n2008207 - vsphere CSI driver doesn\u0027t set resource limits\n2008223 - gather_audit_logs: fix oc command line to get the current audit profile\n2008235 - The Save button in the Edit DC form remains disabled\n2008256 - Update Internationalization README with scope info\n2008321 - Add correct documentation link for MON_DISK_LOW\n2008462 - Disable PodSecurity feature gate for 4.10\n2008490 - Backing store details page does not contain all the kebab actions. \n2008521 - gcp-hostname service should correct invalid search entries in resolv.conf\n2008532 - CreateContainerConfigError:: failed to prepare subPath for volumeMount\n2008539 - Registry doesn\u0027t fall back to secondary ImageContentSourcePolicy Mirror\n2008540 - HighlyAvailableWorkloadIncorrectlySpread always fires on upgrade on cluster with two workers\n2008599 - Azure Stack UPI does not have Internal Load Balancer\n2008612 - Plugin asset proxy does not pass through browser cache headers\n2008712 - VPA webhook timeout prevents all pods from starting\n2008733 - kube-scheduler: exposed /debug/pprof port\n2008911 - Prometheus repeatedly scaling prometheus-operator replica set\n2008926 - [sig-api-machinery] API data in etcd should be stored at the correct location and version for all resources [Serial] [Suite:openshift/conformance/serial]\n2008987 - OpenShift SDN Hosted Egress IP\u0027s are not being scheduled to nodes after upgrade to 4.8.12\n2009055 - Instances of OCS to be replaced with ODF on UI\n2009078 - NetworkPodsCrashLooping alerts in upgrade CI jobs\n2009083 - opm blocks pruning of existing bundles during add\n2009111 - [IPI-on-GCP] \u0027Install a cluster with nested virtualization enabled\u0027 failed due to unable to launch compute instances\n2009131 - [e2e][automation] add more test about vmi\n2009148 - [e2e][automation] test vm nic presets and options\n2009233 - ACM policy object generated by PolicyGen conflicting with OLM Operator\n2009253 - [BM] [IPI] [DualStack] apiVIP and ingressVIP should be of the same primary IP family\n2009298 - Service created for VM SSH access is not owned by the VM and thus is not deleted if the VM is deleted\n2009384 - UI changes to support BindableKinds CRD changes\n2009404 - ovnkube-node pod enters CrashLoopBackOff after OVN_IMAGE is swapped\n2009424 - Deployment upgrade is failing availability check\n2009454 - Change web terminal subscription permissions from get to list\n2009465 - container-selinux should come from rhel8-appstream\n2009514 - Bump OVS to 2.16-15\n2009555 - Supermicro X11 system not booting from vMedia with AI\n2009623 - Console: Observe \u003e Metrics page: Table pagination menu shows bullet points\n2009664 - Git Import: Edit of knative service doesn\u0027t work as expected for git import flow\n2009699 - Failure to validate flavor RAM\n2009754 - Footer is not sticky anymore in import forms\n2009785 - CRI-O\u0027s version file should be pinned by MCO\n2009791 - Installer:  ibmcloud ignores install-config values\n2009823 - [sig-arch] events should not repeat pathologically - reason/VSphereOlderVersionDetected Marking cluster un-upgradeable because one or more VMs are on hardware version vmx-13\n2009840 - cannot build extensions on aarch64 because of unavailability of rhel-8-advanced-virt repo\n2009859 - Large number of sessions created by vmware-vsphere-csi-driver-operator during e2e tests\n2009873 - Stale Logical Router Policies and Annotations for a given node\n2009879 - There should be test-suite coverage to ensure admin-acks work as expected\n2009888 - SRO package name collision between official and community version\n2010073 - uninstalling and then reinstalling sriov-network-operator is not working\n2010174 - 2 PVs get created unexpectedly with different paths that actually refer to the same device on the node. \n2010181 - Environment variables not getting reset on reload on deployment edit form\n2010310 - [sig-instrumentation][Late] OpenShift alerting rules should have description and summary annotations [Skipped:Disconnected] [Suite:openshift/conformance/parallel]\n2010341 - OpenShift Alerting Rules Style-Guide Compliance\n2010342 - Local console builds can have out of memory errors\n2010345 - OpenShift Alerting Rules Style-Guide Compliance\n2010348 - Reverts PIE build mode for K8S components\n2010352 - OpenShift Alerting Rules Style-Guide Compliance\n2010354 - OpenShift Alerting Rules Style-Guide Compliance\n2010359 - OpenShift Alerting Rules Style-Guide Compliance\n2010368 - OpenShift Alerting Rules Style-Guide Compliance\n2010376 - OpenShift Alerting Rules Style-Guide Compliance\n2010662 - Cluster is unhealthy after image-registry-operator tests\n2010663 - OpenShift Alerting Rules Style-Guide Compliance (ovn-kubernetes subcomponent)\n2010665 - Bootkube tries to use oc after cluster bootstrap is done and there is no API\n2010698 - [BM] [IPI] [Dual Stack] Installer must ensure ipv6 short forms too if clusterprovisioning IP is specified as ipv6 address\n2010719 - etcdHighNumberOfFailedGRPCRequests runbook is missing\n2010864 - Failure building EFS operator\n2010910 - ptp worker events unable to identify interface for multiple interfaces\n2010911 - RenderOperatingSystem() returns wrong OS version on OCP 4.7.24\n2010921 - Azure Stack Hub does not handle additionalTrustBundle\n2010931 - SRO CSV uses non default category \"Drivers and plugins\"\n2010946 - concurrent CRD from ovirt-csi-driver-operator gets reconciled by CVO after deployment, changing CR as well. \n2011038 - optional operator conditions are confusing\n2011063 - CVE-2021-39226 grafana: Snapshot authentication bypass\n2011171 - diskmaker-manager constantly redeployed by LSO when creating LV\u0027s\n2011293 - Build pod are not pulling images if we are not explicitly giving the registry name with the image\n2011368 - Tooltip in pipeline visualization shows misleading data\n2011386 - [sig-arch] Check if alerts are firing during or after upgrade success --- alert KubePodNotReady fired for 60 seconds with labels\n2011411 - Managed Service\u0027s Cluster overview page contains link to missing Storage dashboards\n2011443 - Cypress tests assuming Admin Perspective could fail on shared/reference cluster\n2011513 - Kubelet rejects pods that use resources that should be freed by completed pods\n2011668 - Machine stuck in deleting phase in VMware \"reconciler failed to Delete machine\"\n2011693 - (release-4.10) \"insightsclient_request_recvreport_total\" metric is always incremented\n2011698 - After upgrading cluster to 4.8 the kube-state-metrics service doesn\u0027t export namespace labels anymore\n2011733 - Repository README points to broken documentarion link\n2011753 - Ironic resumes clean before raid configuration job is actually completed\n2011809 - The nodes page in the openshift console doesn\u0027t work. You just get a blank page\n2011822 - Obfuscation doesn\u0027t work at clusters with OVN\n2011882 - SRO helm charts not synced with templates\n2011893 - Validation: BMC driver ipmi is not supported for secure UEFI boot\n2011896 - [4.10] ClusterVersion Upgradeable=False MultipleReasons should include all messages\n2011903 - vsphere-problem-detector: session leak\n2011927 - OLM should allow users to specify a proxy for GRPC connections\n2011956 - [tracker] Kubelet rejects pods that use resources that should be freed by completed pods\n2011960 - [tracker] Storage operator is not available after reboot cluster instances\n2011971 - ICNI2 pods are stuck in ContainerCreating state\n2011972 - Ingress operator not creating wildcard route for hypershift  clusters\n2011977 - SRO bundle references non-existent image\n2012069 - Refactoring Status controller\n2012177 - [OCP 4.9 + OCS 4.8.3] Overview tab is missing under Storage after successful deployment on UI\n2012228 - ibmcloud: credentialsrequests invalid for machine-api-operator: resource-group\n2012233 - [IBMCLOUD] IPI: \"Exceeded limit of remote rules per security group (the limit is 5 remote rules per security group)\"\n2012235 - [IBMCLOUD] IPI: IBM cloud provider requires ResourceGroupName in cloudproviderconfig\n2012317 - Dynamic Plugins: ListPageCreateDropdown items cut off\n2012407 - [e2e][automation] improve vm tab console tests\n2012426 - ThanosSidecarBucketOperationsFailed/ThanosSidecarUnhealthy alerts don\u0027t have namespace label\n2012562 - migration condition is not detected in list view\n2012770 - when using expression metric openshift_apps_deploymentconfigs_last_failed_rollout_time namespace label is re-written\n2012780 - The port 50936 used by haproxy is occupied by kube-apiserver\n2012838 - Setting the default maximum container root partition size for Overlay with CRI-O stop working\n2012902 - Neutron Ports assigned to Completed Pods are not reused Edit\n2012915 - kube_persistentvolumeclaim_labels and kube_persistentvolume_labels are missing in OCP 4.8 monitoring stack\n2012971 - Disable operands deletes\n2013034 - Cannot install to openshift-nmstate namespace\n2013127 - OperatorHub links could not be opened in a new tabs (sharing and open a deep link works fine)\n2013199 - post reboot of node SRIOV policy taking huge time\n2013203 - UI breaks when trying to create block pool before storage cluster/system creation\n2013222 - Full breakage for nightly payload promotion\n2013273 - Nil pointer exception when phc2sys options are missing\n2013321 - TuneD: high CPU utilization of the TuneD daemon. \n2013416 - Multiple assets emit different content to the same filename\n2013431 - Application selector dropdown has incorrect font-size and positioning\n2013528 - mapi_current_pending_csr is always set to 1 on OpenShift Container Platform 4.8\n2013545 - Service binding created outside topology is not visible\n2013599 - Scorecard support storage is not included in ocp4.9\n2013632 - Correction/Changes in Quick Start Guides for ODF 4.9 (Install ODF guide)\n2013646 - fsync controller will show false positive if gaps in metrics are observed. \n2013710 - ZTP Operator subscriptions for 4.9 release branch should point to 4.9 by default\n2013751 - Service details page is showing wrong in-cluster hostname\n2013787 - There are two tittle \u0027Network Attachment Definition Details\u0027 on NAD details page\n2013871 - Resource table headings are not aligned with their column data\n2013895 - Cannot enable accelerated network via MachineSets on Azure\n2013920 - \"--collector.filesystem.ignored-mount-points is DEPRECATED and will be removed in 2.0.0, use --collector.filesystem.mount-points-exclude\"\n2013930 - Create Buttons enabled for Bucket Class, Backingstore and Namespace Store in the absence of Storagesystem(or MCG)\n2013969 - oVIrt CSI driver fails on creating PVCs on hosted engine storage domain\n2013990 - Observe dashboard crashs on reload when perspective has changed (in another tab)\n2013996 - Project detail page: Action \"Delete Project\" does nothing for the default project\n2014071 - Payload imagestream new tags not properly updated during cluster upgrade\n2014153 - SRIOV exclusive pooling\n2014202 - [OCP-4.8.10] OVN-Kubernetes: service IP is not responding when egressIP set to the namespace\n2014238 - AWS console test is failing on importing duplicate YAML definitions\n2014245 - Several aria-labels, external links, and labels aren\u0027t internationalized\n2014248 - Several files aren\u0027t internationalized\n2014352 - Could not filter out machine by using node name on machines page\n2014464 - Unexpected spacing/padding below navigation groups in developer perspective\n2014471 - Helm Release notes tab is not automatically open after installing a chart for other languages\n2014486 - Integration Tests: OLM single namespace operator tests failing\n2014488 - Custom operator cannot change orders of condition tables\n2014497 - Regex slows down different forms and creates too much recursion errors in the log\n2014538 - Kuryr controller crash looping on  self._get_vip_port(loadbalancer).id   \u0027NoneType\u0027 object has no attribute \u0027id\u0027\n2014614 - Metrics scraping requests should be assigned to exempt priority level\n2014710 - TestIngressStatus test is broken on Azure\n2014954 - The prometheus-k8s-{0,1} pods are CrashLoopBackoff repeatedly\n2014995 - oc adm must-gather cannot gather audit logs with \u0027None\u0027 audit profile\n2015115 - [RFE] PCI passthrough\n2015133 - [IBMCLOUD] ServiceID API key credentials seems to be insufficient for ccoctl \u0027--resource-group-name\u0027 parameter\n2015154 - Support ports defined networks and primarySubnet\n2015274 - Yarn dev fails after updates to dynamic plugin JSON schema logic\n2015337 - 4.9.0 GA MetalLB operator image references need to be adjusted to match production\n2015386 - Possibility to add labels to the built-in OCP alerts\n2015395 - Table head on Affinity Rules modal is not fully expanded\n2015416 - CI implementation for Topology plugin\n2015418 - Project Filesystem query returns No datapoints found\n2015420 - No vm resource in project view\u0027s inventory\n2015422 - No conflict checking on snapshot name\n2015472 - Form and YAML view switch button should have distinguishable status\n2015481 - [4.10]  sriov-network-operator daemon pods are failing to start\n2015493 - Cloud Controller Manager Operator does not respect \u0027additionalTrustBundle\u0027 setting\n2015496 - Storage - PersistentVolumes : Claim colum value \u0027No Claim\u0027 in English\n2015498 - [UI] Add capacity when not applicable (for MCG only deployment and External mode cluster) fails to pass any info. to user and tries to just load a blank screen on \u0027Add Capacity\u0027 button click\n2015506 - Home - Search - Resources - APIRequestCount : hard to select an item from ellipsis menu\n2015515 - Kubelet checks all providers even if one is configured: NoCredentialProviders: no valid providers in chain. \n2015535 - Administration - ResourceQuotas - ResourceQuota details: Inside Pie chart \u0027x% used\u0027 is in English\n2015549 - Observe - Metrics: Column heading and pagination text is in English\n2015557 - Workloads - DeploymentConfigs :  Error message is in English\n2015568 - Compute - Nodes : CPU column\u0027s values are in English\n2015635 - Storage operator fails causing installation to fail on ASH\n2015660 - \"Finishing boot source customization\" screen should not use term \"patched\"\n2015793 - [hypershift] The collect-profiles job\u0027s pods should run on the control-plane node\n2015806 - Metrics view in Deployment reports \"Forbidden\" when not cluster-admin\n2015819 - Conmon sandbox processes run on non-reserved CPUs with workload partitioning\n2015837 - OS_CLOUD overwrites install-config\u0027s platform.openstack.cloud\n2015950 - update from 4.7.22 to 4.8.11 is failing due to large amount of secrets to watch\n2015952 - RH CodeReady Workspaces Operator in e2e testing will soon fail\n2016004 - [RFE] RHCOS: help determining whether a user-provided image was already booted (Ignition provisioning already performed)\n2016008 - [4.10] Bootimage bump tracker\n2016052 - No e2e CI presubmit configured for release component azure-file-csi-driver\n2016053 - No e2e CI presubmit configured for release component azure-file-csi-driver-operator\n2016054 - No e2e CI presubmit configured for release component cluster-autoscaler\n2016055 - No e2e CI presubmit configured for release component console\n2016058 - openshift-sync does not synchronise in \"ose-jenkins:v4.8\"\n2016064 - No e2e CI presubmit configured for release component ibm-cloud-controller-manager\n2016065 - No e2e CI presubmit configured for release component ibmcloud-machine-controllers\n2016175 - Pods get stuck in ContainerCreating state when attaching volumes fails on SNO clusters. \n2016179 - Add Sprint 208 translations\n2016228 - Collect Profiles pprof secret is hardcoded to openshift-operator-lifecycle-manager\n2016235 - should update to 7.5.11 for grafana resources version label\n2016296 - Openshift virtualization  : Create Windows Server 2019 VM using template : Fails\n2016334 - shiftstack: SRIOV nic reported as not supported\n2016352 - Some pods start before CA resources are present\n2016367 - Empty task box is getting created for a pipeline without finally task\n2016435 - Duplicate AlertmanagerClusterFailedToSendAlerts alerts\n2016438 - Feature flag gating is missing in few extensions contributed via knative plugin\n2016442 - OCPonRHV: pvc should be in Bound state and without error when choosing default sc\n2016446 - [OVN-Kubernetes] Egress Networkpolicy is failing Intermittently for statefulsets\n2016453 - Complete i18n for GaugeChart defaults\n2016479 - iface-id-ver is not getting updated for existing lsp\n2016925 - Dashboards with All filter, change to a specific value and change back to All,  data will disappear\n2016951 - dynamic actions list is not disabling \"open console\" for stopped vms\n2016955 - m5.large instance type for bootstrap node is hardcoded causing deployments to fail if instance type is not available\n2016988 - NTO does not set io_timeout and max_retries for AWS Nitro instances\n2017016 - [REF] Virtualization menu\n2017036 - [sig-network-edge][Feature:Idling] Unidling should handle many TCP connections fails in periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn\n2017050 - Dynamic Plugins: Shared modules loaded multiple times, breaking use of PatternFly\n2017130 - t is not a function error navigating to details page\n2017141 - Project dropdown has a dynamic inline width added which can cause min-width issue\n2017244 - ovirt csi operator static files creation is in the wrong order\n2017276 - [4.10] Volume mounts not created with the correct security context\n2017327 - When run opm index prune failed with error removing operator package cic-operator FOREIGN KEY constraint failed. \n2017427 - NTO does not restart TuneD daemon when profile application is taking too long\n2017535 - Broken Argo CD link image on GitOps Details Page\n2017547 - Siteconfig application sync fails with The AgentClusterInstall is invalid: spec.provisionRequirements.controlPlaneAgents: Required value when updating images references\n2017564 - On-prem prepender dispatcher script overwrites DNS search settings\n2017565 - CCMO does not handle additionalTrustBundle on Azure Stack\n2017566 - MetalLB: Web Console -Create Address pool form shows address pool name twice\n2017606 - [e2e][automation] add test to verify send key for VNC console\n2017650 - [OVN]EgressFirewall cannot be applied correctly if cluster has windows nodes\n2017656 - VM IP address is \"undefined\" under VM details -\u003e ssh field\n2017663 - SSH password authentication is disabled when public key is not supplied\n2017680 - [gcp] Couldn\u2019t enable support for instances with GPUs on GCP\n2017732 - [KMS] Prevent creation of encryption enabled storageclass without KMS connection set\n2017752 - (release-4.10) obfuscate identity provider attributes in collected authentication.operator.openshift.io resource\n2017756 - overlaySize setting on containerruntimeconfig is ignored due to cri-o defaults\n2017761 - [e2e][automation] dummy bug for 4.9 test dependency\n2017872 - Add Sprint 209 translations\n2017874 - The installer is incorrectly checking the quota for X instances instead of G and VT instances\n2017879 - Add Chinese translation for \"alternate\"\n2017882 - multus: add handling of pod UIDs passed from runtime\n2017909 - [ICNI 2.0] ovnkube-masters stop processing add/del events for pods\n2018042 - HorizontalPodAutoscaler CPU averageValue did not show up in HPA metrics GUI\n2018093 - Managed cluster should ensure control plane pods do not run in best-effort QoS\n2018094 - the tooltip length is limited\n2018152 - CNI pod is not restarted when It cannot start servers due to ports being used\n2018208 - e2e-metal-ipi-ovn-ipv6 are failing 75% of the time\n2018234 - user settings are saved in local storage instead of on cluster\n2018264 - Delete Export button doesn\u0027t work in topology sidebar (general issue with unknown CSV?)\n2018272 - Deployment managed by link and topology sidebar links to invalid resource page (at least for Exports)\n2018275 - Topology graph doesn\u0027t show context menu for Export CSV\n2018279 - Edit and Delete confirmation modals for managed resource should close when the managed resource is clicked\n2018380 - Migrate docs links to access.redhat.com\n2018413 - Error: context deadline exceeded, OCP 4.8.9\n2018428 - PVC is deleted along with VM even with \"Delete Disks\" unchecked\n2018445 - [e2e][automation] enhance tests for downstream\n2018446 - [e2e][automation] move tests to different level\n2018449 - [e2e][automation] add test about create/delete network attachment definition\n2018490 - [4.10] Image provisioning fails with file name too long\n2018495 - Fix typo in internationalization README\n2018542 - Kernel upgrade does not reconcile DaemonSet\n2018880 - Get \u0027No datapoints found.\u0027 when query metrics about alert rule KubeCPUQuotaOvercommit and KubeMemoryQuotaOvercommit\n2018884 - QE - Adapt crw-basic feature file to OCP 4.9/4.10 changes\n2018935 - go.sum not updated, that ART extracts version string from, WAS: Missing backport from 4.9 for Kube bump PR#950\n2018965 - e2e-metal-ipi-upgrade is permafailing in 4.10\n2018985 - The rootdisk size is 15Gi of windows VM in customize wizard\n2019001 - AWS: Operator degraded (CredentialsFailing): 1 of 6 credentials requests are failing to sync. \n2019096 - Update SRO leader election timeout to support SNO\n2019129 - SRO in operator hub points to wrong repo for README\n2019181 - Performance profile does not apply\n2019198 - ptp offset metrics are not named according to the log output\n2019219 - [IBMCLOUD]: cloud-provider-ibm missing IAM permissions in CCCMO CredentialRequest\n2019284 - Stop action should not in the action list while VMI is not running\n2019346 - zombie processes accumulation and Argument list too long\n2019360 - [RFE] Virtualization Overview page\n2019452 - Logger object in LSO appends to existing logger recursively\n2019591 - Operator install modal body that scrolls has incorrect padding causing shadow position to be incorrect\n2019634 - Pause and migration is enabled in action list for a user who has view only permission\n2019636 - Actions in VM tabs should be disabled when user has view only permission\n2019639 - \"Take snapshot\" should be disabled while VM image is still been importing\n2019645 - Create button is not removed on \"Virtual Machines\" page for view only user\n2019646 - Permission error should pop-up immediately while clicking \"Create VM\" button on template page for view only user\n2019647 - \"Remove favorite\" and \"Create new Template\" should be disabled in template action list for view only user\n2019717 - cant delete VM with un-owned pvc attached\n2019722 - The shared-resource-csi-driver-node pod runs as \u201cBestEffort\u201d qosClass\n2019739 - The shared-resource-csi-driver-node uses imagePullPolicy as \"Always\"\n2019744 - [RFE] Suggest users to download newest RHEL 8 version\n2019809 - [OVN][Upgrade] After upgrade to 4.7.34 ovnkube-master pods are in CrashLoopBackOff/ContainerCreating and other multiple issues at OVS/OVN level\n2019827 - Display issue with top-level menu items running demo plugin\n2019832 - 4.10 Nightlies blocked: Failed to upgrade authentication, operator was degraded\n2019886 - Kuryr unable to finish ports recovery upon controller restart\n2019948 - [RFE] Restructring Virtualization links\n2019972 - The Nodes section doesn\u0027t display the csr of the nodes that are trying to join the cluster\n2019977 - Installer doesn\u0027t validate region causing binary to hang with a 60 minute timeout\n2019986 - Dynamic demo plugin fails to build\n2019992 - instance:node_memory_utilisation:ratio metric is incorrect\n2020001 - Update dockerfile for demo dynamic plugin to reflect dir change\n2020003 - MCD does not regard \"dangling\" symlinks as a files, attempts to write through them on next backup, resulting in \"not writing through dangling symlink\" error and degradation. \n2020107 - cluster-version-operator: remove runlevel from CVO namespace\n2020153 - Creation of Windows high performance VM fails\n2020216 - installer: Azure storage container blob where is stored bootstrap.ign file shouldn\u0027t be public\n2020250 - Replacing deprecated ioutil\n2020257 - Dynamic plugin with multiple webpack compilation passes may fail to build\n2020275 - ClusterOperators link in console returns blank page during upgrades\n2020377 - permissions error while using tcpdump option with must-gather\n2020489 - coredns_dns metrics don\u0027t include the custom zone metrics data due to CoreDNS prometheus plugin is not defined\n2020498 - \"Show PromQL\" button is disabled\n2020625 - [AUTH-52] User fails to login from web console with keycloak OpenID IDP after enable group membership sync feature\n2020638 - [4.7] CI conformance test failures related to CustomResourcePublishOpenAPI\n2020664 - DOWN subports are not cleaned up\n2020904 - When trying to create a connection from the Developer view between VMs, it fails\n2021016 - \u0027Prometheus Stats\u0027 of dashboard \u0027Prometheus Overview\u0027 miss data on console compared with Grafana\n2021017 - 404 page not found error on knative eventing page\n2021031 - QE - Fix the topology CI scripts\n2021048 - [RFE] Added MAC Spoof check\n2021053 - Metallb operator presented as community operator\n2021067 - Extensive number of requests from storage version operator in cluster\n2021081 - Missing PolicyGenTemplate for configuring Local Storage Operator LocalVolumes\n2021135 - [azure-file-csi-driver] \"make unit-test\" returns non-zero code, but tests pass\n2021141 - Cluster should allow a fast rollout of kube-apiserver is failing on single node\n2021151 - Sometimes the DU node does not get the performance profile configuration applied and MachineConfigPool stays stuck in Updating\n2021152 - imagePullPolicy is \"Always\" for ptp operator images\n2021191 - Project admins should be able to list available network attachment defintions\n2021205 - Invalid URL in git import form causes validation to not happen on URL change\n2021322 - cluster-api-provider-azure should populate purchase plan information\n2021337 - Dynamic Plugins: ResourceLink doesn\u0027t render when passed a groupVersionKind\n2021364 - Installer requires invalid AWS permission s3:GetBucketReplication\n2021400 - Bump documentationBaseURL to 4.10\n2021405 - [e2e][automation] VM creation wizard Cloud Init editor\n2021433 - \"[sig-builds][Feature:Builds][pullsearch] docker build where the registry is not specified\" test fail permanently on disconnected\n2021466 - [e2e][automation] Windows guest tool mount\n2021544 - OCP 4.6.44 - Ingress VIP assigned as secondary IP in ovs-if-br-ex and added to resolv.conf as nameserver\n2021551 - Build is not recognizing the USER group from an s2i image\n2021607 - Unable to run openshift-install with a vcenter hostname that begins with a numeric character\n2021629 - api request counts for current hour are incorrect\n2021632 - [UI] Clicking on odf-operator breadcrumb from StorageCluster details page displays empty page\n2021693 - Modals assigned modal-lg class are no longer the correct width\n2021724 - Observe \u003e Dashboards: Graph lines are not visible when obscured by other lines\n2021731 - CCO occasionally down, reporting networksecurity.googleapis.com API as disabled\n2021936 - Kubelet version in RPMs should be using Dockerfile label instead of git tags\n2022050 - [BM][IPI] Failed during bootstrap - unable to read client-key /var/lib/kubelet/pki/kubelet-client-current.pem\n2022053 - dpdk application with vhost-net is not able to start\n2022114 - Console logging every proxy request\n2022144 - 1 of 3 ovnkube-master pods stuck in clbo after ipi bm deployment - dualstack  (Intermittent)\n2022251 - wait interval in case of a failed upload due to 403 is unnecessarily long\n2022399 - MON_DISK_LOW troubleshooting guide link when clicked, gives 404 error . \n2022447 - ServiceAccount in manifests conflicts with OLM\n2022502 - Patternfly tables with a checkbox column are not displaying correctly because of conflicting css rules. \n2022509 - getOverrideForManifest does not check manifest.GVK.Group\n2022536 - WebScale: duplicate ecmp next hop error caused by multiple of the same gateway IPs in ovnkube cache\n2022612 - no namespace field for \"Kubernetes / Compute Resources / Namespace (Pods)\" admin console dashboard\n2022627 - Machine object not picking up external FIP added to an openstack vm\n2022646 - configure-ovs.sh failure -  Error: unknown connection \u0027WARN:\u0027\n2022707 - Observe / monitoring dashboard shows forbidden errors on Dev Sandbox\n2022801 - Add Sprint 210 translations\n2022811 - Fix kubelet log rotation file handle leak\n2022812 - [SCALE] ovn-kube service controller executes unnecessary load balancer operations\n2022824 - Large number of sessions created by vmware-vsphere-csi-driver-operator during e2e tests\n2022880 - Pipeline renders with minor visual artifact with certain task dependencies\n2022886 - Incorrect URL in operator description\n2023042 - CRI-O filters custom runtime allowed annotation when both custom workload and custom runtime sections specified under the config\n2023060 - [e2e][automation] Windows VM with CDROM migration\n2023077 - [e2e][automation] Home Overview Virtualization status\n2023090 - [e2e][automation] Examples of Import URL for VM templates\n2023102 - [e2e][automation] Cloudinit disk of VM from custom template\n2023216 - ACL for a deleted egressfirewall still present on node join switch\n2023228 - Remove Tech preview badge on Trigger components 1.6 OSP on OCP 4.9\n2023238 - [sig-devex][Feature:ImageEcosystem][python][Slow] hot deploy for openshift python image  Django example should work with hot deploy\n2023342 - SCC admission should take ephemeralContainers into account\n2023356 - Devfiles can\u0027t be loaded in Safari on macOS (403 - Forbidden)\n2023434 - Update Azure Machine Spec API to accept Marketplace Images\n2023500 - Latency experienced while waiting for volumes to attach to node\n2023522 - can\u0027t remove package from index: database is locked\n2023560 - \"Network Attachment Definitions\" has no project field on the top in the list view\n2023592 - [e2e][automation] add mac spoof check for nad\n2023604 - ACL violation when deleting a provisioning-configuration resource\n2023607 - console returns blank page when normal user without any projects visit Installed Operators page\n2023638 - Downgrade support level for extended control plane integration to Dev Preview\n2023657 - inconsistent behaviours of adding ssh key on rhel node between 4.9 and 4.10\n2023675 - Changing CNV Namespace\n2023779 - Fix Patch 104847 in 4.9\n2023781 - initial hardware devices is not loading in wizard\n2023832 - CCO updates lastTransitionTime for non-Status changes\n2023839 - Bump recommended FCOS to 34.20211031.3.0\n2023865 - Console css overrides prevent dynamic plug-in PatternFly tables from displaying correctly\n2023950 - make test-e2e-operator on kubernetes-nmstate results in failure to pull image from \"registry:5000\" repository\n2023985 - [4.10] OVN idle service cannot be accessed after upgrade from 4.8\n2024055 - External DNS added extra prefix for the TXT record\n2024108 - Occasionally node remains in SchedulingDisabled state even after update has been completed sucessfully\n2024190 - e2e-metal UPI is permafailing with inability to find rhcos.json\n2024199 - 400 Bad Request error for some queries for the non admin user\n2024220 - Cluster monitoring checkbox flickers when installing Operator in all-namespace mode\n2024262 - Sample catalog is not displayed when one API call to the backend fails\n2024309 - cluster-etcd-operator: defrag controller needs to provide proper observability\n2024316 - modal about support displays wrong annotation\n2024328 - [oVirt / RHV] PV disks are lost when machine deleted while node is disconnected\n2024399 - Extra space is in the translated text of \"Add/Remove alternate service\" on Create Route page\n2024448 - When ssh_authorized_keys is empty in form view it should not appear in yaml view\n2024493 - Observe \u003e Alerting \u003e Alerting rules page throws error trying to destructure undefined\n2024515 - test-blocker: Ceph-storage-plugin tests failing\n2024535 - hotplug disk missing OwnerReference\n2024537 - WINDOWS_IMAGE_LINK does not refer to windows cloud image\n2024547 - Detail page is breaking for namespace store , backing store and bucket class. \n2024551 - KMS resources not getting created for IBM FlashSystem storage\n2024586 - Special Resource Operator(SRO) - Empty image in BuildConfig when using RT kernel\n2024613 - pod-identity-webhook starts without tls\n2024617 - vSphere CSI tests constantly failing with Rollout of the monitoring stack failed and is degraded\n2024665 - Bindable services are not shown on topology\n2024731 - linuxptp container: unnecessary checking of interfaces\n2024750 - i18n some remaining OLM items\n2024804 - gcp-pd-csi-driver does not use trusted-ca-bundle when cluster proxy configured\n2024826 - [RHOS/IPI] Masters are not joining a clusters when installing on OpenStack\n2024841 - test Keycloak with latest tag\n2024859 - Not able to deploy an existing image from private image registry using developer console\n2024880 - Egress IP breaks when network policies are applied\n2024900 - Operator upgrade kube-apiserver\n2024932 - console throws \"Unauthorized\" error after logging out\n2024933 - openshift-sync plugin does not sync existing secrets/configMaps on start up\n2025093 - Installer does not honour diskformat specified in storage policy and defaults to zeroedthick\n2025230 - ClusterAutoscalerUnschedulablePods should not be a warning\n2025266 - CreateResource route has exact prop which need to be removed\n2025301 - [e2e][automation] VM actions availability in different VM states\n2025304 - overwrite storage section of the DV spec instead of the pvc section\n2025431 - [RFE]Provide specific windows source link\n2025458 - [IPI-AWS] cluster-baremetal-operator pod in a crashloop state after patching from 4.7.21 to 4.7.36\n2025464 - [aws] openshift-install gather bootstrap collects logs for bootstrap and only one master node\n2025467 - [OVN-K][ETP=local] Host to service backed by ovn pods doesn\u0027t work for ExternalTrafficPolicy=local\n2025481 - Update VM Snapshots UI\n2025488 - [DOCS] Update the doc for nmstate operator installation\n2025592 - ODC 4.9 supports invalid devfiles only\n2025765 - It should not try to load from storageProfile after unchecking\"Apply optimized StorageProfile settings\"\n2025767 - VMs orphaned during machineset scaleup\n2025770 - [e2e] non-priv seems looking for v2v-vmware configMap in ns \"kubevirt-hyperconverged\" while using customize wizard\n2025788 - [IPI on azure]Pre-check on IPI Azure, should check VM Size\u2019s vCPUsAvailable instead of vCPUs for the sku. \n2025821 - Make \"Network Attachment Definitions\" available to regular user\n2025823 - The console nav bar ignores plugin separator in existing sections\n2025830 - CentOS capitalizaion is wrong\n2025837 - Warn users that the RHEL URL expire\n2025884 - External CCM deploys openstack-cloud-controller-manager from quay.io/openshift/origin-*\n2025903 - [UI] RoleBindings tab doesn\u0027t show correct rolebindings\n2026104 - [sig-imageregistry][Feature:ImageAppend] Image append should create images by appending them [Skipped:Disconnected] [Suite:openshift/conformance/parallel]\n2026178 - OpenShift Alerting Rules Style-Guide Compliance\n2026209 - Updation of task is getting failed (tekton hub integration)\n2026223 - Internal error occurred: failed calling webhook \"ptpconfigvalidationwebhook.openshift.io\"\n2026321 - [UPI on Azure] Shall we remove allowedValue about VMSize in ARM templates\n2026343 - [upgrade from 4.5 to 4.6] .status.connectionState.address of catsrc community-operators is not correct\n2026352 - Kube-Scheduler revision-pruner fail during install of new cluster\n2026374 - aws-pod-identity-webhook go.mod version out of sync with build environment\n2026383 - Error when rendering custom Grafana dashboard through ConfigMap\n2026387 - node tuning operator metrics endpoint serving old certificates after certificate rotation\n2026396 - Cachito Issues: sriov-network-operator Image build failure\n2026488 - openshift-controller-manager - delete event is repeating pathologically\n2026489 - ThanosRuleRuleEvaluationLatencyHigh alerts when a big quantity of alerts defined. \n2026560 - Cluster-version operator does not remove unrecognized volume mounts\n2026699 - fixed a bug with missing metadata\n2026813 - add Mellanox CX-6 Lx DeviceID 101f NIC support in SR-IOV Operator\n2026898 - Description/details are missing for Local Storage Operator\n2027132 - Use the specific icon for Fedora and CentOS template\n2027238 - \"Node Exporter / USE Method / Cluster\" CPU utilization graph shows incorrect legend\n2027272 - KubeMemoryOvercommit alert should be human readable\n2027281 - [Azure] External-DNS cannot find the private DNS zone in the resource group\n2027288 - Devfile samples can\u0027t be loaded after fixing it on Safari (redirect caching issue)\n2027299 - The status of checkbox component is not revealed correctly in code\n2027311 - K8s watch hooks do not work when fetching core resources\n2027342 - Alert ClusterVersionOperatorDown is firing on OpenShift Container Platform after ca certificate rotation\n2027363 - The azure-file-csi-driver and azure-file-csi-driver-operator don\u0027t use the downstream images\n2027387 - [IBMCLOUD] Terraform ibmcloud-provider buffers entirely the qcow2 image causing spikes of 5GB of RAM during installation\n2027498 - [IBMCloud] SG Name character length limitation\n2027501 - [4.10] Bootimage bump tracker\n2027524 - Delete Application doesn\u0027t delete Channels or Brokers\n2027563 - e2e/add-flow-ci.feature fix accessibility violations\n2027585 - CVO crashes when changing spec.upstream to a cincinnati graph which includes invalid conditional edges\n2027629 - Gather ValidatingWebhookConfiguration and MutatingWebhookConfiguration resource definitions\n2027685 - openshift-cluster-csi-drivers pods crashing on PSI\n2027745 - default samplesRegistry prevents the creation of imagestreams when registrySources.allowedRegistries is enforced\n2027824 - ovnkube-master CrashLoopBackoff: panic: Expected slice or struct but got string\n2027917 - No settings in hostfirmwaresettings and schema objects for masters\n2027927 - sandbox creation fails due to obsolete option in /etc/containers/storage.conf\n2027982 - nncp stucked at ConfigurationProgressing\n2028019 - Max pending serving CSRs allowed in cluster machine approver is not right for UPI clusters\n2028024 - After deleting a SpecialResource, the node is still tagged although the driver is removed\n2028030 - Panic detected in cluster-image-registry-operator pod\n2028042 - Desktop viewer for Windows VM shows \"no Service for the RDP (Remote Desktop Protocol) can be found\"\n2028054 - Cloud controller manager operator can\u0027t get leader lease when upgrading from 4.8 up to 4.9\n2028106 - [RFE] Use dynamic plugin actions for kubevirt plugin\n2028141 - Console tests doesn\u0027t pass on Node.js 15 and 16\n2028160 - Remove i18nKey in network-policy-peer-selectors.tsx\n2028162 - Add Sprint 210 translations\n2028170 - Remove leading and trailing whitespace\n2028174 - Add Sprint 210 part 2 translations\n2028187 - Console build doesn\u0027t pass on Node.js 16 because node-sass doesn\u0027t support it\n2028217 - Cluster-version operator does not default Deployment replicas to one\n2028240 - Multiple CatalogSources causing higher CPU use than necessary\n2028268 - Password parameters are listed in FirmwareSchema in spite that cannot and shouldn\u0027t be set in HostFirmwareSettings\n2028325 - disableDrain should be set automatically on SNO\n2028484 - AWS EBS CSI driver\u0027s livenessprobe does not respect operator\u0027s loglevel\n2028531 - Missing netFilter to the list of parameters when platform is OpenStack\n2028610 - Installer doesn\u0027t retry on GCP rate limiting\n2028685 - LSO repeatedly reports errors while diskmaker-discovery pod is starting\n2028695 - destroy cluster does not prune bootstrap instance profile\n2028731 - The containerruntimeconfig controller has wrong assumption regarding the number of containerruntimeconfigs\n2028802 - CRI-O panic due to invalid memory address or nil pointer dereference\n2028816 - VLAN IDs not released on failures\n2028881 - Override not working for the PerformanceProfile template\n2028885 - Console should show an error context if it logs an error object\n2028949 - Masthead dropdown item hover text color is incorrect\n2028963 - Whereabouts should reconcile stranded IP addresses\n2029034 - enabling ExternalCloudProvider leads to inoperative cluster\n2029178 - Create VM with wizard - page is not displayed\n2029181 - Missing CR from PGT\n2029273 - wizard is not able to use if project field is \"All Projects\"\n2029369 - Cypress tests github rate limit errors\n2029371 - patch pipeline--worker nodes unexpectedly reboot during scale out\n2029394 - missing empty text for hardware devices at wizard review\n2029414 - Alibaba Disk snapshots with XFS filesystem cannot be used\n2029416 - Alibaba Disk CSI driver does not use credentials provided by CCO / ccoctl\n2029521 - EFS CSI driver cannot delete volumes under load\n2029570 - Azure Stack Hub: CSI Driver does not use user-ca-bundle\n2029579 - Clicking on an Application which has a Helm Release in it causes an error\n2029644 - New resource FirmwareSchema - reset_required exists for Dell machines and doesn\u0027t for HPE\n2029645 - Sync upstream 1.15.0 downstream\n2029671 - VM action \"pause\" and \"clone\" should be disabled while VM disk is still being importing\n2029742 - [ovn] Stale lr-policy-list  and snat rules left for egressip\n2029750 - cvo keep restart due to it fail to get feature gate value during the initial start stage\n2029785 - CVO panic when an edge is included in both edges and conditionaledges\n2029843 - Downstream ztp-site-generate-rhel8 4.10 container image missing content(/home/ztp)\n2030003 - HFS CRD: Attempt to set Integer parameter to not-numeric string value - no error\n2030029 - [4.10][goroutine]Namespace stuck terminating: Failed to delete all resource types, 1 remaining: unexpected items still remain in namespace\n2030228 - Fix StorageSpec resources field to use correct API\n2030229 - Mirroring status card reflect wrong data\n2030240 - Hide overview page for non-privileged user\n2030305 - Export App job do not completes\n2030347 - kube-state-metrics exposes metrics about resource annotations\n2030364 - Shared resource CSI driver monitoring is not setup correctly\n2030488 - Numerous Azure CI jobs are Failing with Partially Rendered machinesets\n2030534 - Node selector/tolerations rules are evaluated too early\n2030539 - Prometheus is not highly available\n2030556 - Don\u0027t display Description or Message fields for alerting rules if those annotations are missing\n2030568 - Operator installation fails to parse operatorframework.io/initialization-resource annotation\n2030574 - console service uses older \"service.alpha.openshift.io\" for the service serving certificates. \n2030677 - BOND CNI: There is no option to configure MTU on a Bond interface\n2030692 - NPE in PipelineJobListener.upsertWorkflowJob\n2030801 - CVE-2021-44716 golang: net/http: limit growth of header canonicalization cache\n2030806 - CVE-2021-44717 golang: syscall: don\u0027t close fd 0 on ForkExec error\n2030847 - PerformanceProfile API version should be v2\n2030961 - Customizing the OAuth server URL does not apply to upgraded cluster\n2031006 - Application name input field is not autofocused when user selects \"Create application\"\n2031012 - Services of type loadbalancer do not work if the traffic reaches the node from an interface different from br-ex\n2031040 - Error screen when open topology sidebar for a Serverless / knative service which couldn\u0027t be started\n2031049 - [vsphere upi] pod machine-config-operator cannot be started due to panic issue\n2031057 - Topology sidebar for Knative services shows a small pod ring with \"0 undefined\" as tooltip\n2031060 - Failing CSR Unit test due to expired test certificate\n2031085 - ovs-vswitchd running more threads than expected\n2031141 - Some pods not able to reach k8s api svc IP 198.223.0.1\n2031228 - CVE-2021-43813 grafana: directory traversal vulnerability\n2031502 - [RFE] New common templates crash the ui\n2031685 - Duplicated forward upstreams should be removed from the dns operator\n2031699 - The displayed ipv6 address of a dns upstream should be case sensitive\n2031797 - [RFE] Order and text of Boot source type input are wrong\n2031826 - CI tests needed to confirm driver-toolkit image contents\n2031831 - OCP Console - Global CSS overrides affecting dynamic plugins\n2031839 - Starting from Go 1.17 invalid certificates will render a cluster dysfunctional\n2031858 - GCP beta-level Role (was: CCO occasionally down, reporting networksecurity.googleapis.com API as disabled)\n2031875 - [RFE]: Provide online documentation for the SRO CRD (via oc explain)\n2031926 - [ipv6dualstack] After SVC conversion from single stack only to RequireDualStack, cannot curl NodePort from the node itself\n2032006 - openshift-gitops-application-controller-0 failed to schedule with sufficient node allocatable resource\n2032111 - arm64 cluster, create project and deploy the example deployment, pod is CrashLoopBackOff due to the image is built on linux+amd64\n2032141 - open the alertrule link in new tab, got empty page\n2032179 - [PROXY] external dns pod cannot reach to cloud API in the cluster behind a proxy\n2032296 - Cannot create machine with ephemeral disk on Azure\n2032407 - UI will show the default openshift template wizard for HANA template\n2032415 - Templates page - remove \"support level\" badge and add \"support level\" column which should not be hard coded\n2032421 - [RFE] UI integration with automatic updated images\n2032516 - Not able to import git repo with .devfile.yaml\n2032521 - openshift-installer intermittent failure on AWS with \"Error: Provider produced inconsistent result after apply\" when creating the aws_vpc_dhcp_options_association resource\n2032547 - hardware devices table have filter when table is empty\n2032565 - Deploying compressed files with a MachineConfig resource degrades the MachineConfigPool\n2032566 - Cluster-ingress-router does not support Azure Stack\n2032573 - Adopting enforces deploy_kernel/ramdisk which does not work with deploy_iso\n2032589 - DeploymentConfigs ignore resolve-names annotation\n2032732 - Fix styling conflicts due to recent console-wide CSS changes\n2032831 - Knative Services and Revisions are not shown when Service has no ownerReference\n2032851 - Networking is \"not available\" in Virtualization Overview\n2032926 - Machine API components should use K8s 1.23 dependencies\n2032994 - AddressPool IP is not allocated to service external IP wtih aggregationLength 24\n2032998 - Can not achieve 250 pods/node with OVNKubernetes in a multiple worker node cluster\n2033013 - Project dropdown in user preferences page is broken\n2033044 - Unable to change import strategy if devfile is invalid\n2033098 - Conjunction in ProgressiveListFooter.tsx is not translatable\n2033111 - IBM VPC operator library bump removed global CLI args\n2033138 - \"No model registered for Templates\" shows on customize wizard\n2033215 - Flaky CI: crud/other-routes.spec.ts fails sometimes with an cypress ace/a11y AssertionError: 1 accessibility violation was detected\n2033239 - [IPI on Alibabacloud] \u0027openshift-install\u0027 gets the wrong region (\u2018cn-hangzhou\u2019) selected\n2033257 - unable to use configmap for helm charts\n2033271 - [IPI on Alibabacloud] destroying cluster succeeded, but the resource group deletion wasn\u2019t triggered\n2033290 - Product builds for console are failing\n2033382 - MAPO is missing machine annotations\n2033391 - csi-driver-shared-resource-operator sets unused CVO-manifest annotations\n2033403 - Devfile catalog does not show provider information\n2033404 - Cloud event schema is missing source type and resource field is using wrong value\n2033407 - Secure route data is not pre-filled in edit flow form\n2033422 - CNO not allowing LGW conversion from SGW in runtime\n2033434 - Offer darwin/arm64 oc in clidownloads\n2033489 - CCM operator failing on baremetal platform\n2033518 - [aws-efs-csi-driver]Should not accept invalid FSType in sc for AWS EFS driver\n2033524 - [IPI on Alibabacloud] interactive installer cannot list existing base domains\n2033536 - [IPI on Alibabacloud] bootstrap complains invalid value for alibabaCloud.resourceGroupID when updating \"cluster-infrastructure-02-config.yml\" status, which leads to bootstrap failed and all master nodes NotReady\n2033538 - Gather Cost Management Metrics Custom Resource\n2033579 - SRO cannot update the special-resource-lifecycle ConfigMap if the data field is undefined\n2033587 - Flaky CI test project-dashboard.scenario.ts: Resource Quotas Card was not found on project detail page\n2033634 - list-style-type: disc is applied to the modal dropdowns\n2033720 - Update samples in 4.10\n2033728 - Bump OVS to 2.16.0-33\n2033729 - remove runtime request timeout restriction for azure\n2033745 - Cluster-version operator makes upstream update service / Cincinnati requests more frequently than intended\n2033749 - Azure Stack Terraform fails without Local Provider\n2033750 - Local volume should pull multi-arch image for kube-rbac-proxy\n2033751 - Bump kubernetes to 1.23\n2033752 - make verify fails due to missing yaml-patch\n2033784 - set kube-apiserver degraded=true if webhook matches a virtual resource\n2034004 - [e2e][automation] add tests for VM snapshot improvements\n2034068 - [e2e][automation] Enhance tests for 4.10 downstream\n2034087 - [OVN] EgressIP was assigned to the node which is not egress node anymore\n2034097 - [OVN] After edit EgressIP object, the status is not correct\n2034102 - [OVN] Recreate the  deleted EgressIP object got  InvalidEgressIP  warning\n2034129 - blank page returned when clicking \u0027Get started\u0027 button\n2034144 - [OVN AWS] ovn-kube egress IP monitoring cannot detect the failure on ovn-k8s-mp0\n2034153 - CNO does not verify MTU migration for OpenShiftSDN\n2034155 - [OVN-K] [Multiple External Gateways] Per pod SNAT is disabled\n2034170 - Use function.knative.dev for Knative Functions related labels\n2034190 - unable to add new VirtIO disks to VMs\n2034192 - Prometheus fails to insert reporting metrics when the sample limit is met\n2034243 - regular user cant load template list\n2034245 - installing a cluster on aws, gcp always fails with \"Error: Incompatible provider version\"\n2034248 - GPU/Host device modal is too small\n2034257 - regular user `Create VM` missing permissions alert\n2034285 - [sig-api-machinery] API data in etcd should be stored at the correct location and version for all resources [Serial] [Suite:openshift/conformance/serial]\n2034287 - do not block upgrades if we can\u0027t create storageclass in 4.10 in vsphere\n2034300 - Du validator policy is NonCompliant after DU configuration completed\n2034319 - Negation constraint is not validating packages\n2034322 - CNO doesn\u0027t pick up settings required when ExternalControlPlane topology\n2034350 - The CNO should implement the Whereabouts IP reconciliation cron job\n2034362 - update description of disk interface\n2034398 - The Whereabouts IPPools CRD should include the podref field\n2034409 - Default CatalogSources should be pointing to 4.10 index images\n2034410 - Metallb BGP, BFD:  prometheus is not scraping the frr metrics\n2034413 - cloud-network-config-controller fails to init with secret \"cloud-credentials\" not found in manual credential mode\n2034460 - Summary: cloud-network-config-controller does not account for different environment\n2034474 - Template\u0027s boot source is \"Unknown source\" before and after set enableCommonBootImageImport to true\n2034477 - [OVN] Multiple EgressIP objects configured, EgressIPs weren\u0027t working properly\n2034493 - Change cluster version operator log level\n2034513 - [OVN] After update one EgressIP in EgressIP object, one internal IP lost from lr-policy-list\n2034527 - IPI deployment fails \u0027timeout reached while inspecting the node\u0027 when provisioning network ipv6\n2034528 - [IBM VPC] volumeBindingMode should be WaitForFirstConsumer\n2034534 - Update ose-machine-api-provider-openstack images to be consistent with ART\n2034537 - Update team\n2034559 - KubeAPIErrorBudgetBurn firing outside recommended latency thresholds\n2034563 - [Azure] create machine with wrong ephemeralStorageLocation value success\n2034577 - Current OVN gateway mode should be reflected on node annotation as well\n2034621 - context menu not popping up for application group\n2034622 - Allow volume expansion by default in vsphere CSI storageclass 4.10\n2034624 - Warn about unsupported CSI driver in vsphere operator\n2034647 - missing volumes list in snapshot modal\n2034648 - Rebase openshift-controller-manager to 1.23\n2034650 - Rebase openshift/builder to 1.23\n2034705 - vSphere: storage e2e tests logging configuration data\n2034743 - EgressIP: assigning the same egress IP to a second EgressIP object after a ovnkube-master restart does not fail. \n2034766 - Special Resource Operator(SRO) -  no cert-manager pod created in dual stack environment\n2034785 - ptpconfig with summary_interval cannot be applied\n2034823 - RHEL9 should be starred in template list\n2034838 - An external router can inject routes if no service is added\n2034839 - Jenkins sync plugin does not synchronize ConfigMap having label role=jenkins-agent\n2034879 - Lifecycle hook\u0027s name and owner shouldn\u0027t be allowed to be empty\n2034881 - Cloud providers components should use K8s 1.23 dependencies\n2034884 - ART cannot build the image because it tries to download controller-gen\n2034889 - `oc adm prune deployments` does not work\n2034898 - Regression in recently added Events feature\n2034957 - update openshift-apiserver to kube 1.23.1\n2035015 - ClusterLogForwarding CR remains stuck remediating forever\n2035093 - openshift-cloud-network-config-controller never runs on Hypershift cluster\n2035141 - [RFE] Show GPU/Host devices in template\u0027s details tab\n2035146 - \"kubevirt-plugin~PVC cannot be empty\" shows on add-disk modal while adding existing PVC\n2035167 - [cloud-network-config-controller] unable to deleted cloudprivateipconfig when deleting\n2035199 - IPv6 support in mtu-migration-dispatcher.yaml\n2035239 - e2e-metal-ipi-virtualmedia tests are permanently failing\n2035250 - Peering with ebgp peer over multi-hops doesn\u0027t work\n2035264 - [RFE] Provide a proper message for nonpriv user who not able to add PCI devices\n2035315 - invalid test cases for AWS passthrough mode\n2035318 - Upgrade management workflow needs to allow custom upgrade graph path for disconnected env\n2035321 - Add Sprint 211 translations\n2035326 - [ExternalCloudProvider] installation with additional network on workers fails\n2035328 - Ccoctl does not ignore credentials request manifest marked for deletion\n2035333 - Kuryr orphans ports on 504 errors from Neutron\n2035348 - Fix two grammar issues in kubevirt-plugin.json strings\n2035393 - oc set data --dry-run=server  makes persistent changes to configmaps and secrets\n2035409 - OLM E2E test depends on operator package that\u0027s no longer published\n2035439 - SDN  Automatic assignment EgressIP on GCP returned node IP adress not egressIP address\n2035453 - [IPI on Alibabacloud] 2 worker machines stuck in Failed phase due to connection to \u0027ecs-cn-hangzhou.aliyuncs.com\u0027 timeout, although the specified region is \u0027us-east-1\u0027\n2035454 - [IPI on Alibabacloud] the OSS bucket created during installation for image registry is not deleted after destroying the cluster\n2035467 - UI: Queried metrics can\u0027t be ordered on Oberve-\u003eMetrics page\n2035494 - [SDN Migration]ovnkube-node pods CrashLoopBackOff after sdn migrated to ovn for RHEL workers\n2035515 - [IBMCLOUD] allowVolumeExpansion should be true in storage class\n2035602 - [e2e][automation] add tests for Virtualization Overview page cards\n2035703 - Roles -\u003e RoleBindings tab doesn\u0027t show RoleBindings correctly\n2035704 - RoleBindings list page filter doesn\u0027t apply\n2035705 - Azure \u0027Destroy cluster\u0027 get stuck when the cluster resource group is already not existing. \n2035757 - [IPI on Alibabacloud] one master node turned NotReady which leads to installation failed\n2035772 - AccessMode and VolumeMode is not reserved for customize wizard\n2035847 - Two dashes in the Cronjob / Job pod name\n2035859 - the output of opm render doesn\u0027t contain  olm.constraint which is defined in dependencies.yaml\n2035882 - [BIOS setting values] Create events for all invalid settings in spec\n2035903 - One redundant capi-operator credential requests in \u201coc adm extract --credentials-requests\u201d\n2035910 - [UI] Manual approval options are missing after ODF 4.10 installation starts when Manual Update approval is chosen\n2035927 - Cannot enable HighNodeUtilization scheduler profile\n2035933 - volume mode and access mode are empty in customize wizard review tab\n2035969 - \"ip a \" shows \"Error: Peer netns reference is invalid\" after create test pods\n2035986 - Some pods under kube-scheduler/kube-controller-manager are using the deprecated annotation\n2036006 - [BIOS setting values] Attempt to set Integer parameter results in preparation error\n2036029 - New added cloud-network-config operator doesn\u2019t supported aws sts format credential\n2036096 - [azure-file-csi-driver] there are no e2e tests for NFS backend\n2036113 - cluster scaling new nodes ovs-configuration fails on all new nodes\n2036567 - [csi-driver-nfs] Upstream merge: Bump k8s libraries to 1.23\n2036569 - [cloud-provider-openstack] Upstream merge: Bump k8s libraries to 1.23\n2036577 - OCP 4.10 nightly builds from 4.10.0-0.nightly-s390x-2021-12-18-034912 to 4.10.0-0.nightly-s390x-2022-01-11-233015 fail to upgrade from OCP 4.9.11 and 4.9.12 for network type OVNKubernetes for zVM hypervisor environments\n2036622 - sdn-controller crashes when restarted while a previous egress IP assignment exists\n2036717 - Valid AlertmanagerConfig custom resource with valid a mute time interval definition is rejected\n2036826 - `oc adm prune deployments` can prune the RC/RS\n2036827 - The ccoctl still accepts CredentialsRequests without ServiceAccounts on GCP platform\n2036861 - kube-apiserver is degraded while enable multitenant\n2036937 - Command line tools page shows wrong download ODO link\n2036940 - oc registry login fails if the file is empty or stdout\n2036951 - [cluster-csi-snapshot-controller-operator] proxy settings is being injected in container\n2036989 - Route URL copy to clipboard button wraps to a separate line by itself\n2036990 - ZTP \"DU Done inform policy\" never becomes compliant on multi-node clusters\n2036993 - Machine API components should use Go lang version 1.17\n2037036 - The tuned profile goes into degraded status and ksm.service is displayed in the log. \n2037061 - aws and gcp CredentialsRequest manifests missing ServiceAccountNames list for cluster-api\n2037073 - Alertmanager container fails to start because of startup probe never being successful\n2037075 - Builds do not support CSI volumes\n2037167 - Some log level in ibm-vpc-block-csi-controller are hard code\n2037168 - IBM-specific Deployment manifest for package-server-manager should be excluded on non-IBM cluster-profiles\n2037182 - PingSource badge color is not matched with knativeEventing color\n2037203 - \"Running VMs\" card is too small in Virtualization Overview\n2037209 - [IPI on Alibabacloud] worker nodes are put in the default resource group unexpectedly\n2037237 - Add \"This is a CD-ROM boot source\" to customize wizard\n2037241 - default TTL for noobaa cache buckets should be 0\n2037246 - Cannot customize auto-update boot source\n2037276 - [IBMCLOUD] vpc-node-label-updater may fail to label nodes appropriately\n2037288 - Remove stale image reference\n2037331 - Ensure the ccoctl behaviors are similar between aws and gcp on the existing resources\n2037483 - Rbacs for Pods within the CBO should be more restrictive\n2037484 - Bump dependencies to k8s 1.23\n2037554 - Mismatched wave number error message should include the wave numbers that are in conflict\n2037622 - [4.10-Alibaba CSI driver][Restore size for volumesnapshot/volumesnapshotcontent is showing as 0 in Snapshot feature for Alibaba platform]\n2037635 - impossible to configure custom certs for default console route in ingress config\n2037637 - configure custom certificate for default console route doesn\u0027t take effect for OCP \u003e= 4.8\n2037638 - Builds do not support CSI volumes as volume sources\n2037664 - text formatting issue in Installed Operators list table\n2037680 - [IPI on Alibabacloud] sometimes operator \u0027cloud-controller-manager\u0027 tells empty VERSION, due to conflicts on listening tcp :8080\n2037689 - [IPI on Alibabacloud] sometimes operator \u0027cloud-controller-manager\u0027 tells empty VERSION, due to conflicts on listening tcp :8080\n2037801 - Serverless installation is failing on CI jobs for e2e tests\n2037813 - Metal Day 1 Networking -  networkConfig Field Only Accepts String Format\n2037856 - use lease for leader election\n2037891 - 403 Forbidden error shows for all the graphs in each grafana dashboard after upgrade from 4.9 to 4.10\n2037903 - Alibaba Cloud: delete-ram-user requires the credentials-requests\n2037904 - upgrade operator deployment failed due to memory limit too low for manager container\n2038021 - [4.10-Alibaba CSI driver][Default volumesnapshot class is not added/present after successful cluster installation]\n2038034 - non-privileged user cannot see auto-update boot source\n2038053 - Bump dependencies to k8s 1.23\n2038088 - Remove ipa-downloader references\n2038160 - The `default` project missed the annotation : openshift.io/node-selector: \"\"\n2038166 - Starting from Go 1.17 invalid certificates will render a cluster non-functional\n2038196 - must-gather is missing collecting some metal3 resources\n2038240 - Error when configuring a file using permissions bigger than decimal 511 (octal 0777)\n2038253 - Validator Policies are long lived\n2038272 - Failures to build a PreprovisioningImage are not reported\n2038384 - Azure Default Instance Types are Incorrect\n2038389 - Failing test: [sig-arch] events should not repeat pathologically\n2038412 - Import page calls the git file list unnecessarily twice from GitHub/GitLab/Bitbucket\n2038465 - Upgrade chromedriver to 90.x to support Mac M1 chips\n2038481 - kube-controller-manager-guard and openshift-kube-scheduler-guard pods being deleted and restarted on a cordoned node when drained\n2038596 - Auto egressIP for OVN cluster on GCP: After egressIP object is deleted, egressIP still takes effect\n2038663 - update kubevirt-plugin OWNERS\n2038691 - [AUTH-8] Panic on user login when the user belongs to a group in the IdP side and the group already exists via \"oc adm groups new\"\n2038705 - Update ptp reviewers\n2038761 - Open Observe-\u003eTargets page, wait for a while, page become blank\n2038768 - All the filters on the Observe-\u003eTargets page can\u0027t work\n2038772 - Some monitors failed to display on Observe-\u003eTargets page\n2038793 - [SDN EgressIP] After reboot egress node, the egressip was lost from egress node\n2038827 - should add user containers in /etc/subuid and /etc/subgid to support run pods in user namespaces\n2038832 - New templates for centos stream8 are missing registry suggestions in create vm wizard\n2038840 - [SDN EgressIP]cloud-network-config-controller pod was CrashLoopBackOff after some operation\n2038864 - E2E tests fail because multi-hop-net was not created\n2038879 - All Builds are getting listed in DeploymentConfig under workloads on OpenShift Console\n2038934 - CSI driver operators should use the trusted CA bundle when cluster proxy is configured\n2038968 - Move feature gates from a carry patch to openshift/api\n2039056 - Layout issue with breadcrumbs on API explorer page\n2039057 - Kind column is not wide enough in API explorer page\n2039064 - Bulk Import e2e test flaking at a high rate\n2039065 - Diagnose and fix Bulk Import e2e test that was previously disabled\n2039085 - Cloud credential operator configuration failing to apply in hypershift/ROKS clusters\n2039099 - [OVN EgressIP GCP] After reboot egress node, egressip that was previously assigned got lost\n2039109 - [FJ OCP4.10 Bug]: startironic.sh failed to pull the image of image-customization container when behind a proxy\n2039119 - CVO hotloops on Service openshift-monitoring/cluster-monitoring-operator\n2039170 - [upgrade]Error shown on registry operator \"missing the cloud-provider-config configmap\" after upgrade\n2039227 - Improve image customization server parameter passing during installation\n2039241 - Improve image customization server parameter passing during installation\n2039244 - Helm Release revision history page crashes the UI\n2039294 - SDN controller metrics cannot be consumed correctly by prometheus\n2039311 - oc Does Not Describe Build CSI Volumes\n2039315 - Helm release list page should only fetch secrets for deployed charts\n2039321 - SDN controller metrics are not being consumed by prometheus\n2039330 - Create NMState button doesn\u0027t work in OperatorHub web console\n2039339 - cluster-ingress-operator should report Unupgradeable if user has modified the aws resources annotations\n2039345 - CNO does not verify the minimum MTU value for IPv6/dual-stack clusters. \n2039359 - `oc adm prune deployments` can\u0027t prune the RS  where the associated Deployment no longer exists\n2039382 - gather_metallb_logs does not have execution permission\n2039406 - logout from rest session after vsphere operator sync is finished\n2039408 - Add GCP region northamerica-northeast2 to allowed regions\n2039414 - Cannot see the weights increased for NodeAffinity, InterPodAffinity, TaintandToleration\n2039425 - No need to set KlusterletAddonConfig CR applicationManager-\u003eenabled: true in RAN ztp deployment\n2039491 - oc - git:// protocol used in unit tests\n2039516 - Bump OVN to ovn21.12-21.12.0-25\n2039529 - Project Dashboard Resource Quotas Card empty state test flaking at a high rate\n2039534 - Diagnose and fix Project Dashboard Resource Quotas Card test that was previously disabled\n2039541 - Resolv-prepender script duplicating entries\n2039586 - [e2e] update centos8 to centos stream8\n2039618 - VM created from SAP HANA template leads to 404 page if leave one network parameter empty\n2039619 - [AWS] In tree provisioner storageclass aws disk type should contain \u0027gp3\u0027 and csi provisioner storageclass default aws disk type should be \u0027gp3\u0027\n2039670 - Create PDBs for control plane components\n2039678 - Page goes blank when create image pull secret\n2039689 - [IPI on Alibabacloud] Pay-by-specification NAT is no longer supported\n2039743 - React missing key warning when open operator hub detail page (and maybe others as well)\n2039756 - React missing key warning when open KnativeServing details\n2039770 - Observe dashboard doesn\u0027t react on time-range changes after browser reload when perspective is changed in another tab\n2039776 - Observe dashboard shows nothing if the URL links to an non existing dashboard\n2039781 - [GSS] OBC is not visible by admin of a Project on Console\n2039798 - Contextual binding with Operator backed service creates visual connector instead of Service binding connector\n2039868 - Insights Advisor widget is not in the disabled state when the Insights Operator is disabled\n2039880 - Log level too low for control plane metrics\n2039919 - Add E2E test for router compression feature\n2039981 - ZTP for standard clusters installs stalld on master nodes\n2040132 - Flag --port has been deprecated, This flag has no effect now and will be removed in v1.24. You can use --secure-port instead\n2040136 - external-dns-operator pod keeps restarting and reports error: timed out waiting for cache to be synced\n2040143 - [IPI on Alibabacloud] suggest to remove region \"cn-nanjing\" or provide better error message\n2040150 - Update ConfigMap keys for IBM HPCS\n2040160 - [IPI on Alibabacloud] installation fails when region does not support pay-by-bandwidth\n2040285 - Bump build-machinery-go for console-operator to pickup change in yaml-patch repository\n2040357 - bump OVN to ovn-2021-21.12.0-11.el8fdp\n2040376 - \"unknown instance type\" error for supported m6i.xlarge instance\n2040394 - Controller: enqueue the failed configmap till services update\n2040467 - Cannot build ztp-site-generator container image\n2040504 - Change AWS EBS GP3 IOPS in MachineSet doesn\u0027t take affect in OpenShift 4\n2040521 - RouterCertsDegraded certificate could not validate route hostname v4-0-config-system-custom-router-certs.apps\n2040535 - Auto-update boot source is not available in customize wizard\n2040540 - ovs hardware offload: ovsargs format error when adding vf netdev name\n2040603 - rhel worker scaleup playbook failed because missing some dependency of podman\n2040616 - rolebindings page doesn\u0027t load for normal users\n2040620 - [MAPO] Error pulling MAPO image on installation\n2040653 - Topology sidebar warns that another component is updated while rendering\n2040655 - User settings update fails when selecting application in topology sidebar\n2040661 - Different react warnings about updating state on unmounted components when leaving topology\n2040670 - Permafailing CI job: periodic-ci-openshift-release-master-nightly-4.10-e2e-gcp-libvirt-cert-rotation\n2040671 - [Feature:IPv6DualStack] most tests are failing in dualstack ipi\n2040694 - Three upstream HTTPClientConfig struct fields missing in the operator\n2040705 - Du policy for standard cluster runs the PTP daemon on masters and workers\n2040710 - cluster-baremetal-operator cannot update BMC subscription CR\n2040741 - Add CI test(s) to ensure that metal3 components are deployed in vSphere, OpenStack and None platforms\n2040782 - Import YAML page blocks input with more then one generateName attribute\n2040783 - The Import from YAML summary page doesn\u0027t show the resource name if created via generateName attribute\n2040791 - Default PGT policies must be \u0027inform\u0027 to integrate with the Lifecycle Operator\n2040793 - Fix snapshot e2e failures\n2040880 - do not block upgrades if we can\u0027t connect to vcenter\n2041087 - MetalLB: MetalLB CR is not upgraded automatically from 4.9 to 4.10\n2041093 - autounattend.xml missing\n2041204 - link to templates in virtualization-cluster-overview inventory card is to all templates\n2041319 - [IPI on Alibabacloud] installation in region \"cn-shanghai\" failed, due to \"Resource alicloud_vswitch CreateVSwitch Failed...InvalidCidrBlock.Overlapped\"\n2041326 - Should bump cluster-kube-descheduler-operator to kubernetes version V1.23\n2041329 - aws and gcp CredentialsRequest manifests missing ServiceAccountNames list for cloud-network-config-controller\n2041361 - [IPI on Alibabacloud] Disable session persistence and removebBandwidth peak of listener\n2041441 - Provision volume with size 3000Gi even if sizeRange: \u0027[10-2000]GiB\u0027 in storageclass on IBM cloud\n2041466 - Kubedescheduler version is missing from the operator logs\n2041475 - React components should have a (mostly) unique name in react dev tools to simplify code analyses\n2041483 - MetallB: quay.io/openshift/origin-kube-rbac-proxy:4.10 deploy Metallb CR  is missing (controller and speaker pods)\n2041492 - Spacing between resources in inventory card is too small\n2041509 - GCP Cloud provider components should use K8s 1.23 dependencies\n2041510 - cluster-baremetal-operator doesn\u0027t run baremetal-operator\u0027s subscription webhook\n2041541 - audit: ManagedFields are dropped using API not annotation\n2041546 - ovnkube: set election timer at RAFT cluster creation time\n2041554 - use lease for leader election\n2041581 - KubeDescheduler operator log shows \"Use of insecure cipher detected\"\n2041583 - etcd and api server cpu mask interferes with a guaranteed workload\n2041598 - Including CA bundle in Azure Stack cloud config causes MCO failure\n2041605 - Dynamic Plugins: discrepancy in proxy alias documentation/implementation\n2041620 - bundle CSV alm-examples does not parse\n2041641 - Fix inotify leak and kubelet retaining memory\n2041671 - Delete templates leads to 404 page\n2041694 - [IPI on Alibabacloud] installation fails when region does not support the cloud_essd disk category\n2041734 - ovs hwol: VFs are unbind when switchdev mode is enabled\n2041750 - [IPI on Alibabacloud] trying \"create install-config\" with region \"cn-wulanchabu (China (Ulanqab))\" (or \"ap-southeast-6 (Philippines (Manila))\", \"cn-guangzhou (China (Guangzhou))\") failed due to invalid endpoint\n2041763 - The Observe \u003e Alerting pages no longer have their default sort order applied\n2041830 - CI: ovn-kubernetes-master-e2e-aws-ovn-windows is broken\n2041854 - Communities / Local prefs are applied to all the services regardless of the pool, and only one community is applied\n2041882 - cloud-network-config operator can\u0027t work normal on GCP workload identity cluster\n2041888 - Intermittent incorrect build to run correlation, leading to run status updates applied to wrong build, builds stuck in non-terminal phases\n2041926 - [IPI on Alibabacloud] Installer ignores public zone when it does not exist\n2041971 - [vsphere] Reconciliation of mutating webhooks didn\u0027t happen\n2041989 - CredentialsRequest manifests being installed for ibm-cloud-managed profile\n2041999 - [PROXY] external dns pod cannot recognize custom proxy CA\n2042001 - unexpectedly found multiple load balancers\n2042029 - kubedescheduler fails to install completely\n2042036 - [IBMCLOUD] \"openshift-install explain installconfig.platform.ibmcloud\" contains not yet supported custom vpc parameters\n2042049 - Seeing warning related to unrecognized feature gate in kubescheduler \u0026 KCM logs\n2042059 - update discovery burst to reflect lots of CRDs on openshift clusters\n2042069 - Revert toolbox to rhcos-toolbox\n2042169 - Can not delete egressnetworkpolicy in Foreground propagation\n2042181 - MetalLB: User should not be allowed add same bgp advertisement twice in BGP address pool\n2042265 - [IBM]\"--scale-down-utilization-threshold\" doesn\u0027t work on IBMCloud\n2042274 - Storage API should be used when creating a PVC\n2042315 - Baremetal IPI deployment with IPv6 control plane and disabled provisioning network fails as the nodes do not pass introspection\n2042366 - Lifecycle hooks should be independently managed\n2042370 - [IPI on Alibabacloud] installer panics when the zone does not have an enhanced NAT gateway\n2042382 - [e2e][automation] CI takes more then 2 hours to run\n2042395 - Add prerequisites for active health checks test\n2042438 - Missing rpms in openstack-installer image\n2042466 - Selection does not happen when switching from Topology Graph to List View\n2042493 - No way to verify if IPs with leading zeros are still valid in the apiserver\n2042567 - insufficient info on CodeReady Containers configuration\n2042600 - Alone, the io.kubernetes.cri-o.Devices option poses a security risk\n2042619 - Overview page of the console is broken for hypershift clusters\n2042655 - [IPI on Alibabacloud] cluster becomes unusable if there is only one kube-apiserver pod running\n2042711 - [IBMCloud] Machine Deletion Hook cannot work on IBMCloud\n2042715 - [AliCloud] Machine Deletion Hook cannot work on AliCloud\n2042770 - [IPI on Alibabacloud] with vpcID \u0026 vswitchIDs specified, the installer would still try creating NAT gateway unexpectedly\n2042829 - Topology performance: HPA was fetched for each Deployment (Pod Ring)\n2042851 - Create template from SAP HANA template flow - VM is created instead of a new template\n2042906 - Edit machineset with same machine deletion hook name succeed\n2042960 - azure-file CI fails with \"gid(0) in storageClass and pod fsgroup(1000) are not equal\"\n2043003 - [IPI on Alibabacloud] \u0027destroy cluster\u0027 of a failed installation (bug2041694) stuck after \u0027stage=Nat gateways\u0027\n2043042 - [Serial] [sig-auth][Feature:OAuthServer] [RequestHeaders] [IdP] test RequestHeaders IdP [Suite:openshift/conformance/serial]\n2043043 - Cluster Autoscaler should use K8s 1.23 dependencies\n2043064 - Topology performance: Unnecessary rerenderings in topology nodes (unchanged mobx props)\n2043078 - Favorite system projects not visible in the project selector after toggling \"Show default projects\". \n2043117 - Recommended operators links are erroneously treated as external\n2043130 - Update CSI sidecars to the latest release for 4.10\n2043234 - Missing validation when creating several BGPPeers with the same peerAddress\n2043240 - Sync openshift/descheduler with sigs.k8s.io/descheduler\n2043254 - crio does not bind the security profiles directory\n2043296 - Ignition fails when reusing existing statically-keyed LUKS volume\n2043297 - [4.10] Bootimage bump tracker\n2043316 - RHCOS VM fails to boot on Nutanix AOS\n2043446 - Rebase aws-efs-utils to the latest upstream version. \n2043556 - Add proper ci-operator configuration to ironic and ironic-agent images\n2043577 - DPU network operator\n2043651 - Fix bug with exp. backoff working correcly when setting nextCheck in vsphere operator\n2043675 - Too many machines deleted by cluster autoscaler when scaling down\n2043683 - Revert bug 2039344 Ignoring IPv6 addresses against etcd cert validation\n2043709 - Logging flags no longer being bound to command line\n2043721 - Installer bootstrap hosts using outdated kubelet containing bugs\n2043731 - [IBMCloud] terraform outputs missing for ibmcloud bootstrap and worker ips for must-gather\n2043759 - Bump cluster-ingress-operator to k8s.io/api 1.23\n2043780 - Bump router to k8s.io/api 1.23\n2043787 - Bump cluster-dns-operator to k8s.io/api 1.23\n2043801 - Bump CoreDNS to k8s.io/api 1.23\n2043802 - EgressIP stopped working after single egressIP for a netnamespace is switched to the other node of HA pair after the first egress node is shutdown\n2043961 - [OVN-K] If pod creation fails, retry doesn\u0027t work as expected. \n2044201 - Templates golden image parameters names should be supported\n2044244 - Builds are failing after upgrading the cluster with builder image [jboss-webserver-5/jws56-openjdk8-openshift-rhel8]\n2044248 - [IBMCloud][vpc.block.csi.ibm.io]Cluster common user use the storageclass without parameter \u201ccsi.storage.k8s.io/fstype\u201d create pvc,pod successfully but write data to the pod\u0027s volume failed of \"Permission denied\"\n2044303 - [ovn][cloud-network-config-controller] cloudprivateipconfigs ips were left after deleting egressip objects\n2044347 - Bump to kubernetes 1.23.3\n2044481 - collect sharedresource cluster scoped instances with must-gather\n2044496 - Unable to create hardware events subscription - failed to add finalizers\n2044628 - CVE-2022-21673 grafana: Forward OAuth Identity Token can allow users to access some data sources\n2044680 - Additional libovsdb performance and resource consumption fixes\n2044704 - Observe \u003e Alerting pages should not show runbook links in 4.10\n2044717 - [e2e] improve tests for upstream test environment\n2044724 - Remove namespace column on VM list page when a project is selected\n2044745 - Upgrading cluster from 4.9 to 4.10 on Azure (ARO) causes the cloud-network-config-controller pod to CrashLoopBackOff\n2044808 - machine-config-daemon-pull.service: use `cp` instead of `cat` when extracting MCD in OKD\n2045024 - CustomNoUpgrade alerts should be ignored\n2045112 - vsphere-problem-detector has missing rbac rules for leases\n2045199 - SnapShot with Disk Hot-plug hangs\n2045561 - Cluster Autoscaler should use the same default Group value as Cluster API\n2045591 - Reconciliation of aws pod identity mutating webhook did not happen\n2045849 - Add Sprint 212 translations\n2045866 - MCO Operator pod spam \"Error creating event\" warning messages in 4.10\n2045878 - Sync upstream 1.16.0 downstream; includes hybrid helm plugin\n2045916 - [IBMCloud] Default machine profile in installer is unreliable\n2045927 - [FJ OCP4.10 Bug]: Podman failed to pull the IPA image due to the loss of proxy environment\n2046025 - [IPI on Alibabacloud] pre-configured alicloud DNS private zone is deleted after destroying cluster, please clarify\n2046137 - oc output for unknown commands is not human readable\n2046296 - When creating multiple consecutive egressIPs on GCP not all of them get assigned to the instance\n2046297 - Bump DB reconnect timeout\n2046517 - In Notification drawer, the \"Recommendations\" header shows when there isn\u0027t any recommendations\n2046597 - Observe \u003e Targets page may show the wrong service monitor is multiple monitors have the same namespace \u0026 label selectors\n2046626 - Allow setting custom metrics for Ansible-based Operators\n2046683 - [AliCloud]\"--scale-down-utilization-threshold\" doesn\u0027t work on AliCloud\n2047025 - Installation fails because of Alibaba CSI driver operator is degraded\n2047190 - Bump Alibaba CSI driver for 4.10\n2047238 - When using communities and localpreferences together, only localpreference gets applied\n2047255 - alibaba: resourceGroupID not found\n2047258 - [aws-usgov] fatal error occurred if AMI is not provided for AWS GovCloud regions\n2047317 - Update HELM OWNERS files under Dev Console\n2047455 - [IBM Cloud] Update custom image os type\n2047496 - Add image digest feature\n2047779 - do not degrade cluster if storagepolicy creation fails\n2047927 - \u0027oc get project\u0027 caused \u0027Observed a panic: cannot deep copy core.NamespacePhase\u0027 when AllRequestBodies is used\n2047929 - use lease for leader election\n2047975 - [sig-network][Feature:Router] The HAProxy router should override the route host for overridden domains with a custom value [Skipped:Disconnected] [Suite:openshift/conformance/parallel]\n2048046 - New route annotation to show another URL or hide topology URL decorator doesn\u0027t work for Knative Services\n2048048 - Application tab in User Preferences dropdown menus are too wide. \n2048050 - Topology list view items are not highlighted on keyboard navigation\n2048117 - [IBM]Shouldn\u0027t change status.storage.bucket and status.storage.resourceKeyCRN when update sepc.stroage,ibmcos with invalid value\n2048413 - Bond CNI: Failed to  attach Bond NAD to pod\n2048443 - Image registry operator panics when finalizes config deletion\n2048478 - [alicloud] CCM deploys alibaba-cloud-controller-manager from quay.io/openshift/origin-*\n2048484 - SNO: cluster-policy-controller failed to start due to missing serving-cert/tls.crt\n2048598 - Web terminal view is broken\n2048836 - ovs-configure mis-detecting the ipv6 status on IPv4 only cluster causing Deployment failure\n2048891 - Topology page is crashed\n2049003 - 4.10: [IBMCloud] ibm-vpc-block-csi-node does not specify an update strategy, only resource requests, or priority class\n2049043 - Cannot create VM from template\n2049156 - \u0027oc get project\u0027 caused \u0027Observed a panic: cannot deep copy core.NamespacePhase\u0027 when AllRequestBodies is used\n2049886 - Placeholder bug for OCP 4.10.0 metadata release\n2049890 - Warning annotation for pods with cpu requests or limits on single-node OpenShift cluster without workload partitioning\n2050189 - [aws-efs-csi-driver] Merge upstream changes since v1.3.2\n2050190 - [aws-ebs-csi-driver] Merge upstream changes since v1.2.0\n2050227 - Installation on PSI fails with: \u0027openstack platform does not have the required standard-attr-tag network extension\u0027\n2050247 - Failing test in periodics: [sig-network] Services should respect internalTrafficPolicy=Local Pod and Node, to Pod (hostNetwork: true) [Feature:ServiceInternalTrafficPolicy] [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel] [Suite:k8s]\n2050250 - Install fails to bootstrap, complaining about DefragControllerDegraded and sad members\n2050310 - ContainerCreateError when trying to launch large (\u003e500) numbers of pods across nodes\n2050370 - alert data for burn budget needs to be updated to prevent regression\n2050393 - ZTP missing support for local image registry and custom machine config\n2050557 - Can not push images to image-registry when enabling KMS encryption in AlibabaCloud\n2050737 - Remove metrics and events for master port offsets\n2050801 - Vsphere upi tries to access vsphere during manifests generation phase\n2050883 - Logger object in LSO does not log source location accurately\n2051692 - co/image-registry is degrade because ImagePrunerDegraded: Job has reached the specified backoff limit\n2052062 - Whereabouts should implement client-go 1.22+\n2052125 - [4.10] Crio appears to be coredumping in some scenarios\n2052210 - [aws-c2s] kube-apiserver crashloops due to missing cloud config\n2052339 - Failing webhooks will block an upgrade to 4.10 mid-way through the upgrade. \n2052458 - [IBM Cloud] ibm-vpc-block-csi-controller does not specify an update strategy, priority class, or only resource requests\n2052598 - kube-scheduler should use configmap lease\n2052599 - kube-controller-manger should use configmap lease\n2052600 - Failed to scaleup RHEL machine against OVN cluster due to jq tool is required by configure-ovs.sh\n2052609 - [vSphere CSI driver Operator] RWX volumes counts metrics `vsphere_rwx_volumes_total` not valid\n2052611 - MetalLB: BGPPeer object does not have ability to set ebgpMultiHop\n2052612 - MetalLB: Webhook Validation: Two BGPPeers instances can have different router ID set. \n2052644 - Infinite OAuth redirect loop post-upgrade to 4.10.0-rc.1\n2052666 - [4.10.z] change gitmodules to rhcos-4.10 branch\n2052756 - [4.10] PVs are not being cleaned up after PVC deletion\n2053175 - oc adm catalog mirror throws \u0027missing signature key\u0027 error when using file://local/index\n2053218 - ImagePull fails with error  \"unable to pull manifest from example.com/busy.box:v5  invalid reference format\"\n2053252 - Sidepanel for Connectors/workloads in topology shows invalid tabs\n2053268 - inability to detect static lifecycle failure\n2053314 - requestheader IDP test doesn\u0027t wait for cleanup, causing high failure rates\n2053323 - OpenShift-Ansible BYOH Unit Tests are Broken\n2053339 - Remove dev preview badge from IBM FlashSystem deployment windows\n2053751 - ztp-site-generate container is missing convenience entrypoint\n2053945 - [4.10] Failed to apply sriov policy on intel nics\n2054109 - Missing \"app\" label\n2054154 - RoleBinding in project without subject is causing \"Project access\" page to fail\n2054244 - Latest pipeline run should be listed on the top of the pipeline run list\n2054288 - console-master-e2e-gcp-console is broken\n2054562 - DPU network operator 4.10 branch need to sync with master\n2054897 - Unable to deploy hw-event-proxy operator\n2055193 - e2e-metal-ipi-serial-ovn-ipv6 is failing frequently\n2055358 - Summary Interval Hardcoded in PTP Operator if Set in the Global Body Instead of Command Line\n2055371 - Remove Check which enforces summary_interval must match logSyncInterval\n2055689 - [ibm]Operator storage PROGRESSING and DEGRADED is true during fresh install for ocp4.11\n2055894 - CCO mint mode will not work for Azure after sunsetting of Active Directory Graph API\n2056441 - AWS EFS CSI driver should use the trusted CA bundle when cluster proxy is configured\n2056479 - ovirt-csi-driver-node pods are crashing intermittently\n2056572 - reconcilePrecaching error: cannot list resource \"clusterserviceversions\" in API group \"operators.coreos.com\" at the cluster scope\"\n2056629 - [4.10] EFS CSI driver can\u0027t unmount volumes with \"wait: no child processes\"\n2056878 - (dummy bug) ovn-kubernetes ExternalTrafficPolicy still SNATs\n2056928 - Ingresscontroller LB scope change behaviour differs for different values of aws-load-balancer-internal annotation\n2056948 - post 1.23 rebase: regression in service-load balancer reliability\n2057438 - Service Level Agreement (SLA) always show \u0027Unknown\u0027\n2057721 - Fix Proxy support in RHACM 2.4.2\n2057724 - Image creation fails when NMstateConfig CR is empty\n2058641 - [4.10] Pod density test causing problems when using kube-burner\n2059761 - 4.9.23-s390x-machine-os-content manifest invalid when mirroring content for disconnected install\n2060610 - Broken access to public images: Unable to connect to the server: no basic auth credentials\n2060956 - service domain can\u0027t be resolved when networkpolicy is used in OCP 4.10-rc\n\n5. References:\n\nhttps://access.redhat.com/security/cve/CVE-2014-3577\nhttps://access.redhat.com/security/cve/CVE-2016-10228\nhttps://access.redhat.com/security/cve/CVE-2017-14502\nhttps://access.redhat.com/security/cve/CVE-2018-20843\nhttps://access.redhat.com/security/cve/CVE-2018-1000858\nhttps://access.redhat.com/security/cve/CVE-2019-8625\nhttps://access.redhat.com/security/cve/CVE-2019-8710\nhttps://access.redhat.com/security/cve/CVE-2019-8720\nhttps://access.redhat.com/security/cve/CVE-2019-8743\nhttps://access.redhat.com/security/cve/CVE-2019-8764\nhttps://access.redhat.com/security/cve/CVE-2019-8766\nhttps://access.redhat.com/security/cve/CVE-2019-8769\nhttps://access.redhat.com/security/cve/CVE-2019-8771\nhttps://access.redhat.com/security/cve/CVE-2019-8782\nhttps://access.redhat.com/security/cve/CVE-2019-8783\nhttps://access.redhat.com/security/cve/CVE-2019-8808\nhttps://access.redhat.com/security/cve/CVE-2019-8811\nhttps://access.redhat.com/security/cve/CVE-2019-8812\nhttps://access.redhat.com/security/cve/CVE-2019-8813\nhttps://access.redhat.com/security/cve/CVE-2019-8814\nhttps://access.redhat.com/security/cve/CVE-2019-8815\nhttps://access.redhat.com/security/cve/CVE-2019-8816\nhttps://access.redhat.com/security/cve/CVE-2019-8819\nhttps://access.redhat.com/security/cve/CVE-2019-8820\nhttps://access.redhat.com/security/cve/CVE-2019-8823\nhttps://access.redhat.com/security/cve/CVE-2019-8835\nhttps://access.redhat.com/security/cve/CVE-2019-8844\nhttps://access.redhat.com/security/cve/CVE-2019-8846\nhttps://access.redhat.com/security/cve/CVE-2019-9169\nhttps://access.redhat.com/security/cve/CVE-2019-13050\nhttps://access.redhat.com/security/cve/CVE-2019-13627\nhttps://access.redhat.com/security/cve/CVE-2019-14889\nhttps://access.redhat.com/security/cve/CVE-2019-15903\nhttps://access.redhat.com/security/cve/CVE-2019-19906\nhttps://access.redhat.com/security/cve/CVE-2019-20454\nhttps://access.redhat.com/security/cve/CVE-2019-20807\nhttps://access.redhat.com/security/cve/CVE-2019-25013\nhttps://access.redhat.com/security/cve/CVE-2020-1730\nhttps://access.redhat.com/security/cve/CVE-2020-3862\nhttps://access.redhat.com/security/cve/CVE-2020-3864\nhttps://access.redhat.com/security/cve/CVE-2020-3865\nhttps://access.redhat.com/security/cve/CVE-2020-3867\nhttps://access.redhat.com/security/cve/CVE-2020-3868\nhttps://access.redhat.com/security/cve/CVE-2020-3885\nhttps://access.redhat.com/security/cve/CVE-2020-3894\nhttps://access.redhat.com/security/cve/CVE-2020-3895\nhttps://access.redhat.com/security/cve/CVE-2020-3897\nhttps://access.redhat.com/security/cve/CVE-2020-3899\nhttps://access.redhat.com/security/cve/CVE-2020-3900\nhttps://access.redhat.com/security/cve/CVE-2020-3901\nhttps://access.redhat.com/security/cve/CVE-2020-3902\nhttps://access.redhat.com/security/cve/CVE-2020-8927\nhttps://access.redhat.com/security/cve/CVE-2020-9802\nhttps://access.redhat.com/security/cve/CVE-2020-9803\nhttps://access.redhat.com/security/cve/CVE-2020-9805\nhttps://access.redhat.com/security/cve/CVE-2020-9806\nhttps://access.redhat.com/security/cve/CVE-2020-9807\nhttps://access.redhat.com/security/cve/CVE-2020-9843\nhttps://access.redhat.com/security/cve/CVE-2020-9850\nhttps://access.redhat.com/security/cve/CVE-2020-9862\nhttps://access.redhat.com/security/cve/CVE-2020-9893\nhttps://access.redhat.com/security/cve/CVE-2020-9894\nhttps://access.redhat.com/security/cve/CVE-2020-9895\nhttps://access.redhat.com/security/cve/CVE-2020-9915\nhttps://access.redhat.com/security/cve/CVE-2020-9925\nhttps://access.redhat.com/security/cve/CVE-2020-9952\nhttps://access.redhat.com/security/cve/CVE-2020-10018\nhttps://access.redhat.com/security/cve/CVE-2020-11793\nhttps://access.redhat.com/security/cve/CVE-2020-13434\nhttps://access.redhat.com/security/cve/CVE-2020-14391\nhttps://access.redhat.com/security/cve/CVE-2020-15358\nhttps://access.redhat.com/security/cve/CVE-2020-15503\nhttps://access.redhat.com/security/cve/CVE-2020-25660\nhttps://access.redhat.com/security/cve/CVE-2020-25677\nhttps://access.redhat.com/security/cve/CVE-2020-27618\nhttps://access.redhat.com/security/cve/CVE-2020-27781\nhttps://access.redhat.com/security/cve/CVE-2020-29361\nhttps://access.redhat.com/security/cve/CVE-2020-29362\nhttps://access.redhat.com/security/cve/CVE-2020-29363\nhttps://access.redhat.com/security/cve/CVE-2021-3121\nhttps://access.redhat.com/security/cve/CVE-2021-3326\nhttps://access.redhat.com/security/cve/CVE-2021-3449\nhttps://access.redhat.com/security/cve/CVE-2021-3450\nhttps://access.redhat.com/security/cve/CVE-2021-3516\nhttps://access.redhat.com/security/cve/CVE-2021-3517\nhttps://access.redhat.com/security/cve/CVE-2021-3518\nhttps://access.redhat.com/security/cve/CVE-2021-3520\nhttps://access.redhat.com/security/cve/CVE-2021-3521\nhttps://access.redhat.com/security/cve/CVE-2021-3537\nhttps://access.redhat.com/security/cve/CVE-2021-3541\nhttps://access.redhat.com/security/cve/CVE-2021-3733\nhttps://access.redhat.com/security/cve/CVE-2021-3749\nhttps://access.redhat.com/security/cve/CVE-2021-20305\nhttps://access.redhat.com/security/cve/CVE-2021-21684\nhttps://access.redhat.com/security/cve/CVE-2021-22946\nhttps://access.redhat.com/security/cve/CVE-2021-22947\nhttps://access.redhat.com/security/cve/CVE-2021-25215\nhttps://access.redhat.com/security/cve/CVE-2021-27218\nhttps://access.redhat.com/security/cve/CVE-2021-30666\nhttps://access.redhat.com/security/cve/CVE-2021-30761\nhttps://access.redhat.com/security/cve/CVE-2021-30762\nhttps://access.redhat.com/security/cve/CVE-2021-33928\nhttps://access.redhat.com/security/cve/CVE-2021-33929\nhttps://access.redhat.com/security/cve/CVE-2021-33930\nhttps://access.redhat.com/security/cve/CVE-2021-33938\nhttps://access.redhat.com/security/cve/CVE-2021-36222\nhttps://access.redhat.com/security/cve/CVE-2021-37750\nhttps://access.redhat.com/security/cve/CVE-2021-39226\nhttps://access.redhat.com/security/cve/CVE-2021-41190\nhttps://access.redhat.com/security/cve/CVE-2021-43813\nhttps://access.redhat.com/security/cve/CVE-2021-44716\nhttps://access.redhat.com/security/cve/CVE-2021-44717\nhttps://access.redhat.com/security/cve/CVE-2022-0532\nhttps://access.redhat.com/security/cve/CVE-2022-21673\nhttps://access.redhat.com/security/cve/CVE-2022-24407\nhttps://access.redhat.com/security/updates/classification/#moderate\n\n6. Contact:\n\nThe Red Hat security contact is \u003csecalert@redhat.com\u003e. More contact\ndetails at https://access.redhat.com/security/team/contact/\n\nCopyright 2022 Red Hat, Inc. \n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1\n\niQIVAwUBYipqONzjgjWX9erEAQjQcBAAgWTjA6Q2NgqfVf63ZpJF1jPurZLPqxDL\n0in/5+/wqWaiQ6yk7wM3YBZgviyKnAMCVdrLsaR7R77BvfJcTE3W/fzogxpp6Rne\neGT1PTgQRecrSIn+WG4gGSteavTULWOIoPvUiNpiy3Y7fFgjFdah+Nyx3Xd+xehM\nCEswylOd6Hr03KZ1tS3XL3kGL2botha48Yls7FzDFbNcy6TBAuycmQZifKu8mHaF\naDAupVJinDnnVgACeS6CnZTAD+Vrx5W7NIisteXv4x5Hy+jBIUHr8Yge3oxYoFnC\nY/XmuOw2KilLZuqFe+KHig45qT+FmNU8E1egcGpNWvmS8hGZfiG1jEQAqDPbZHxp\nsQAQZLQyz3TvXa29vp4QcsUuMxndIOi+QaK75JmqE06MqMIlFDYpr6eQOIgIZvFO\nRDZU/qvBjh56ypInoqInBf8KOQMy6eO+r6nFbMGcAfucXmz0EVcSP1oFHAoA1nWN\nrs1Qz/SO4CvdPERxcr1MLuBLggZ6iqGmHKk5IN0SwcndBHaVJ3j/LBv9m7wBYVry\nbSvojBDYx5ricbTwB5sGzu7oH5yVl813FA9cjkFpEhBiMtTfI+DKC8ssoRYNHd5Z\n7gLW6KWPUIDuCIiiioPZAJMyvJ0IMrNDoQ0lhqPeV7PFdlRhT95M/DagUZOpPVuT\nb5PUYUBIZLc=\n=GUDA\n-----END PGP SIGNATURE-----\n--\nRHSA-announce mailing list\nRHSA-announce@redhat.com\nhttps://listman.redhat.com/mailman/listinfo/rhsa-announce\n. Description:\n\nRed Hat OpenShift Serverless 1.17.0 release of the OpenShift Serverless\nOperator. \n\nSecurity Fix(es):\n\n* golang: crypto/tls: certificate of wrong type is causing TLS client to\npanic\n(CVE-2021-34558)\n* golang: net: lookup functions may return invalid host names\n(CVE-2021-33195)\n* golang: net/http/httputil: ReverseProxy forwards connection headers if\nfirst one is empty (CVE-2021-33197)\n* golang: match/big.Rat: may cause a panic or an unrecoverable fatal error\nif passed inputs with very large exponents (CVE-2021-33198)\n* golang: encoding/xml: infinite loop when using xml.NewTokenDecoder with a\ncustom TokenReader (CVE-2021-27918)\n* golang: net/http: panic in ReadRequest and ReadResponse when reading a\nvery large header (CVE-2021-31525)\n* golang: archive/zip: malformed archive may cause panic or memory\nexhaustion (CVE-2021-33196)\n\nIt was found that the CVE-2021-27918, CVE-2021-31525 and CVE-2021-33196\nhave been incorrectly mentioned as fixed in RHSA for Serverless client kn\n1.16.0. This has been fixed (CVE-2021-3703). \n\nFor more details about the security issue(s), including the impact, a CVSS\nscore, acknowledgments, and other related information, refer to the CVE\npage(s) listed in the References section. Bugs fixed (https://bugzilla.redhat.com/):\n\n1983596 - CVE-2021-34558 golang: crypto/tls: certificate of wrong type is causing TLS client to panic\n1983651 - Release of OpenShift Serverless Serving 1.17.0\n1983654 - Release of OpenShift Serverless Eventing 1.17.0\n1989564 - CVE-2021-33195 golang: net: lookup functions may return invalid host names\n1989570 - CVE-2021-33197 golang: net/http/httputil: ReverseProxy forwards connection headers if first one is empty\n1989575 - CVE-2021-33198 golang: math/big.Rat: may cause a panic or an unrecoverable fatal error if passed inputs with very large exponents\n1992955 - CVE-2021-3703 serverless: incomplete fix for CVE-2021-27918 / CVE-2021-31525 / CVE-2021-33196\n\n5",
    "sources": [
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "db": "PACKETSTORM",
        "id": "162634"
      },
      {
        "db": "PACKETSTORM",
        "id": "162837"
      },
      {
        "db": "PACKETSTORM",
        "id": "163267"
      },
      {
        "db": "PACKETSTORM",
        "id": "163496"
      },
      {
        "db": "PACKETSTORM",
        "id": "161254"
      },
      {
        "db": "PACKETSTORM",
        "id": "166279"
      },
      {
        "db": "PACKETSTORM",
        "id": "164192"
      }
    ],
    "trust": 2.34
  },
  "external_ids": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/external_ids#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "db": "NVD",
        "id": "CVE-2019-25013",
        "trust": 4.0
      },
      {
        "db": "ICS CERT",
        "id": "ICSA-23-166-10",
        "trust": 0.8
      },
      {
        "db": "JVN",
        "id": "JVNVU99464755",
        "trust": 0.8
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179",
        "trust": 0.8
      },
      {
        "db": "PACKETSTORM",
        "id": "162634",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "162837",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "163267",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "163496",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "161254",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "166279",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "164192",
        "trust": 0.7
      },
      {
        "db": "PACKETSTORM",
        "id": "163789",
        "trust": 0.6
      },
      {
        "db": "PACKETSTORM",
        "id": "163276",
        "trust": 0.6
      },
      {
        "db": "PACKETSTORM",
        "id": "163747",
        "trust": 0.6
      },
      {
        "db": "PACKETSTORM",
        "id": "168011",
        "trust": 0.6
      },
      {
        "db": "PACKETSTORM",
        "id": "163406",
        "trust": 0.6
      },
      {
        "db": "PACKETSTORM",
        "id": "162877",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.0868",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2022.6426",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2228",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2180",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2022.0875",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.0373",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.0728",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.0743",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2711",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.1866",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.3141",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.4058",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2657",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.1820",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2022.5140",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.1743",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2022.4222",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2604",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2022.1025",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2365",
        "trust": 0.6
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2021.2781",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2022011038",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2022031430",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021071310",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021070604",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021062703",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021062315",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021071516",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021122914",
        "trust": 0.6
      },
      {
        "db": "CS-HELP",
        "id": "SB2021092220",
        "trust": 0.6
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048",
        "trust": 0.6
      },
      {
        "db": "VULMON",
        "id": "CVE-2019-25013",
        "trust": 0.1
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "db": "PACKETSTORM",
        "id": "162634"
      },
      {
        "db": "PACKETSTORM",
        "id": "162837"
      },
      {
        "db": "PACKETSTORM",
        "id": "163267"
      },
      {
        "db": "PACKETSTORM",
        "id": "163496"
      },
      {
        "db": "PACKETSTORM",
        "id": "161254"
      },
      {
        "db": "PACKETSTORM",
        "id": "166279"
      },
      {
        "db": "PACKETSTORM",
        "id": "164192"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "id": "VAR-202101-0119",
  "iot": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/iot#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": true,
    "sources": [
      {
        "db": "VARIoT devices database",
        "id": null
      }
    ],
    "trust": 0.465277775
  },
  "last_update_date": "2025-12-22T21:27:57.360000Z",
  "patch": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/patch#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "title": "Bug\u00a024973 NetAppNetApp\u00a0Advisory",
        "trust": 0.8,
        "url": "https://www.broadcom.com/"
      },
      {
        "title": "GNU C Library Buffer error vulnerability fix",
        "trust": 0.6,
        "url": "http://123.124.177.30/web/xxk/bdxqById.tag?id=138312"
      },
      {
        "title": "Debian CVElist Bug Report Logs: glibc: CVE-2019-25013",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=7073abdc63eae799f90555726b8fbe41"
      },
      {
        "title": "Red Hat: Moderate: glibc security and bug fix update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20210348 - Security Advisory"
      },
      {
        "title": "Amazon Linux 2: ALAS2-2021-1599",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=amazon_linux2\u0026qid=ALAS2-2021-1599"
      },
      {
        "title": "Ubuntu Security Notice: USN-5768-1: GNU C Library vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-5768-1"
      },
      {
        "title": "Arch Linux Issues: ",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=arch_linux_issues\u0026qid=CVE-2019-25013 log"
      },
      {
        "title": "Amazon Linux AMI: ALAS-2021-1511",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=amazon_linux_ami\u0026qid=ALAS-2021-1511"
      },
      {
        "title": "Arch Linux Advisories: [ASA-202102-18] glibc: denial of service",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=arch_linux_advisories\u0026qid=ASA-202102-18"
      },
      {
        "title": "Arch Linux Advisories: [ASA-202102-17] lib32-glibc: denial of service",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=arch_linux_advisories\u0026qid=ASA-202102-17"
      },
      {
        "title": "Red Hat: Moderate: Red Hat Advanced Cluster Management 2.1.3 security and bug fix update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20210607 - Security Advisory"
      },
      {
        "title": "Amazon Linux 2: ALAS2-2021-1605",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=amazon_linux2\u0026qid=ALAS2-2021-1605"
      },
      {
        "title": "Ubuntu Security Notice: USN-5310-1: GNU C Library vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-5310-1"
      },
      {
        "title": "Red Hat: Important: Service Telemetry Framework 1.4 security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20225924 - Security Advisory"
      },
      {
        "title": "IBM: Security Bulletin: Cloud Pak for Security contains security vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ibm_psirt_blog\u0026qid=08f19f0be4d5dcf7486e5abcdb671477"
      },
      {
        "title": "Red Hat: Moderate: OpenShift Container Platform 4.10.3 security update",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=red_hat_security_advisories\u0026qid=RHSA-20220056 - Security Advisory"
      },
      {
        "title": "Siemens Security Advisories: Siemens Security Advisory",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=siemens_security_advisories\u0026qid=ec6577109e640dac19a6ddb978afe82d"
      },
      {
        "title": "",
        "trust": 0.1,
        "url": "https://github.com/Live-Hack-CVE/CVE-2019-25013 "
      },
      {
        "title": "ecr-api",
        "trust": 0.1,
        "url": "https://github.com/YaleSpinup/ecr-api "
      },
      {
        "title": "sanction",
        "trust": 0.1,
        "url": "https://github.com/ctc-oss/sanction "
      },
      {
        "title": "release-the-code-litecoin",
        "trust": 0.1,
        "url": "https://github.com/brandoncamenisch/release-the-code-litecoin "
      },
      {
        "title": "interview_project",
        "trust": 0.1,
        "url": "https://github.com/domyrtille/interview_project "
      },
      {
        "title": "trivy-multiscanner",
        "trust": 0.1,
        "url": "https://github.com/onzack/trivy-multiscanner "
      },
      {
        "title": "spring-boot-app-with-log4j-vuln",
        "trust": 0.1,
        "url": "https://github.com/nedenwalker/spring-boot-app-with-log4j-vuln "
      },
      {
        "title": "giant-squid",
        "trust": 0.1,
        "url": "https://github.com/dispera/giant-squid "
      },
      {
        "title": "devops-demo",
        "trust": 0.1,
        "url": "https://github.com/epequeno/devops-demo "
      },
      {
        "title": "spring-boot-app-using-gradle",
        "trust": 0.1,
        "url": "https://github.com/nedenwalker/spring-boot-app-using-gradle "
      },
      {
        "title": "xyz-solutions",
        "trust": 0.1,
        "url": "https://github.com/sauliuspr/xyz-solutions "
      },
      {
        "title": "myapp-container-jaxrs",
        "trust": 0.1,
        "url": "https://github.com/akiraabe/myapp-container-jaxrs "
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      }
    ]
  },
  "problemtype_data": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "problemtype": "CWE-125",
        "trust": 1.0
      },
      {
        "problemtype": "Out-of-bounds read (CWE-125) [NVD evaluation ]",
        "trust": 0.8
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "references": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/references#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "trust": 2.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-25013"
      },
      {
        "trust": 1.6,
        "url": "https://security.netapp.com/advisory/ntap-20210205-0004/"
      },
      {
        "trust": 1.6,
        "url": "https://security.gentoo.org/glsa/202107-07"
      },
      {
        "trust": 1.6,
        "url": "https://www.oracle.com/security-alerts/cpuapr2022.html"
      },
      {
        "trust": 1.6,
        "url": "https://lists.debian.org/debian-lts-announce/2022/10/msg00021.html"
      },
      {
        "trust": 1.6,
        "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=24973"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r32d767ac804e9b8aad4355bb85960a6a1385eab7afff549a5e98660f%40%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r5af4430421bb6f9973294691a7904bbd260937e9eef96b20556f43ff%40%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r750eee18542bc02bd8350861c424ee60a9b9b225568fa09436a37ece%40%3cissues.zookeeper.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r448bb851cc8e6e3f93f3c28c70032b37062625d81214744474ac49e7%40%3cdev.kafka.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/rd2354f9ccce41e494fbadcbc5ad87218de6ec0fff8a7b54c8462226c%40%3cissues.zookeeper.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r7a2e94adfe0a2f0a1d42e4927e8c32ecac97d37db9cb68095fe9ddbc%40%3cdev.zookeeper.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3cdev.mina.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r4806a391091e082bdea17266452ca656ebc176e51bb3932733b3a0a2%40%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 1.0,
        "url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/tvcunlq3hxgs4vpuqkwtjgraw2ktfgxs/"
      },
      {
        "trust": 1.0,
        "url": "https://sourceware.org/git/?p=glibc.git%3ba=commit%3bh=ee7a3144c9922808181009b7b3e50e852fb4999b"
      },
      {
        "trust": 1.0,
        "url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4y6tx47p47kabsfol26fldnvcwxdkdez/"
      },
      {
        "trust": 1.0,
        "url": "https://lists.apache.org/thread.html/r499e4f96d0b5109ef083f2feccd33c51650c1b7d7068aa3bd47efca9%40%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 0.8,
        "url": "http://jvn.jp/vu/jvnvu99464755/index.html"
      },
      {
        "trust": 0.8,
        "url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-166-10"
      },
      {
        "trust": 0.7,
        "url": "https://access.redhat.com/security/cve/cve-2019-25013"
      },
      {
        "trust": 0.7,
        "url": "https://access.redhat.com/security/team/contact/"
      },
      {
        "trust": 0.7,
        "url": "https://access.redhat.com/security/updates/classification/#moderate"
      },
      {
        "trust": 0.7,
        "url": "https://bugzilla.redhat.com/):"
      },
      {
        "trust": 0.6,
        "url": "https://access.redhat.com/security/cve/cve-2021-3326"
      },
      {
        "trust": 0.6,
        "url": "https://listman.redhat.com/mailman/listinfo/rhsa-announce"
      },
      {
        "trust": 0.6,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-10228"
      },
      {
        "trust": 0.6,
        "url": "https://access.redhat.com/security/cve/cve-2016-10228"
      },
      {
        "trust": 0.6,
        "url": "https://access.redhat.com/security/cve/cve-2020-27618"
      },
      {
        "trust": 0.6,
        "url": "https://access.redhat.com/security/cve/cve-2019-9169"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r5af4430421bb6f9973294691a7904bbd260937e9eef96b20556f43ff@%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r7a2e94adfe0a2f0a1d42e4927e8c32ecac97d37db9cb68095fe9ddbc@%3cdev.zookeeper.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r448bb851cc8e6e3f93f3c28c70032b37062625d81214744474ac49e7@%3cdev.kafka.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://sourceware.org/git/?p=glibc.git;a=commit;h=ee7a3144c9922808181009b7b3e50e852fb4999b"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r4806a391091e082bdea17266452ca656ebc176e51bb3932733b3a0a2@%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3cdev.mina.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/rd2354f9ccce41e494fbadcbc5ad87218de6ec0fff8a7b54c8462226c@%3cissues.zookeeper.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/tvcunlq3hxgs4vpuqkwtjgraw2ktfgxs/"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r750eee18542bc02bd8350861c424ee60a9b9b225568fa09436a37ece@%3cissues.zookeeper.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r499e4f96d0b5109ef083f2feccd33c51650c1b7d7068aa3bd47efca9@%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4y6tx47p47kabsfol26fldnvcwxdkdez/"
      },
      {
        "trust": 0.6,
        "url": "https://lists.apache.org/thread.html/r32d767ac804e9b8aad4355bb85960a6a1385eab7afff549a5e98660f@%3cjira.kafka.apache.org%3e"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/164192/red-hat-security-advisory-2021-3556-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/168011/red-hat-security-advisory-2022-5924-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/163789/red-hat-security-advisory-2021-3119-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.ibm.com/blogs/psirt/security-bulletin-cloud-pak-for-security-contains-security-vulnerabilities/"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.1866"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2657"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.1743"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.1820"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2711"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021071310"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/163747/red-hat-security-advisory-2021-3016-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2781"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2022.5140"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.0373/"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2022031430"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/166279/red-hat-security-advisory-2022-0056-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2365"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2180"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021122914"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/162634/red-hat-security-advisory-2021-1585-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/163276/red-hat-security-advisory-2021-2543-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2022.0875"
      },
      {
        "trust": 0.6,
        "url": "https://vigilance.fr/vulnerability/glibc-out-of-bounds-memory-reading-via-iconv-euc-kr-encoding-34360"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2022.1025"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.0728"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/163496/red-hat-security-advisory-2021-2705-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.0743"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2228"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021062703"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021092220"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.0868"
      },
      {
        "trust": 0.6,
        "url": "https://www.ibm.com/support/pages/node/6520474"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.2604"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/162837/red-hat-security-advisory-2021-2136-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/163267/red-hat-security-advisory-2021-2532-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2022011038"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/161254/red-hat-security-advisory-2021-0348-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021070604"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021071516"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/162877/red-hat-security-advisory-2021-2121-01.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.cybersecurity-help.cz/vdb/sb2021062315"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.4058"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2022.4222"
      },
      {
        "trust": 0.6,
        "url": "https://packetstormsecurity.com/files/163406/gentoo-linux-security-advisory-202107-07.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2021.3141"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2022.6426"
      },
      {
        "trust": 0.5,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-9169"
      },
      {
        "trust": 0.5,
        "url": "https://access.redhat.com/security/cve/cve-2020-15358"
      },
      {
        "trust": 0.5,
        "url": "https://access.redhat.com/security/cve/cve-2020-13434"
      },
      {
        "trust": 0.5,
        "url": "https://access.redhat.com/security/cve/cve-2020-29362"
      },
      {
        "trust": 0.5,
        "url": "https://access.redhat.com/security/cve/cve-2020-29361"
      },
      {
        "trust": 0.5,
        "url": "https://access.redhat.com/security/cve/cve-2020-8927"
      },
      {
        "trust": 0.5,
        "url": "https://access.redhat.com/security/cve/cve-2020-29363"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-27618"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2020-8286"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2020-28196"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2021-20305"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2020-8231"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-13434"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2020-8285"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2019-2708"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-2708"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2020-8284"
      },
      {
        "trust": 0.4,
        "url": "https://access.redhat.com/security/cve/cve-2017-14502"
      },
      {
        "trust": 0.4,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-14502"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-3326"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-13776"
      },
      {
        "trust": 0.3,
        "url": "https://access.redhat.com/security/cve/cve-2019-3842"
      },
      {
        "trust": 0.3,
        "url": "https://access.redhat.com/security/cve/cve-2020-13776"
      },
      {
        "trust": 0.3,
        "url": "https://access.redhat.com/security/cve/cve-2020-24977"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-3842"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-29362"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-8284"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-15358"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-8285"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-8286"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-8927"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-29363"
      },
      {
        "trust": 0.3,
        "url": "https://access.redhat.com/security/cve/cve-2021-3449"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-8231"
      },
      {
        "trust": 0.3,
        "url": "https://access.redhat.com/security/cve/cve-2021-3450"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-29361"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-28196"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/articles/11258"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/team/key/"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3121"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2020-26116"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2020-27619"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3177"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-23336"
      },
      {
        "trust": 0.2,
        "url": "https://issues.jboss.org/):"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-27219"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-20305"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-27219"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-24977"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-27918"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/documentation/en-us/openshift_container_platform/"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-31525"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-31525"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/documentation/en-us/openshift_container_platform/4.7/html/serverless/index"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-27918"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/html/serverless/index"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-33196"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-33196"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3537"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-27218"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3520"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3541"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3518"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3516"
      },
      {
        "trust": 0.2,
        "url": "https://access.redhat.com/security/cve/cve-2021-3517"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.4_release_notes/"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2021:1585"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14346"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14347"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-36322"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-12114"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25712"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-12114"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-13543"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-27835"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9951"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25704"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-10878"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-19528"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9948"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-13012"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-0431"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14363"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14345"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-13584"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-26137"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-18811"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-13543"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14360"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-13584"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-19528"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-12464"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14314"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14347"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14360"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-12362"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2021:2136"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14356"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-27786"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14314"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25643"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9983"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-24394"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-0431"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-0342"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-18811"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14344"
      },
      {
        "trust": 0.1,
        "url": "https://docs.openshift.com/container-platform/4.7/release_notes/ocp-4-7-rel"
      },
      {
        "trust": 0.1,
        "url": "https://docs.openshift.com/container-platform/4.7/logging/cluster-logging-u"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14345"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14344"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-19523"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14362"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14361"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-10543"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25285"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-35508"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-12362"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25212"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-19523"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-28974"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-10543"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-15437"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-13012"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25284"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14346"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-14356"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-10878"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-11608"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-11608"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-12464"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-26116"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-28362"
      },
      {
        "trust": 0.1,
        "url": "https://docs.openshift.com/container-platform/4.7/jaeger/jaeger_install/rhb"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-3114"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-28362"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2021:2532"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-23336"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-27619"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-3114"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2021:2705"
      },
      {
        "trust": 0.1,
        "url": "https://www.redhat.com/mailman/listinfo/rhsa-announce"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-10029"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-10029"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2021:0348"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2020-29573"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-29573"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-13050"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9925"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9802"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8771"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-30762"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33938"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8783"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9895"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8625"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-44716"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8812"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8812"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3899"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8819"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-43813"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3867"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-20454"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8720"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9893"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33930"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8782"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8808"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3902"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2022-24407"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-25215"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3900"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-30761"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33928"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8743"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9805"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-19906"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8820"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9807"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8769"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8710"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-37750"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8813"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9850"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8710"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-27781"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8811"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8769"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2022:0055"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-22947"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9803"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8764"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9862"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2014-3577"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2014-3577"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-3749"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3885"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-15503"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-20807"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-41190"
      },
      {
        "trust": 0.1,
        "url": "https://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-10018"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-14889"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25660"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8835"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8764"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-3733"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8844"
      },
      {
        "trust": 0.1,
        "url": "https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3865"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-1730"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3864"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-19906"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-21684"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-13627"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-14391"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3862"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2022:0056"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8811"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3901"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-39226"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8823"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8808"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2018-1000858"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-15903"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3895"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-44717"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-11793"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2018-1000858"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-20454"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2018-20843"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2022-0532"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8720"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9894"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8816"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9843"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-13627"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8771"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-13050"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3897"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9806"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8814"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-14889"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2018-20843"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8743"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33929"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9915"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-36222"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8815"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8813"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8625"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-8766"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8783"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-20807"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-9952"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-22946"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2022-21673"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2019-15903"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8766"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3868"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8846"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-3894"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2020-25677"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-30666"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2019-8782"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-3521"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-33195"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-27218"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/documentation/en-us/openshift_container_platform/4.8/html/serverless/index"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-33197"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33195"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-33198"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33198"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-34558"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/errata/rhsa-2021:3556"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-33197"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2021-20271"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-3421"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-20271"
      },
      {
        "trust": 0.1,
        "url": "https://access.redhat.com/security/cve/cve-2021-3703"
      }
    ],
    "sources": [
      {
        "db": "PACKETSTORM",
        "id": "162634"
      },
      {
        "db": "PACKETSTORM",
        "id": "162837"
      },
      {
        "db": "PACKETSTORM",
        "id": "163267"
      },
      {
        "db": "PACKETSTORM",
        "id": "163496"
      },
      {
        "db": "PACKETSTORM",
        "id": "161254"
      },
      {
        "db": "PACKETSTORM",
        "id": "166279"
      },
      {
        "db": "PACKETSTORM",
        "id": "164192"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "sources": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "db": "PACKETSTORM",
        "id": "162634"
      },
      {
        "db": "PACKETSTORM",
        "id": "162837"
      },
      {
        "db": "PACKETSTORM",
        "id": "163267"
      },
      {
        "db": "PACKETSTORM",
        "id": "163496"
      },
      {
        "db": "PACKETSTORM",
        "id": "161254"
      },
      {
        "db": "PACKETSTORM",
        "id": "166279"
      },
      {
        "db": "PACKETSTORM",
        "id": "164192"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "sources_release_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2021-01-04T00:00:00",
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "date": "2021-05-19T13:59:56",
        "db": "PACKETSTORM",
        "id": "162634"
      },
      {
        "date": "2021-05-27T13:28:54",
        "db": "PACKETSTORM",
        "id": "162837"
      },
      {
        "date": "2021-06-23T16:08:25",
        "db": "PACKETSTORM",
        "id": "163267"
      },
      {
        "date": "2021-07-14T15:02:07",
        "db": "PACKETSTORM",
        "id": "163496"
      },
      {
        "date": "2021-02-02T16:12:10",
        "db": "PACKETSTORM",
        "id": "161254"
      },
      {
        "date": "2022-03-11T16:38:38",
        "db": "PACKETSTORM",
        "id": "166279"
      },
      {
        "date": "2021-09-17T16:04:56",
        "db": "PACKETSTORM",
        "id": "164192"
      },
      {
        "date": "2021-01-04T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "date": "2021-09-10T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "date": "2021-01-04T18:15:13.027000",
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "sources_update_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2023-11-09T00:00:00",
        "db": "VULMON",
        "id": "CVE-2019-25013"
      },
      {
        "date": "2022-12-12T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      },
      {
        "date": "2023-06-16T05:32:00",
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      },
      {
        "date": "2025-06-09T16:15:30.703000",
        "db": "NVD",
        "id": "CVE-2019-25013"
      }
    ]
  },
  "threat_type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/threat_type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "remote",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      }
    ],
    "trust": 0.6
  },
  "title": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/title#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "GNU\u00a0C\u00a0Library\u00a0 Out-of-bounds read vulnerability in",
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2019-016179"
      }
    ],
    "trust": 0.8
  },
  "type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "buffer error",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-202101-048"
      }
    ],
    "trust": 0.6
  }
}

{
  "@context": {
    "@vocab": "https://www.variotdbs.pl/ref/VARIoTentry#",
    "affected_products": {
      "@id": "https://www.variotdbs.pl/ref/affected_products"
    },
    "configurations": {
      "@id": "https://www.variotdbs.pl/ref/configurations"
    },
    "credits": {
      "@id": "https://www.variotdbs.pl/ref/credits"
    },
    "cvss": {
      "@id": "https://www.variotdbs.pl/ref/cvss/"
    },
    "description": {
      "@id": "https://www.variotdbs.pl/ref/description/"
    },
    "exploit_availability": {
      "@id": "https://www.variotdbs.pl/ref/exploit_availability/"
    },
    "external_ids": {
      "@id": "https://www.variotdbs.pl/ref/external_ids/"
    },
    "iot": {
      "@id": "https://www.variotdbs.pl/ref/iot/"
    },
    "iot_taxonomy": {
      "@id": "https://www.variotdbs.pl/ref/iot_taxonomy/"
    },
    "patch": {
      "@id": "https://www.variotdbs.pl/ref/patch/"
    },
    "problemtype_data": {
      "@id": "https://www.variotdbs.pl/ref/problemtype_data/"
    },
    "references": {
      "@id": "https://www.variotdbs.pl/ref/references/"
    },
    "sources": {
      "@id": "https://www.variotdbs.pl/ref/sources/"
    },
    "sources_release_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_release_date/"
    },
    "sources_update_date": {
      "@id": "https://www.variotdbs.pl/ref/sources_update_date/"
    },
    "threat_type": {
      "@id": "https://www.variotdbs.pl/ref/threat_type/"
    },
    "title": {
      "@id": "https://www.variotdbs.pl/ref/title/"
    },
    "type": {
      "@id": "https://www.variotdbs.pl/ref/type/"
    }
  },
  "@id": "https://www.variotdbs.pl/vuln/VAR-201606-0391",
  "affected_products": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/affected_products#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "model": "opensuse",
        "scope": "eq",
        "trust": 1.8,
        "vendor": "opensuse",
        "version": "13.2"
      },
      {
        "model": "leap",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "opensuse",
        "version": "42.1"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "12.04"
      },
      {
        "model": "glibc",
        "scope": "lt",
        "trust": 1.0,
        "vendor": "gnu",
        "version": "2.24"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "14.04"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "18.04"
      },
      {
        "model": "ubuntu linux",
        "scope": "eq",
        "trust": 1.0,
        "vendor": "canonical",
        "version": "16.04"
      },
      {
        "model": "c library",
        "scope": null,
        "trust": 0.8,
        "vendor": "gnu",
        "version": null
      },
      {
        "model": "glibc",
        "scope": null,
        "trust": 0.6,
        "vendor": "gnu",
        "version": null
      },
      {
        "model": "big-ip afm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "security network controller 1.0.3361m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-ip gtm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip analytics build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.110.104.180"
      },
      {
        "model": "big-ip psm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip aam build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip psm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip gtm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf7",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip apm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip afm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.1209"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip asm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip link controller build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      },
      {
        "model": "big-ip apm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip link controller hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip aam hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip link controller hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-iq device",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.5"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.3361"
      },
      {
        "model": "big-ip pem hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.13-34"
      },
      {
        "model": "big-iq device",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.2"
      },
      {
        "model": "big-ip pem hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.0"
      },
      {
        "model": "glibc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "gnu",
        "version": "2.24"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.3394"
      },
      {
        "model": "big-ip afm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip apm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip apm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-iq device",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip aam hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip aam hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip afm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      },
      {
        "model": "big-ip asm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "ne",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.30.7-23"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.16-37"
      },
      {
        "model": "big-ip psm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip afm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip gtm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "security virtual server protection for vmware",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.1.0.1"
      },
      {
        "model": "big-ip pem hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.25-57"
      },
      {
        "model": "big-ip ltm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.18-43"
      },
      {
        "model": "big-ip webaccelerator hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip edge gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip afm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip link controller hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip apm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip link controller hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip afm build 685-hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.40"
      },
      {
        "model": "big-iq device hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "arx",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "6.4"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.11-28"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-iq security",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.5"
      },
      {
        "model": "big-ip link controller hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip dns build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      },
      {
        "model": "big-ip afm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.110.104.180"
      },
      {
        "model": "big-ip pem hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security network controller 1.0.3350m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-ip dns",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip edge gateway 10.2.3-hf1",
        "scope": null,
        "trust": 0.3,
        "vendor": "f5",
        "version": null
      },
      {
        "model": "arx",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "6.3"
      },
      {
        "model": "big-ip link controller hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip aam hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-iq security",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip afm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip edge gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip wom",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip asm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.30.0-13"
      },
      {
        "model": "big-ip afm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip pem hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "arx",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "6.2"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip analytics hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip aam build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip asm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip analytics hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip link controller hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip gtm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip gtm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.110.104.180"
      },
      {
        "model": "big-ip aam hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip apm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip analytics hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip apm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip wom",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.15-36"
      },
      {
        "model": "big-ip aam hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip link controller hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "security network controller 1.0.3387m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "security network controller 1.0.3379m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-iq device",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.3"
      },
      {
        "model": "big-ip apm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.0"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip analytics hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip gtm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip gtm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip afm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip webaccelerator",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip link controller hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip aam hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip apm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.1768"
      },
      {
        "model": "android",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "google",
        "version": "0"
      },
      {
        "model": "big-ip edge gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip apm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "websafe",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "1.0"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.2919"
      },
      {
        "model": "big-ip link controller hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip asm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip aam hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "mobilesafe",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "1.0"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.30.2-9"
      },
      {
        "model": "big-ip webaccelerator",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip asm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-iq cloud hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip asm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip apm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "linux lts amd64",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ubuntu",
        "version": "12.04"
      },
      {
        "model": "big-ip apm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.110.104.180"
      },
      {
        "model": "big-ip aam build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "big-ip edge gateway hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip gtm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip apm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip gtm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-iq security",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.3"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.29-9"
      },
      {
        "model": "big-ip link controller hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.3387"
      },
      {
        "model": "big-ip psm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-iq cloud hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip asm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip ltm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "security network controller 1.0.3352m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-ip asm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip afm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip apm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip afm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip aam hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip asm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip apm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip analytics hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip asm hf6",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip afm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip afm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip afm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip analytics hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip aam build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.110.104.180"
      },
      {
        "model": "big-ip apm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip pem hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip aam hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security virtual server protection for vmware",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.1"
      },
      {
        "model": "big-ip psm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-iq centralized management",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.6"
      },
      {
        "model": "big-ip analytics hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip link controller hf7",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip analytics build 685-hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip link controller hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip pem hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip afm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip analytics hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip apm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip gtm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip analytics hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip link controller hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-iq cloud",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.0"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip asm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip pem hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip dns hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip analytics hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.0"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip psm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip asm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip gtm hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "security network controller 1.0.3394m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "security network controller 1.0.3381m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-iq cloud",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.2"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0"
      },
      {
        "model": "linux lts i386",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ubuntu",
        "version": "12.04"
      },
      {
        "model": "big-ip wom",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-iq centralized management",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "5.0"
      },
      {
        "model": "big-ip afm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip gtm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip aam hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip link controller hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-iq adc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.5"
      },
      {
        "model": "big-ip asm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip aam hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-iq cloud",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.1"
      },
      {
        "model": "big-ip aam hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip analytics hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip afm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.18-49"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip gtm hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip asm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.13-41"
      },
      {
        "model": "big-ip gtm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip afm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "big-ip apm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip psm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip asm hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip wom",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "big-ip dns hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip analytics hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.3381"
      },
      {
        "model": "big-ip analytics build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip aam hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip link controller hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip edge gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-iq cloud and orchestration",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "1.0"
      },
      {
        "model": "big-ip apm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "big-ip analytics hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip webaccelerator",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip gtm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip aam build 685-hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip gtm build 685-hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip edge gateway",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip apm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip asm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      },
      {
        "model": "big-ip afm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip apm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip asm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.4"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.3376"
      },
      {
        "model": "libtirpc",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "redhat",
        "version": "0"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "2.18-42"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "big-ip aam hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip apm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip pem hf5",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip analytics hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.1"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.2"
      },
      {
        "model": "big-ip webaccelerator",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "big-ip psm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip asm build 685-hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip analytics hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-iq security",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.0"
      },
      {
        "model": "big-ip psm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip pem hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip dns",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip wom",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip apm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.1876"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-iq cloud",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.3"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "big-ip wom hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip link controller build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip asm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip psm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-iq security",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.2"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.30.4-12"
      },
      {
        "model": "big-ip link controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "big-ip afm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.2"
      },
      {
        "model": "big-ip afm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip dns hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0"
      },
      {
        "model": "iworkflow",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "2.0"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip apm hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.110.104.180"
      },
      {
        "model": "big-ip gtm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip pem",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5"
      },
      {
        "model": "big-ip gtm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.2.1"
      },
      {
        "model": "big-ip analytics build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      },
      {
        "model": "big-ip apm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.40.1.256"
      },
      {
        "model": "big-ip afm hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security network controller 1.0.3376m",
        "scope": null,
        "trust": 0.3,
        "vendor": "ibm",
        "version": null
      },
      {
        "model": "big-ip aam hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-iq security",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.1"
      },
      {
        "model": "big-ip analytics hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "security network controller",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.0.3379"
      },
      {
        "model": "big-ip ltm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.4"
      },
      {
        "model": "security proventia network active bypass",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "3.0"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.3"
      },
      {
        "model": "big-ip afm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip pem hf4",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "big-ip aam hf3",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-ip afm hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-iq cloud",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.5"
      },
      {
        "model": "big-ip aam hf9",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "enterprise manager",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "3.1.1"
      },
      {
        "model": "big-ip analytics",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip asm hf8",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip apm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip link controller hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-iq security hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip webaccelerator",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "10.2.1"
      },
      {
        "model": "big-ip apm build 685-hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4.1"
      },
      {
        "model": "big-ip pem hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.0.0"
      },
      {
        "model": "big-iq cloud",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip analytics hf10",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.4"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.1.0"
      },
      {
        "model": "big-ip aam",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.6.0"
      },
      {
        "model": "security virtual server protection for vmware",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "ibm",
        "version": "1.1.1"
      },
      {
        "model": "big-iq device hf2",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "4.4"
      },
      {
        "model": "big-ip gtm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.66.204.442"
      },
      {
        "model": "big-ip afm hf1",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.3"
      },
      {
        "model": "big-ip asm",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "11.5.1"
      },
      {
        "model": "big-ip apm build",
        "scope": "eq",
        "trust": 0.3,
        "vendor": "f5",
        "version": "12.01.14.628"
      }
    ],
    "sources": [
      {
        "db": "BID",
        "id": "90737"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "configurations": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/configurations#",
      "children": {
        "@container": "@list"
      },
      "cpe_match": {
        "@container": "@list"
      },
      "data": {
        "@container": "@list"
      },
      "nodes": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "CVE_data_version": "4.0",
        "nodes": [
          {
            "cpe_match": [
              {
                "cpe22Uri": "cpe:/a:gnu:glibc",
                "vulnerable": true
              },
              {
                "cpe22Uri": "cpe:/o:opensuse_project:opensuse",
                "vulnerable": true
              }
            ],
            "operator": "OR"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      }
    ]
  },
  "credits": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/credits#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "The vendor reported these issues.",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      }
    ],
    "trust": 0.6
  },
  "cve": "CVE-2016-4429",
  "cvss": {
    "@context": {
      "cvssV2": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV2#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV2"
      },
      "cvssV3": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/cvss/cvssV3#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/cvssV3/"
      },
      "severity": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/cvss/severity#"
        },
        "@id": "https://www.variotdbs.pl/ref/cvss/severity"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        },
        "@id": "https://www.variotdbs.pl/ref/sources"
      }
    },
    "data": [
      {
        "cvssV2": [
          {
            "accessComplexity": "MEDIUM",
            "accessVector": "NETWORK",
            "authentication": "NONE",
            "author": "nvd@nist.gov",
            "availabilityImpact": "PARTIAL",
            "baseScore": 4.3,
            "confidentialityImpact": "NONE",
            "exploitabilityScore": 8.6,
            "id": "CVE-2016-4429",
            "impactScore": 2.9,
            "integrityImpact": "NONE",
            "severity": "MEDIUM",
            "trust": 1.1,
            "vectorString": "AV:N/AC:M/Au:N/C:N/I:N/A:P",
            "version": "2.0"
          },
          {
            "acInsufInfo": null,
            "accessComplexity": "Low",
            "accessVector": "Network",
            "authentication": "None",
            "author": "NVD",
            "availabilityImpact": "Partial",
            "baseScore": 7.5,
            "confidentialityImpact": "Partial",
            "exploitabilityScore": null,
            "id": "CVE-2016-4429",
            "impactScore": null,
            "integrityImpact": "Partial",
            "obtainAllPrivilege": null,
            "obtainOtherPrivilege": null,
            "obtainUserPrivilege": null,
            "severity": "High",
            "trust": 0.8,
            "userInteractionRequired": null,
            "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P",
            "version": "2.0"
          }
        ],
        "cvssV3": [
          {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "author": "nvd@nist.gov",
            "availabilityImpact": "HIGH",
            "baseScore": 5.9,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "exploitabilityScore": 2.2,
            "id": "CVE-2016-4429",
            "impactScore": 3.6,
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "trust": 1.0,
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          {
            "attackComplexity": "Low",
            "attackVector": "Network",
            "author": "NVD",
            "availabilityImpact": "High",
            "baseScore": 9.8,
            "baseSeverity": "Critical",
            "confidentialityImpact": "High",
            "exploitabilityScore": null,
            "id": "CVE-2016-4429",
            "impactScore": null,
            "integrityImpact": "High",
            "privilegesRequired": "None",
            "scope": "Unchanged",
            "trust": 0.8,
            "userInteraction": "None",
            "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.0"
          }
        ],
        "severity": [
          {
            "author": "nvd@nist.gov",
            "id": "CVE-2016-4429",
            "trust": 1.0,
            "value": "MEDIUM"
          },
          {
            "author": "NVD",
            "id": "CVE-2016-4429",
            "trust": 0.8,
            "value": "Critical"
          },
          {
            "author": "CNNVD",
            "id": "CNNVD-201606-230",
            "trust": 0.6,
            "value": "MEDIUM"
          },
          {
            "author": "VULMON",
            "id": "CVE-2016-4429",
            "trust": 0.1,
            "value": "MEDIUM"
          }
        ]
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "description": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/description#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "Stack-based buffer overflow in the clntudp_call function in sunrpc/clnt_udp.c in the GNU C Library (aka glibc or libc6) allows remote servers to cause a denial of service (crash) or possibly unspecified other impact via a flood of crafted ICMP and UDP packets. GNU glibc is prone to a remote denial-of-service vulnerability. \nSuccessful exploits may allow an attacker to crash the application or to consume excessive memory resources, resulting in a denial-of-service condition. Due to the nature of this issue arbitrary code execution may be possible, but this has not been confirmed. \nGNU glibc 2.24 is vulnerable; other versions may also be affected. \nNote: libtirpc is also affected. (CVE-2016-4429)\n\nIt was discovered that libtirpc incorrectly handled certain inputs. \n(CVE-2018-14622)\n\nIt was discovered that libtirpc incorrectly handled certain strings. \n===========================================================================\nUbuntu Security Notice USN-3239-2\nMarch 21, 2017\n\neglibc, glibc regression\n===========================================================================\n\nA security issue affects these releases of Ubuntu and its derivatives:\n\n- Ubuntu 16.04 LTS\n- Ubuntu 14.04 LTS\n- Ubuntu 12.04 LTS\n\nSummary:\n\nUSN-3239-1 introduced a regression in the GNU C Library. \n\nSoftware Description:\n- glibc: GNU C Library\n- eglibc: GNU C Library\n\nDetails:\n\nUSN-3239-1 fixed vulnerabilities in the GNU C Library. Unfortunately,\nthe fix for CVE-2015-5180 introduced an internal ABI change within\nthe resolver library. This update reverts the change. We apologize\nfor the inconvenience. \n\nPlease note that long-running services that were restarted to compensate\nfor the USN-3239-1 update may need to be restarted again. \n\nOriginal advisory details:\n\n It was discovered that the GNU C Library incorrectly handled the\n strxfrm() function. This issue only affected\n Ubuntu 12.04 LTS and Ubuntu 14.04 LTS. (CVE-2015-8982)\n\n It was discovered that an integer overflow existed in the\n _IO_wstr_overflow() function of the GNU C Library. This issue only affected Ubuntu 12.04 LTS and Ubuntu 14.04\n LTS. (CVE-2015-8983)\n\n It was discovered that the fnmatch() function in the GNU C Library\n did not properly handle certain malformed patterns. An attacker could\n use this to cause a denial of service. This issue only affected Ubuntu\n 12.04 LTS and Ubuntu 14.04 LTS. (CVE-2015-8984)\n\n Alexander Cherepanov discovered a stack-based buffer overflow in the\n glob implementation of the GNU C Library. An attacker could use this\n to specially craft a directory layout and cause a denial of service. \n (CVE-2016-1234)\n\n Florian Weimer discovered a NULL pointer dereference in the DNS\n resolver of the GNU C Library. An attacker could use this to cause\n a denial of service. (CVE-2015-5180)\n\n Michael Petlan discovered an unbounded stack allocation in the\n getaddrinfo() function of the GNU C Library. An attacker could use\n this to cause a denial of service. (CVE-2016-3706)\n\n Aldy Hernandez discovered an unbounded stack allocation in the sunrpc\n implementation in the GNU C Library. An attacker could use this to\n cause a denial of service. (CVE-2016-4429)\n\n Tim Ruehsen discovered that the getaddrinfo() implementation in the\n GNU C Library did not properly track memory allocations. An attacker\n could use this to cause a denial of service. This issue only affected\n Ubuntu 16.04 LTS. (CVE-2016-5417)\n\n Andreas Schwab discovered that the GNU C Library on ARM 32-bit\n platforms did not properly set up execution contexts. An attacker\n could use this to cause a denial of service. (CVE-2016-6323)\n\nUpdate instructions:\n\nThe problem can be corrected by updating your system to the following\npackage versions:\n\nUbuntu 16.04 LTS:\n  libc6                           2.23-0ubuntu7\n\nUbuntu 14.04 LTS:\n  libc6                           2.19-0ubuntu6.11\n\nUbuntu 12.04 LTS:\n  libc6                           2.15-0ubuntu10.17\n\nAfter a standard system update you need to reboot your computer to make\nall the necessary changes. \n\nReferences:\n  http://www.ubuntu.com/usn/usn-3239-2\n  http://www.ubuntu.com/usn/usn-3239-1\n  https://bugs.launchpad.net/bugs/1674532\n\nPackage Information:\n  https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu7\n  https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.11\n  https://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.17\n\n\n",
    "sources": [
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "BID",
        "id": "90737"
      },
      {
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "db": "PACKETSTORM",
        "id": "149244"
      },
      {
        "db": "PACKETSTORM",
        "id": "141812"
      },
      {
        "db": "PACKETSTORM",
        "id": "149243"
      },
      {
        "db": "PACKETSTORM",
        "id": "141758"
      },
      {
        "db": "PACKETSTORM",
        "id": "141749"
      }
    ],
    "trust": 2.43
  },
  "external_ids": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/external_ids#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "db": "NVD",
        "id": "CVE-2016-4429",
        "trust": 3.3
      },
      {
        "db": "BID",
        "id": "102073",
        "trust": 1.7
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093",
        "trust": 0.8
      },
      {
        "db": "AUSCERT",
        "id": "ESB-2020.2223",
        "trust": 0.6
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230",
        "trust": 0.6
      },
      {
        "db": "BID",
        "id": "90737",
        "trust": 0.3
      },
      {
        "db": "VULMON",
        "id": "CVE-2016-4429",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "149244",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "141812",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "149243",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "141758",
        "trust": 0.1
      },
      {
        "db": "PACKETSTORM",
        "id": "141749",
        "trust": 0.1
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "db": "BID",
        "id": "90737"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "PACKETSTORM",
        "id": "149244"
      },
      {
        "db": "PACKETSTORM",
        "id": "141812"
      },
      {
        "db": "PACKETSTORM",
        "id": "149243"
      },
      {
        "db": "PACKETSTORM",
        "id": "141758"
      },
      {
        "db": "PACKETSTORM",
        "id": "141749"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "id": "VAR-201606-0391",
  "iot": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/iot#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": true,
    "sources": [
      {
        "db": "VARIoT devices database",
        "id": null
      }
    ],
    "trust": 0.460834645
  },
  "last_update_date": "2025-04-13T19:56:43.448000Z",
  "patch": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/patch#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "title": "openSUSE-SU-2016:1527",
        "trust": 0.8,
        "url": "https://lists.opensuse.org/opensuse-updates/2016-06/msg00030.html"
      },
      {
        "title": "Bug 20112",
        "trust": 0.8,
        "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=20112"
      },
      {
        "title": "CVE-2016-4429: sunrpc: Do not use alloca in clntudp_call [BZ #20112]",
        "trust": 0.8,
        "url": "https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bc779a1a5b3035133024b21e2f339fe4219fb11c"
      },
      {
        "title": "GNU C Library Fixes for stack-based buffer overflow vulnerabilities",
        "trust": 0.6,
        "url": "http://www.cnnvd.org.cn/web/xxk/bdxqById.tag?id=62185"
      },
      {
        "title": "The Register",
        "trust": 0.2,
        "url": "https://www.theregister.co.uk/2017/12/05/android_december_security_bulletin/"
      },
      {
        "title": "Debian CVElist Bug Report Logs: CVE-2016-4429",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=debian_cvelist_bugreportlogs\u0026qid=2f5b4ce90152a3bb4f395a0901e7e132"
      },
      {
        "title": "Ubuntu Security Notice: libtirpc vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3759-1"
      },
      {
        "title": "Ubuntu Security Notice: libtirpc vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3759-2"
      },
      {
        "title": "Ubuntu Security Notice: eglibc, glibc regression",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3239-2"
      },
      {
        "title": "Ubuntu Security Notice: eglibc regression",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3239-3"
      },
      {
        "title": "Ubuntu Security Notice: eglibc, glibc vulnerabilities",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=ubuntu_security_notice\u0026qid=USN-3239-1"
      },
      {
        "title": "Android Security Bulletins: Android Security Bulletin\u2014December 2017",
        "trust": 0.1,
        "url": "https://vulmon.com/vendoradvisory?qidtp=android_security_bulletins\u0026qid=61f816ea19e8d4351da6636b7a63eb7d"
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      }
    ]
  },
  "problemtype_data": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/problemtype_data#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "problemtype": "CWE-787",
        "trust": 1.0
      },
      {
        "problemtype": "CWE-20",
        "trust": 0.8
      }
    ],
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "references": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/references#",
      "data": {
        "@container": "@list"
      },
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": [
      {
        "trust": 3.0,
        "url": "http://www.securityfocus.com/bid/102073"
      },
      {
        "trust": 2.0,
        "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=20112"
      },
      {
        "trust": 2.0,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21995039"
      },
      {
        "trust": 2.0,
        "url": "https://source.android.com/security/bulletin/2017-12-01"
      },
      {
        "trust": 1.8,
        "url": "https://usn.ubuntu.com/3759-1/"
      },
      {
        "trust": 1.7,
        "url": "http://lists.opensuse.org/opensuse-updates/2016-06/msg00030.html"
      },
      {
        "trust": 1.7,
        "url": "http://lists.opensuse.org/opensuse-updates/2016-07/msg00039.html"
      },
      {
        "trust": 1.7,
        "url": "https://usn.ubuntu.com/3759-2/"
      },
      {
        "trust": 1.7,
        "url": "https://lists.debian.org/debian-lts-announce/2020/06/msg00027.html"
      },
      {
        "trust": 1.0,
        "url": "https://www.oracle.com//security-alerts/cpujul2021.html"
      },
      {
        "trust": 1.0,
        "url": "https://sourceware.org/git/gitweb.cgi?p=glibc.git%3bh=bc779a1a5b3035133024b21e2f339fe4219fb11c"
      },
      {
        "trust": 0.8,
        "url": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2016-4429"
      },
      {
        "trust": 0.8,
        "url": "http://web.nvd.nist.gov/view/vuln/detail?vulnid=cve-2016-4429"
      },
      {
        "trust": 0.7,
        "url": "https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bc779a1a5b3035133024b21e2f339fe4219fb11c"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=8c4901802968b8c8356860ee689b1ef9cd2cbfe4"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=11e7de77bd5ab0a7706a013598f845ad0c4a8b4c"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/la/abl/tianocore/edk2/commit/?id=5c710156bb55b0a085da7c4142b124f3cd986d25"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-3.0/commit/?id=b15f0ff7351eb6b6a8f6694b4cd5ad27145bd439"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0/commit/?id=613f91ebcd0838c2c2bec3657e36dd57fcc6a7ea"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/la//kernel/msm-4.4/commit/?id=aab2cc06db7cb6c7589bef71e65b5acfa58adc33"
      },
      {
        "trust": 0.6,
        "url": "https://source.codeaurora.org/quic/le/oe/recipes/commit/?h=lnx.le.5.3\u0026id=6cfcc1c582a565f5360f7a3977f4a8f42d5245cd"
      },
      {
        "trust": 0.6,
        "url": "http://code.google.com/android/"
      },
      {
        "trust": 0.6,
        "url": "https://www.oracle.com/security-alerts/cpujul2021.html"
      },
      {
        "trust": 0.6,
        "url": "https://www.auscert.org.au/bulletins/esb-2020.2223/"
      },
      {
        "trust": 0.5,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-4429"
      },
      {
        "trust": 0.3,
        "url": "http://www.gnu.org/software/libc/"
      },
      {
        "trust": 0.3,
        "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1337136"
      },
      {
        "trust": 0.3,
        "url": "https://support.f5.com/kb/en-us/solutions/public/k/17/sol17075474.html"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21996174"
      },
      {
        "trust": 0.3,
        "url": "http://www-01.ibm.com/support/docview.wss?uid=swg21996177"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-1234"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-3706"
      },
      {
        "trust": 0.3,
        "url": "http://www.ubuntu.com/usn/usn-3239-1"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8982"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-5417"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2016-6323"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8984"
      },
      {
        "trust": 0.3,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-8983"
      },
      {
        "trust": 0.2,
        "url": "https://usn.ubuntu.com/usn/usn-3759-1"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2017-8779"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2018-14622"
      },
      {
        "trust": 0.2,
        "url": "https://nvd.nist.gov/vuln/detail/cve-2015-5180"
      },
      {
        "trust": 0.1,
        "url": "https://cwe.mitre.org/data/definitions/787.html"
      },
      {
        "trust": 0.1,
        "url": "https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840347"
      },
      {
        "trust": 0.1,
        "url": "https://nvd.nist.gov"
      },
      {
        "trust": 0.1,
        "url": "https://usn.ubuntu.com/usn/usn-3759-2"
      },
      {
        "trust": 0.1,
        "url": "https://bugs.launchpad.net/bugs/1674776"
      },
      {
        "trust": 0.1,
        "url": "http://www.ubuntu.com/usn/usn-3239-3"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.18"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/libtirpc/0.2.5-1.2ubuntu0.1"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/libtirpc/0.2.5-1ubuntu0.1"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/libtirpc/0.2.2-5ubuntu2.1"
      },
      {
        "trust": 0.1,
        "url": "https://bugs.launchpad.net/bugs/1674532"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.11"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.17"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu7"
      },
      {
        "trust": 0.1,
        "url": "http://www.ubuntu.com/usn/usn-3239-2"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.19-0ubuntu6.10"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/glibc/2.23-0ubuntu6"
      },
      {
        "trust": 0.1,
        "url": "https://launchpad.net/ubuntu/+source/eglibc/2.15-0ubuntu10.16"
      }
    ],
    "sources": [
      {
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "db": "BID",
        "id": "90737"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "PACKETSTORM",
        "id": "149244"
      },
      {
        "db": "PACKETSTORM",
        "id": "141812"
      },
      {
        "db": "PACKETSTORM",
        "id": "149243"
      },
      {
        "db": "PACKETSTORM",
        "id": "141758"
      },
      {
        "db": "PACKETSTORM",
        "id": "141749"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "sources": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "db": "BID",
        "id": "90737"
      },
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "db": "PACKETSTORM",
        "id": "149244"
      },
      {
        "db": "PACKETSTORM",
        "id": "141812"
      },
      {
        "db": "PACKETSTORM",
        "id": "149243"
      },
      {
        "db": "PACKETSTORM",
        "id": "141758"
      },
      {
        "db": "PACKETSTORM",
        "id": "141749"
      },
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "sources_release_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_release_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2016-06-10T00:00:00",
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "date": "2016-05-18T00:00:00",
        "db": "BID",
        "id": "90737"
      },
      {
        "date": "2016-06-14T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "date": "2018-09-05T22:46:01",
        "db": "PACKETSTORM",
        "id": "149244"
      },
      {
        "date": "2017-03-24T15:02:31",
        "db": "PACKETSTORM",
        "id": "141812"
      },
      {
        "date": "2018-09-05T22:45:49",
        "db": "PACKETSTORM",
        "id": "149243"
      },
      {
        "date": "2017-03-22T14:12:01",
        "db": "PACKETSTORM",
        "id": "141758"
      },
      {
        "date": "2017-03-21T14:50:15",
        "db": "PACKETSTORM",
        "id": "141749"
      },
      {
        "date": "2016-06-12T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "date": "2016-06-10T15:59:05.687000",
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "sources_update_date": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/sources_update_date#",
      "data": {
        "@container": "@list"
      }
    },
    "data": [
      {
        "date": "2021-07-20T00:00:00",
        "db": "VULMON",
        "id": "CVE-2016-4429"
      },
      {
        "date": "2016-05-18T00:00:00",
        "db": "BID",
        "id": "90737"
      },
      {
        "date": "2016-06-14T00:00:00",
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      },
      {
        "date": "2021-07-21T00:00:00",
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      },
      {
        "date": "2025-04-12T10:46:40.837000",
        "db": "NVD",
        "id": "CVE-2016-4429"
      }
    ]
  },
  "threat_type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/threat_type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "remote",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      }
    ],
    "trust": 0.6
  },
  "title": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/title#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "GNU C Library of  sunrpc/clnt_udp.c of  clntudp_call Function vulnerable to stack-based buffer overflow",
    "sources": [
      {
        "db": "JVNDB",
        "id": "JVNDB-2016-003093"
      }
    ],
    "trust": 0.8
  },
  "type": {
    "@context": {
      "@vocab": "https://www.variotdbs.pl/ref/type#",
      "sources": {
        "@container": "@list",
        "@context": {
          "@vocab": "https://www.variotdbs.pl/ref/sources#"
        }
      }
    },
    "data": "buffer error",
    "sources": [
      {
        "db": "CNNVD",
        "id": "CNNVD-201606-230"
      }
    ],
    "trust": 0.6
  }
}

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T05:17:50.332Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://vuldb.com/?id.220246"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://vuldb.com/?ctiid.220246"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=29444"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-0687",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-11-25T15:41:00.523281Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-11-25T15:41:37.840Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "C Library",
          "vendor": "GNU",
          "versions": [
            {
              "status": "affected",
              "version": "2.38"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This vulnerability affects the function __monstartup of the file gmon.c of the component Call Graph Monitor. The manipulation leads to buffer overflow. It is recommended to apply a patch to fix this issue. VDB-220246 is the identifier assigned to this vulnerability. NOTE: The real existence of this vulnerability is still doubted at the moment. The inputs that induce this vulnerability are basically addresses of the running application that is built with gmon enabled. It\u0027s basically trusted input or input that needs an actual security flaw to be compromised or controlled."
        },
        {
          "lang": "de",
          "value": "In GNU C Library 2.38 wurde eine Schwachstelle ausgemacht. Sie wurde als kritisch eingestuft. Das betrifft die Funktion __monstartup der Datei gmon.c der Komponente Call Graph Monitor. Durch Manipulation mit unbekannten Daten kann eine buffer overflow-Schwachstelle ausgenutzt werden. Als bestm\u00f6gliche Massnahme wird Patching empfohlen."
        }
      ],
      "metrics": [
        {
          "cvssV3_0": {
            "attackComplexity": "HIGH",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 4.6,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
            "version": "3.0"
          },
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 4.6,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-120",
              "description": "CWE-120 Buffer Overflow",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-02-24T00:00:00",
        "orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
        "shortName": "VulDB"
      },
      "references": [
        {
          "url": "https://vuldb.com/?id.220246"
        },
        {
          "url": "https://vuldb.com/?ctiid.220246"
        },
        {
          "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=29444"
        },
        {
          "url": "https://patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/"
        }
      ],
      "tags": [
        "disputed"
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
    "assignerShortName": "VulDB",
    "cveId": "CVE-2023-0687",
    "datePublished": "2023-02-06T00:00:00",
    "dateReserved": "2023-02-06T00:00:00",
    "dateUpdated": "2024-11-25T15:41:37.840Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T05:17:50.332Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://vuldb.com/?id.220246"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://vuldb.com/?ctiid.220246"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=29444"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-0687",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-11-25T15:41:00.523281Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-11-25T15:41:37.840Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "C Library",
          "vendor": "GNU",
          "versions": [
            {
              "status": "affected",
              "version": "2.38"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "A vulnerability was found in GNU C Library 2.38. It has been declared as critical. This vulnerability affects the function __monstartup of the file gmon.c of the component Call Graph Monitor. The manipulation leads to buffer overflow. It is recommended to apply a patch to fix this issue. VDB-220246 is the identifier assigned to this vulnerability. NOTE: The real existence of this vulnerability is still doubted at the moment. The inputs that induce this vulnerability are basically addresses of the running application that is built with gmon enabled. It\u0027s basically trusted input or input that needs an actual security flaw to be compromised or controlled."
        },
        {
          "lang": "de",
          "value": "In GNU C Library 2.38 wurde eine Schwachstelle ausgemacht. Sie wurde als kritisch eingestuft. Das betrifft die Funktion __monstartup der Datei gmon.c der Komponente Call Graph Monitor. Durch Manipulation mit unbekannten Daten kann eine buffer overflow-Schwachstelle ausgenutzt werden. Als bestm\u00f6gliche Massnahme wird Patching empfohlen."
        }
      ],
      "metrics": [
        {
          "cvssV3_0": {
            "attackComplexity": "HIGH",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 4.6,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
            "version": "3.0"
          },
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "ADJACENT_NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 4.6,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-120",
              "description": "CWE-120 Buffer Overflow",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-02-24T00:00:00",
        "orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
        "shortName": "VulDB"
      },
      "references": [
        {
          "url": "https://vuldb.com/?id.220246"
        },
        {
          "url": "https://vuldb.com/?ctiid.220246"
        },
        {
          "url": "https://sourceware.org/bugzilla/show_bug.cgi?id=29444"
        },
        {
          "url": "https://patchwork.sourceware.org/project/glibc/patch/20230204114138.5436-1-leo%40yuriev.ru/"
        }
      ],
      "tags": [
        "disputed"
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
    "assignerShortName": "VulDB",
    "cveId": "CVE-2023-0687",
    "datePublished": "2023-02-06T00:00:00",
    "dateReserved": "2023-02-06T00:00:00",
    "dateUpdated": "2024-11-25T15:41:37.840Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}