Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

Red Hat, Inc.

Web Site:

http://www.redhat.com/

Compatible Capability:

Red Hat Customer Portal

Capability home page:

https://access.redhat.com

Product Accessibility <CR_2.4>

Provide a short description of how and where your capability is made available to your customers and the public (required):

CWE Identifiers are assigned to Red Hat vulnerabilities with a Common Vulnerability Scoring System v2 (CVSS v2) score higher than or equal to 7. Periodically, after classifying, quantifying, and ranking these weaknesses, we direct all our efforts into dealing with these weaknesses in our products as part of our assessment services, knowledge repositories, software development practices, and education offerings.

Map Currency Indication <CR_6.1>

Describe how and where your capability indicates the most recent CWE content used to create or update its mappings (required):

Information about the CWE List version used, reviews, and updates for the present, and the present CWE coverage for Red Hat Customer Portal are available at: https://access.redhat.com/knowledge/articles/171613.

Map Currency Update Approach <CR_6.2>

Indicate how often you plan on updating the mappings to reflect the current CWE content and describe your approach to keeping reasonably current with the CWE content when mapping them to your repository (recommended):

The CWE coverage for Red Hat Customer Portal is reviewed and updated twice per year, along with the release of a vulnerability assessment report. CWE Identifiers are assigned to Red Hat vulnerabilities using the present CWE coverage at the time of the vulnerability assessment. Thus, references to vulnerabilities are divided into "time slices" based upon the date the vulnerability was assessed and the present CWE coverage at that time.

MAP CURRENCY UPDATE TIME <CR_6.3>

Describe how and where you explain to your customers the timeframe they should expect an update of your capability’s mappings to reflect newly available CWE content (required):

See the answer to <CR_6.1>.

CWE AND COMPATIBILITY DOCUMENTATION <CR_5.1>

Provide a copy, or directions to its location, of where your documentation describes CWE and CWE compatibility for your customers (required):

Documentation for CWE and CWE compatibility are available at: https://access.redhat.com/knowledge/articles/171503.

DOCUMENTATION OF FINDING ELEMENTS USING CWE IDENTIFIERS <CR_5.2>

Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CWE identifiers to find the individual security elements within your capability’s repository (required):

Users may use the Bugzilla search interface at: https://bugzilla.redhat.com/query.cgi, or directly refer to the "Whiteboard" field of a particular vulnerability, such as: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-XXX-XXX. Note that you need to be logged into Bugzilla to be able to see the full "Whiteboard" field.

Alternatively, users can also search in the CVE database application, such as in https://access.redhat.com/security/cve/?cwe=XXX, or individual CVE pages, such as: https://access.redhat.com/security/cve/CVE-XXX-XXX.

DOCUMENTATION OF FINDING CWE IDENTIFIERS USING ELEMENTS <CR_5.3>

Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CWE identifiers associated with individual security elements within your capability’s repository (required):

See the answer to <CR_5.1>.

FINDING TASKS USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CWE identifier (required):

Users can find information about the CWE List version used, reviews, and updates for the present, and the present CWE coverage for Red Hat Customer Portal at: https://access.redhat.com/knowledge/articles/171613.

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CWE identifier for the individual security elements in the report (required):

Users may use the Bugzilla search interface at: https://bugzilla.redhat.com/query.cgi, or directly refer to the "Whiteboard" field of a particular vulnerability, such as: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2009-2692. Note that you need to be logged into Bugzilla to be able to see the full "Whiteboard" field.

Alternatively, users can also search in the CVE database application, such as in https://access.redhat.com/security/cve/?cwe=476, or individual CVE pages, such as: https://access.redhat.com/security/cve/CVE-2009-2692.

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.3.3>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that the owner claims the tool is effective at locating in software (required):

See the answer to <CR_A.3.1>.

GETTING A LIST OF CWE IDENTIFIERS ASSOCIATED WITH TASKS <CR_A.3.4>

Give a detailed explanation of how a user can find the Coverage Claim Representation (CCR) XML document with all of the CWE identifiers that the owner claims the service is effective at locating in software (recommended):

