Medium 10 integrity req medium 10 availability req

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: amage Potential [None - High] {0 - 0.5} Target Distribution [None - High] {0 - 1.0} Confidentiality Req. [Medium] (1.0) Integrity Req. [Medium] (1.0) Availability Req. [Low] (0.5) ---------------------------------------------------FORMULA ENVIRONMENTAL SCORE ---------------------------------------------------AdjustedImpact = 10.41*(1-(1-0.66*1)*(1-0.66*1) *(1-0.66*0.5)) == 9.6 AdjustedBase =((0.6*9.6)+(0.4*10.0)–1.5)*1.176 == (9.7) AdjustedTemporal == (9.7*0.95*0.87*1.0) == (8.0) EnvScore = round((8.0+(10-8.0)*{0-0.5})*{0-1}) == (0.00 - 9.0) ---------------------------------------------------- 3.3.3 CVE-2003-0062 Consider CVE-2003-0062: Buffer Overflow in NOD32 Antivirus. NOD32 is an antivirus software application developed by Eset. In February 2003, a buffer overflow vulnerability was discovered in Linux and Unix versions prior to 1.013 that could allow local users to execute arbitrary code with the privileges of the user executing NOD32. To trigger the buffer overflow, the attacker must wait for (or coax) another user (possibly root) to scan a directory path of excessive length. Since the vulnerability is exploitable only to a user locally logged into the system, the Access Vector is “Local”. The Access Complexity is “High” because this vulnerability is not exploitable at the attacker's whim. There is an additional layer of complexity because the attacker must wait for another user to run the virus scanning software. Authentication is set to “None” because the attacker does not need to authenticate to any additional system. If an administrative user were to run the virus scan, causing the buffer overflow, then a full system compromise would be possible. Since the most harmful case must be considered, each of the three Impact metrics is set to “Complete”. Together, these metrics produce a base score of 6.2. The base vector for this vulnerability is therefore: AV:L/AC:H/Au:N/C:C/I:C/A:C. Partial exploit code has been released, so the Exploitability metric is set to “Proof-Of-Concept”. Eset has released updated software, giving a Remediation Level of “Official-Fix” and Report Confidence of “Confirmed”. These three metrics adjust the base score to give a temporal score of 4.9. 19 THE COMMON VULNERABILITY SCORING SYSTEM (CVSS) AND ITS APPLICABILITY TO FEDERAL AGENCY SYSTEMS Assuming that confidentiality, integrity, and availability are roughly equally important for the targeted systems, and depending on the values for Collateral Damage Potential and Target Distribution, the environmental score could vary between 0.0 (“None”, “None”) and 7.5 (“High”, “High”). The results are summarized below. ---------------------------------------------------BASE METRIC EVALUATION SCORE ---------------------------------------------------Access Vector [Local] (0.395) Access Complexity [High] (0.35) Authentication [None] (0.704) Confidentiality Impact [Complete] (0.66) Integrity Impact [Complete] (0.66) Availability Impact...
View Full Document

This document was uploaded on 03/19/2014 for the course IS 4799 at ITT Tech Flint.

Ask a homework question - tutors are online