Abstract: A device includes one or more processors configured to: receive source code including a section of source code associated with at least one bug or vulnerability; generate a formatted code section based at least partly on the section of source code associated with at least one bug or vulnerability; identify a matching patch model based on the formatted code section; provide the formatted code section to the matching patch model; receive a remedied code section from the matching patch model; and apply the remedied code section to the section of source code associated with at least one bug or vulnerability. Generating the formatted code section based at least partly on the section of source code associated with at least one bug or vulnerability includes: dividing the section of source code into sub-elements; associating type information to the sub-elements to generate tokens; and mapping each token to a unique identifier.

Abstract: An embedded software analyzer (ESA) detects vulnerabilities in software, such as embedded software items (e.g., software that is pre-loaded onto a device or component). Vulnerabilities may include flaws, glitches, weaknesses, and/or other elements that may prevent correct operation or allow an attacker to access or exploit the software (and/or associated devices, components, systems, etc.) The ESA may utilize techniques such as fuzzing and symbolic execution to identify vulnerabilities. The ESA may predict vulnerabilities and prioritize analysis based on the prediction. The ESA may use smart seeding to optimize fuzzing or other analysis. Such smart seeding may include generating optimized inputs for a particular software item. The ESA may apply machine learning to perform, optimize, and/or otherwise implement such analysis techniques.

Abstract: A device includes one or more processors configured to: receive source code including a section of source code associated with at least one bug or vulnerability; generate a formatted code section based at least partly on the section of source code associated with at least one bug or vulnerability; identify a matching patch model based on the formatted code section; provide the formatted code section to the matching patch model; receive a remedied code section from the matching patch model; and apply the remedied code section to the section of source code associated with at least one bug or vulnerability. Generating the formatted code section based at least partly on the section of source code associated with at least one bug or vulnerability includes: dividing the section of source code into sub-elements; associating type information to the sub-elements to generate tokens; and mapping each token to a unique identifier.