MétaCan
Menu
Back to cohort

Enhancing Boofuzz Process Monitoring for Closed-Source SCADA System Fuzzing

2023· article· en· W4378191086 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Testing and Debugging Techniques
Canadian institutionsRoyal Military College of Canada
Fundersnot available
KeywordsFuzz testingSCADAComputer scienceContext (archaeology)Software bugProcess (computing)Embedded systemSoftwareComputer securityOperating systemEngineering

Abstract

fetched live from OpenAlex

Past cyber-attacks have demonstrated that Industrial Control and SCADA Systems are high-value targets for modern threat actors. In order to defend these classes of systems, it is necessary to detect and eliminate any pre-existing vulnerabilities before they can be leveraged into zero-day exploits. Different methods exist to find exploitable vulnerabilities in the software that runs these systems, one of which is known as fuzzing – wherein a system under test is exposed to a variety of input streams while simultaneously observed for unexpected behaviours, exceptions, or crashes. The aim of this research is to extend the Boofuzz network protocol-based fuzzing framework in order to effectively monitor a closed-source SCADA HMI endpoint during fuzz testing. Effective monitoring in this context is defined as the automated detection of target crashes during fuzzing which are recorded with an exception description, reproducing steps, and call stack trace. This data minimizes the time required for vulnerabilities discovered during fuzzing to be reproduced, investigated, and rectified by the software vendor. In order to accomplish this aim, our SCADA HMI is first analyzed to identify the fuzzing target and its runtime behaviours. A protocol fuzzer is then custom built for it using Boofuzz, with the existing target process monitor class extended to introduce new log file and debugger-based monitors. These extensions are then tested through fuzz tests of the SCADA HMI, the results from which demonstrate that vulnerabilities can be both automatically detected and recorded with the sufficient level of detail to expedite rectification.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.757
Threshold uncertainty score0.599

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.029
GPT teacher head0.299
Teacher spread0.270 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it