CWE

Common Weakness Enumeration

A Community-Developed Dictionary of Software Weakness Types

Common Weakness Scoring System
Common Weakness Risk Analysis Framework
Home > Compatibility > CWE-Compatible Products and Services  

Name of Your Organization:

High-Tech Bridge SA

Web Site:

https://www.htbridge.com

Compatible Capability:

High-Tech Bridge Security Advisories

Capability home page:

https://www.htbridge.com/advisory/

General Capability Questions

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

The CWE capability is publicly available on our website: https://www.htbridge.com/advisory/

Mapping Questions

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

In every HTB Security Advisory we have "Vulnerability Type" field that contains vulnerability type name and corresponding CWE-ID.

For example for this HTB Advisory, https://www.htbridge.com/advisory/HTB23094, users clearly see CWE-IDs in the body of the webpage:

Vulnerability Type: Cross-Site Request Forgery [CWE-352]
Cross-Site Scripting [CWE-79]

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

As all of the Security Advisories published on our website are provided and discovered by High-Tech Bridge Security Research Lab, we do not expect to update CWE-IDs after they are assigned and published by our security researchers.

The only exception is if we receive a demand or indication of wrong CWE-ID usage from MITRE. In this case our technical team is joinable by advisory@htbridge.com email, and is ready to react rapidly on any demand coming from MITRE.

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

As already mentioned above we are normally not supposed to update the CWE-IDs, with the only exception if we are demanded to do so by MITRE. In this case response time of our technical team is less than 8 working hours. This time is usually sufficient to apply any change or update received from MITRE.

Documentation Questions

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

"Related Links" frame of every webpage in /advisory/ section of our website displays a hyperlink "About CWE" pointing to MITRE’s "About CWE" webpage: http://cwe.mitre.org/about/index.html.

We consider this webpage the most appropriate, complete and useful for users looking for CWE-related documentation. We prefer to send users directly to the original source than to copy-paste the information.

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

On the main webpage of our Security Advisories we have a search function. Search can be performed by:

  1. CVE-ID
  2. HTB-ID
  3. Advisory Name
  4. CWE-ID

The following URL, https://www.htbridge.com/advisory/?cveid=&htbid=&vulnname=&cweid=89&action=search, will display all of the security advisories that contain 1 or more vulnerabilities with CWE-89.

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

Search Function on the main webpage of our Security Advisories is very comprehensible and user-friendly.

Its usage is obvious and does not require additional documentation: https://www.htbridge.com/advisory/

Online Capability Questions

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

As already explained in the CR_5.2 section of this document, the main webpage of our Security Advisories provides users with an obvious and simple search mechanism that enables everybody to search our advisories by a specific CWE-ID: https://www.htbridge.com/advisory/

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

The Search Function allows displaying all advisories with a specific CWE-ID.

The following URL enables any user to search advisories by CWE-ID:
https://www.htbridge.com/advisory/?cveid=&htbid=&vulnname=&cweid=TYPE_CWE_ID_HERE&action=search

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 security element (in our case "security element" is HTB Security Advisory) has a "Vulnerability Type" field with listed CWE-ID(s).

Any HTB Security Advisory can be used as an example:
https://www.htbridge.com/advisory/HTB23072
https://www.htbridge.com/advisory/HTB23084

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

User can see a CWE-ID for every Vulnerability Type (with or without assigned CVE-ID) in the body of webpage of a security advisory.

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

Media Questions

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

Security Advisories are publicly provided in:

  1. HTML format on the main page of HTB Security Advisories: https://www.htbridge.com/advisory/
  2. RSS format on FeedBurner:

    http://feeds.feedburner.com/htbridge_disclosed_advisories

    http://feeds.feedburner.com/high-tech_bridge_security_advisories

Corresponding CWE-ID(s) are always properly indicated in the "Vulnerability Type" field for both formats.

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

CWE-ID(s) are always clearly indicated on every HTB Security Advisory webpage.
Example: https://www.htbridge.com/advisory/HTB23100

Graphical User Interface (GUI) Questions

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

The main page of High-Tech Bridge Security Advisories:
https://www.htbridge.com/advisory/

Provides any user with the following GUI:

  • Input boxes "CVE-ID", "HTB-ID", "Name", "CWE-ID"
  • Button "Search"

With a search function that permits to find security advisories by CVE-ID, HTB-ID, CWE-ID and advisory name.

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

CWE-ID(s) are clearly visible in the body of any security advisory in the "Vulnerability Type" field, both in HTML and RSS formats.

Questions for Signature

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: Ilia Kolochenko

Title: CEO

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: Ilia Kolochenko

Title: CEO

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: Ilia Kolochenko

Title: CEO

Page Last Updated: [an error occurred while processing this directive]