{"id":1514,"date":"2006-10-11T00:00:00","date_gmt":"2006-10-11T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/10\/11\/oracle-commits-to-rating-vulnerabilities\/"},"modified":"2021-12-30T11:39:31","modified_gmt":"2021-12-30T11:39:31","slug":"oracle-commits-to-rating-vulnerabilities","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2006\/10\/11\/oracle-commits-to-rating-vulnerabilities\/","title":{"rendered":"Oracle commits to rating vulnerabilities"},"content":{"rendered":"<p>Database maker Oracle announced that the company&#8217;s quarterly Critical Patch Updates (CPUs) will give administrators more guidance by providing a summary of the flaws fixed in the update and grading the threat posed by each issue.  The company will grade the severity of each flaw using the Common Vulnerability Scoring System (CVSS), highlight flaws that are remotely exploitable by an unauthenticated user and summarize the vulnerabilities fixed by a patch.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;Oracle introduced these changes as the result of feedback we received from many of our customers,&#8221; Eric Maurice, manager for security in the company&#8217;s Global Technology Business Unit, stated in the blog.<\/p>\n<p>&#8220;We hope that these changes will help our customers assess the criticality of the vulnerabilities resolved with each CPU and help them obtain patching decisions from their senior management more quickly.&#8221;<\/p>\n<p>http:\/\/www.securityfocus.com\/brief\/326<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1514","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1514","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1514"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1514\/revisions"}],"predecessor-version":[{"id":4001,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1514\/revisions\/4001"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1514"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1514"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1514"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}