A CCR XML for the CWE coverage for Red Hat Customer Portal is currently not available.

FINDING ONLINE CAPABILITY TASKS USING CWE IDENTIFIERS <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CWE identifier or through an online mapping that links each element of the capability with its associated CWE identifier(s) (required):

See answer to <CR_A.3.2>.

ONLINE CAPABILITY INTERFACE TEMPLATE USAGE <CR_A.4.1.1>

Provide a detailed description of how someone can use your "URL template" to interface to your capability’s search function (recommended):

Examples:

• http://www.example.com/cgi-bin/db-search.cgi?cweid=XXX
• http://www.example.com/cwe/xxx.html

See answer to <CR_A.3.2>.

ONLINE CAPABILITY CGI GET METHOD SUPPORT <CR_A.4.1.2>

If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):

Yes.

FINDING CWE IDENTIFIERS USING ONLINE CAPABILITY ELEMENTS <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CWE Identifiers for the individual security elements in the report (required):

Each CWE element listed in CVE database is linked to the page containing its detailed description at the MITRE web site:

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.4.3>

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE Identifiers that the owner claims the online capability’s repository covers (required):

See answer to <CR_A.3.1>.

USING CCR TO PROVIDE CLAIMED CWE IDENTIFIER COVERAGE <CR_A.4.4>

Give a detailed explanation of how a user can find the Coverage Claim Representation (CCR) XML document with all of the CWE Identifiers that the owner claims the online capability’s repository covers (recommended):

A CCR XML for the CWE coverage for Red Hat Customer Portal is currently not available.

ONLINE CAPABILITY ELEMENT TO CWE IDENTIFIER MAPPING <CR_A.4.5>

If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CWE Identifier(s), otherwise enter N/A (required):

N/A

ELECTRONIC DOCUMENT FORMAT INFO <B.3.1>

Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CWE-related text (required):

See answer to <CR_A.3.2>.

ELECTRONIC DOCUMENT LISTING OF CWE IDENTIFIERS <CR_B.3.2>

If one of the capability’s standard electronic documents only lists security elements by their short names or titles provide example documents that demonstrate how the associated CWE identifiers are listed for each individual security element (required):

See answer to <CR_A.4.2>.

ELECTRONIC DOCUMENT ELEMENT TO CWE IDENTIFIER <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability’s individual elements to the respective CWE identifier(s) (recommended):

See answer to <CR_A.4.2>.

FINDING ELEMENTS USING CWE IDENTIFIERS THROUGH THE GUI <CR_B.4.1>

Give detailed examples and explanations of how the GUI provides a "find" or "search" function for the user to identify your capability’s elements by looking for their associated CWE identifier(s) (required):

See answer to <CR_A.3.2>.

GUI ELEMENT TO CWE IDENTIFIER MAPPING <CR_B.4.2>

Briefly describe how the associated CWE identifiers are listed for the individual security elements or discuss how the user can use the mapping between CWE identifiers and the capability’s elements, also describe the format of the mapping (required):

See answer to <CR_A.4.2>.

GUI EXPORT ELECTRONIC DOCUMENT FORMAT INFO <CR_B.4.3>

Provide details about the different electronic document formats that you provide for exporting or accessing CWE-related data and describe how they can be searched for specific CWE-related text (recommended):

See answer to <CR_A.4.2>.

STATEMENT OF COMPATIBILITY <CR_2.11>

Have an authorized individual sign and date the following Compatibility Statement (required):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Josh Bressers

Title: Product Security, Team Lead

STATEMENT OF ACCURACY <CR_3.4>

Have an authorized individual sign and date the following accuracy Statement (recommended):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Josh Bressers

Title: Product Security, Team Lead

STATEMENT ON FALSE-POSITIVES AND FALSE-NEGATIVES <CR_B.2.10> and/or <CR_B.3.7>

FOR TOOLS AND SERVICES ONLY — Have an authorized individual sign and date the following statement about your tools efficiency in identification of security elements (required):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CWE Compatibility Requirements as well as all of the additional mandatory CWE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Josh Bressers

Title: Product Security, Team Lead