[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-OPENSUSE-SU-2017:1098-1":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-06T02:55:33.997Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":38,"duplicates":39,"related":40,"reserved_at":9,"published_at":53,"modified_at":54,"state":9,"summary":55,"references_raw":57,"kevs":118,"epss":9,"epss_history":119,"metrics":120,"affected":121},"OPENSUSE-SU-2017:1098-1","Security update for chromium\n\nThis update to Chromium 58.0.3029.81 fixes the following security issues (bsc#1035103):\n\n- CVE-2017-5057: Type confusion in PDFium\n- CVE-2017-5058: Heap use after free in Print Preview\n- CVE-2017-5059: Type confusion in Blink\n- CVE-2017-5060: URL spoofing in Omnibox\n- CVE-2017-5061: URL spoofing in Omnibox\n- CVE-2017-5062: Use after free in Chrome Apps\n- CVE-2017-5063: Heap overflow in Skia\n- CVE-2017-5064: Use after free in Blink\n- CVE-2017-5065: Incorrect UI in Blink\n- CVE-2017-5066: Incorrect signature handing in Networking\n- CVE-2017-5067: URL spoofing in Omnibox\n- CVE-2017-5069: Cross-origin bypass in Blink\n",null,[],[],[],[14,16,18,20,22,24,26,28,30,32,34,36],{"_key":15},"CVE-2017-5057",{"_key":17},"CVE-2017-5058",{"_key":19},"CVE-2017-5059",{"_key":21},"CVE-2017-5060",{"_key":23},"CVE-2017-5061",{"_key":25},"CVE-2017-5062",{"_key":27},"CVE-2017-5063",{"_key":29},"CVE-2017-5064",{"_key":31},"CVE-2017-5065",{"_key":33},"CVE-2017-5066",{"_key":35},"CVE-2017-5067",{"_key":37},"CVE-2017-5069",[],[],[41,42,43,44,45,46,47,48,49,50,51,52],{"_key":15},{"_key":17},{"_key":19},{"_key":21},{"_key":23},{"_key":25},{"_key":27},{"_key":29},{"_key":31},{"_key":33},{"_key":35},{"_key":37},"2017-04-24T17:04:59Z","2026-02-04T04:08:27.498219Z",{"cisa_kev":56,"cisa_ransomware":56,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[58,64,69,74,78,82,86,90,94,98,102,106,110,114],{"url":59,"sources":60,"tags":62},"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/DIJCS6KARJQIDFNZKAUUESRMRV7GVCZC/#DIJCS6KARJQIDFNZKAUUESRMRV7GVCZC",[61],"osv_suse",[63],"Advisory",{"url":65,"sources":66,"tags":67},"https://bugzilla.suse.com/1035103",[61],[68],"REPORT",{"url":70,"sources":71,"tags":72},"https://www.suse.com/security/cve/CVE-2017-5057",[61],[73],"WEB",{"url":75,"sources":76,"tags":77},"https://www.suse.com/security/cve/CVE-2017-5058",[61],[73],{"url":79,"sources":80,"tags":81},"https://www.suse.com/security/cve/CVE-2017-5059",[61],[73],{"url":83,"sources":84,"tags":85},"https://www.suse.com/security/cve/CVE-2017-5060",[61],[73],{"url":87,"sources":88,"tags":89},"https://www.suse.com/security/cve/CVE-2017-5061",[61],[73],{"url":91,"sources":92,"tags":93},"https://www.suse.com/security/cve/CVE-2017-5062",[61],[73],{"url":95,"sources":96,"tags":97},"https://www.suse.com/security/cve/CVE-2017-5063",[61],[73],{"url":99,"sources":100,"tags":101},"https://www.suse.com/security/cve/CVE-2017-5064",[61],[73],{"url":103,"sources":104,"tags":105},"https://www.suse.com/security/cve/CVE-2017-5065",[61],[73],{"url":107,"sources":108,"tags":109},"https://www.suse.com/security/cve/CVE-2017-5066",[61],[73],{"url":111,"sources":112,"tags":113},"https://www.suse.com/security/cve/CVE-2017-5067",[61],[73],{"url":115,"sources":116,"tags":117},"https://www.suse.com/security/cve/CVE-2017-5069",[61],[73],[],[],[],[122],{"ecosystem":123,"name":124,"vendor":125,"product":126,"cpe_part":9,"purl_type":127,"purl_namespace":125,"purl_name":126,"source":9,"versions":128},"SUSE Linux Enterprise","chromium","suse","chromium&distro=SUSE Package Hub 12 SP2","rpm",[129],{"version":130,"is_range":131,"range_type":132,"version_start":9,"version_start_type":9,"version_end":133,"version_end_type":134,"fixed_in":9},"lt58_0_3029_81_14_1",true,"ecosystem","58.0.3029.81-14.1","excluding"]