Binary Code Security Scoring Through Automated CVSS Factor Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for determining the security score of binary software code, such as the Common Vulnerability Scoring Standard (CVSS), rely on manual qualitative assessments that are inefficient and prone to bias, leading to inaccurate risk evaluations.

Innovation Solution

Automatically inspecting binary software code to determine security factors like attack vector, attack complexity, privileges required, user interaction, scope, confidentiality, and integrity, and calculating a security score using these factors to provide an efficient and accurate assessment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If manual qualitative assessment methods (such as CVSS) are used to determine security scores, then human judgment and flexibility are applied, but the process becomes inefficient and prone to bias leading to inaccurate risk evaluations

Engineering Contradiction:
Improvesecurity score accuracyVSAvoidassessment efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent replaces manual human assessment with automated computational analysis. A processing system automatically inspects binary software code, extracts security-relevant features, and calculates security scores using standardized formulas, eliminating human bias and inefficiency while maintaining measurement precision through consistent application of security metrics

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables self-service security assessment where the binary code itself provides the necessary information through automated feature extraction and analysis. The processing system independently evaluates security factors without requiring human intervention, making the assessment process both efficient and reproducible

Inventive Principle:
Principle #25Self-service

2Reliability

If manual qualitative assessment is used, then flexibility in judgment is maintained, but consistency and objectivity are compromised leading to biased evaluations

Engineering Contradiction:
Improveevaluation consistencyVSAvoidassessment process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent transforms subjective qualitative assessments into objective quantitative parameter measurements. By defining specific security factors (attack vector, attack complexity, privileges required, user interaction, scope, confidentiality, integrity, availability) with standardized measurement parameters, the system ensures consistent and objective evaluations across different assessments

Inventive Principle:
Principle #35Parameter changes

3Productivity

If automated inspection is implemented, then efficiency and accuracy are improved, but the complexity of the inspection system increases

Engineering Contradiction:
Improvescoring efficiencyVSAvoidinspection system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the security assessment process into distinct modular components: feature extraction module, security factor determination module, and score calculation module. Each module handles specific aspects of the inspection, making the overall complex system manageable and maintainable while achieving high productivity through automated processing

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12608482B2Determining a security score in binary software code
Publication Date: 2026.04.21 BLACKBERRY LTD
  • US12608482B2 patent drawing
  • US12608482B2 patent drawing
  • US12608482B2 patent drawing

AI summary

Systems, methods, and software can be used to determine a security score of a binary software code. In some aspects, a computer-implemented method comprises: receiving a binary software code; inspecting the binary software code to determine at least one Common Vulnerability Scoring Standard (CVSS) factor; and determining a CVSS score based on the at least one CVSS factor.