Common Weakness Enumeration

CWE Glossary Definition

Name of Your Organization:

ValiantSec Technology Co., Ltd

Web Site:

https://codeant.cn/

Compatible Capability:

CodeAnt

Capability home page:

https://codeant.cn/

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):

1. Open the official website of CodeAnt, which is https://codeant.cn/. And you should first click the button "(Login)" in the top right corner, as shown in the Figure-1 .

   

   Figure-1 CodeAnt’s Homepage

2. Click the button "(register)", as shown in the Figure-1.

   

   Figure-2 Login

3. Enter the registration information, click the "(register)" button to register, as shown in the Figure-3.

   

   Figure-3 Registration information

4. After your registrations are registered，the user can login to the CodeAnt system, as shown in the Figure-2.Then the user login and start using our product, as shown in the Figure-4.

   

   Figure-4 CodeAnt’s dashboard

5. Click the "SCA" module to create a new project，and the user can upload the file to analysis，as shown in Figure-5.

   

   Figure-5 Start up new project

6. After the analysis is completed, the user can view the results，as shown in the Figure-6.

   

   Figure-6 Project Scan Result

7. The user can view the CWE information in the vulnerability details area， as shown in the Figure-7.

   

   Figure-7 Vulnerability details

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):

Obtain the latest data released from CWE website and update it to the database in real time to ensure that the CWE data in the system is the latest information，Users also can Click “CWE” link to the CWE official website，as shown in the Figure-8 and Figure-9.

Figure-8 link to CWE

Figure-9 Search CWE information

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):

We release a version every month，we will update the vulnerability database and the CWE identification information. We will try our best to update the most recent CWE content in each version.

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):

CodeAnt is update every month, our customers get updated mapping relations in each version. We use the CWE 4.8 version, which release date is October 28, 2021. Most rules of CWE have been described in Chinese, and the latest update date is August 30, 2022

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):

Our CWE Documentation describes CWE and CWE compatibility at the beginning of this article, by quoting the description of CWE and CWE.As the Same time, users can view the CWE mapping realationship in the platform, also can click the number of CWE to link to the official web, as shown in the Figure 10.

Figure-10 CWE information And link to the CWE website

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):

After the analysis is over, the user searches for the corresponding CWE ID, displays the vulnerability information mapped to the CWE ID, clicks on the vulnerability details, and enters the vulnerability details page to view the vulnerability details. as shown it the Figure 11.

Figure-11 CWE identifier

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):

After the analysis is over, the user searches for the corresponding CWE keywords, displays the vulnerability information mapped to the CWE number, clicks on the vulnerability details, and enters the vulnerability details page to view the vulnerability details. as shown it the Figure 12.

Figure-12 CWE elements

DOCUMENTATION INDEXING OF CWE-RELATED MATERIAL <CR_5.4>

If your documentation includes an index, provide a copy of the items and resources that you have listed under "CWE" in your index. Alternately, provide directions to where these "CWE" items are posted on your web site (recommended):

The supported CWE tags can be displayed in the full text search library. Corresponding to (in the header CWE number) view the list of supported CWE identifiers. As shown in the Figure 13.

Figure-13 CWE details

Type-Specific Capability Questions

FINDING TASKS USING CWE IDENTIFIERS <CR_A.2.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 search for a certain vulnerability through the CWE identifier in "Component Vulnerability" and click on the vulnerability details to view the specific information of the vulnerability. As shown in the Figure 14.

Figure-14 locate tasks

FINDING CWE IDENTIFIERS USING ELEMENTS IN REPORTS <CR_A.2.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 can click on the vulnerability identifier to enter the vulnerability details and view all specific information including the CWE identifier here. As shown in the Figure 15.

Figure-15 determine the associated CWE identifier

GETTING A LIST OF CLAIMED CWE IDENTIFIER COVERAGE <CR_A.2.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):

Users can search for all CWE identifiers in the "Vulnerability Information Details" section through the search bar, and associate them with their corresponding vulnerabilities and components in the CWE identifier list. As shown in the Figure 16.

Figure-16 CWE identifiers list by searching

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

Give detailed examples and explanations of how a user can obtain a listing of all of the CWE identifiers that are associated with the tool's tasks (recommended):

refer to <CR_A.2.3>.

SELECTING TASKS WITH A LIST OF CWE IDENTIFIERS <CR_A.2.7>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CWE identifiers (recommended):

