Skip to main content

NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.

Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.

U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Formalizing Software Bugs

Published

Author(s)

Irena Bojanova

Abstract

Knowing what makes a software systems vulnerable to attacks is critical, as software vulnerabilities hurt security, reliability, and availability of the system as a whole. In addition, understanding how an adversary operates is essential to effective cyber security. The "software bug" concept applies to the Common Weakness Enumeration (CWE), the Common Vulnerabilities and Exposures (CVE), and the Common Attack Pattern Enumeration and Classification (CAPEC). Need For: (1) Precise descriptions of attacks (CAPECs) that lead to realization of vulnerabilities (CVEs), exposed by software weaknesses (CWEs). (2) Research to explore formalization of CWEs, CVEs, & CAPECs.
Citation
Bugs Framework (BF)

Keywords

Attack, Bug, Security, Vulnerability, Weakness

Citation

Bojanova, I. (2014), Formalizing Software Bugs, Bugs Framework (BF), [online], https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=957118, https://usnistgov.github.io/BF/ (Accessed October 8, 2025)

Issues

If you have any questions about this publication or are having problems accessing it, please contact [email protected].

Created December 8, 2014, Updated December 8, 2023
Was this page helpful?