After completing the scanning task, users can enter the project details and locate the task and all its affected components and projects by searching for the CWE identifier inside.

SELECTING TASKS USING INDIVIDUAL CWE IDENTIFIERS <CR_A.2.8>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CWE identifiers (recommended):

After a user locates a component through a certain CWE identifier, they can click on the component name to browse the basic information of the component. They can check the component or click "Cancel All" in the upper left corner to terminate the localization operation.

NON-SUPPORT NOTIFICATION FOR A REQUESTED CWE IDENTIFIER <CR_A.2.9>

Provide a description of how the tool notifies the user that a task associated with a selected CWE identifier cannot be performed (recommended):

If the user fails to search for a certain CWE identifier, the system will inform the user that the CWE identifier does not exist, please re-enter it.

SERVICE COVERAGE DETERMINATION USING CWE IDENTIFIERS <CR_A.3.1>

Give detailed examples and explanations of the different ways that a user can use CWE identifiers to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):

1. Providing a list. Users can view all vulnerabilities(This project) here and view all security elements of the vulnerability by clicking on the CWE identifier. As shown in the Figure 17 and 18.

   

   Figure-17 determine a identifier

   

   Figure-18 all security elements include CWE identifier

2. By search identifier. Users can retrieve identifiers here to find corresponding vulnerabilities. As shown in the Figure 19.

   

   Figure-19 search identifier

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

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

refer to <CR_A.2.2>.

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 service is effective at locating in software (required):

refer to <CR_A.2.3>.

SERVICE'S PRODUCT UTILIZATION DETAILS <CR_A.3.6>

Please provide the name and version number of any product that the service allows users to have direct access to, if that product identifies security elements (recommended):

CodeAnt provides SaaS services, allowing users to choose the product version they want to use on our official website(https://codeant.cn/), including but not limited to community, commercial, and enterprise versions. The most commonly used version currently is the community version v1.12. Each product version has different functionalities, but the CWE identifiers has been associated with the corresponding component.

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):

Users can find or search for a certain CWE identifier in the search bar of "Component Vulnerability". By clicking on this CWE identifier, they can enter the vulnerability details and see its associated components and tasks. As shown in the Figure 20 and 21

Figure-20 search identifier

Figure-21 vulnerability details and its associated components and tasks

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):

CodeAnt provides complete user instructions and API documentation, which users can view on our 'Technical Support' page. (https://doc.codeant.cn/)

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):

refer to <CR_A.2.2>.

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):

If users use CodeAnt online, they can access the knowledge base in real-time through the interface to view the basic information of all CWE identifiers and details. If users use CodeAnt offline, they can update the latest knowledge base information through offline packages. CodeAnt's knowledge base updates data daily from 23:00 to 24:00.

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):

If the package uploaded by the user can be successfully scanned, the detailed information of each component can be viewed, and then the CWE identifier associated with it can be viewed. If the scan fails, the system will automatically record this information and provide feedback to the CodeAnt data group. We will provide user feedback within 24 hours.

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):

We provide detailed instructions on how to search for CWE identifiers and view detailed information in the 《CodeAnt User Manual》. Users can download this user manual on the CodeAnt official website(https://doc.codeant.cn/). Specifically, it includes the following paths:

1. "SCA Analysis - Vulnerability Details - Component Vulnerability - Bug Details".
2. By search identifier. The path is "SCA Analysis - Vulnerability Details - Component Vulnerability - Search bar".

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):

1. Users can export detection reports in 'SCA Analysis'. As shown in the Figure 22.

   

   Figure-22 export detection reports

2. Users can view the basic information of the scan results in the detection report, and view the vulnerability details of each component and its associated CWE identifier. As shown in the Figure-23.

   

   Figure-23 detection reports

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):

refer to <CR_A.2.3>.

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):

refer to <CR_A.2.3>.

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):

refer to <CR_A.2.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: Zhe Wang

Title: Product Manager

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 and to the best of my knowledge, there are no errors in the mapping between our capability's Repository and the CWE identifiers our capability reports, and those CWE identifiers are as specific as possible within the available CWE repository."

Name: Zhe Wang

Title: Product Manager

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 and to the best of my knowledge, normally when our capability reports a specific security element, it is generally correct and normally when an event occurs that is related to a specific security element our capability generally reports it."

Name: Zhe Wang

Title: Product Manager