2022 eCTF Rules - v1

.pdf

School

Northeastern University *

*We aren’t endorsed by this school

Course

MISC

Subject

Computer Science

Date

Dec 6, 2023

Type

pdf

Pages

25

Uploaded by ProfessorMosquitoPerson1001

Report
2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19))) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Page 1 of 25 2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Challenge Description and Rules: SAFFIRe: a Secure Avionics Flight Firmware Installation Routine
2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Page 2 of 25 Contents 1 Challenge Overview ............................................................................................................................... 4 1.1 Motivational Scenario .................................................................................................................... 4 1.2 Competition Phases ....................................................................................................................... 5 1.2.1 Design Phase .......................................................................................................................... 5 1.2.2 Design Handoff ...................................................................................................................... 5 1.2.3 Attack Phase .......................................................................................................................... 6 2 System Overview ................................................................................................................................... 7 2.1 System Components ...................................................................................................................... 7 2.1.1 Challenge Platform ................................................................................................................ 8 2.1.2 Development Resources ........................................................................................................ 8 2.2 Avionic Device Lifecycle ................................................................................................................. 8 2.2.1 Device Fabrication Trojan Insertion .................................................................................... 9 2.2.2 SAFFIRe Device Creation ........................................................................................................ 9 2.2.3 Firmware and Configuration Image Protection ..................................................................... 9 2.2.4 Aircraft Depot Updates ........................................................................................................ 10 2.2.5 Aircraft Flights ...................................................................................................................... 10 3 Functional Requirements ..................................................................................................................... 10 3.1 System Build ................................................................................................................................. 12 3.2 Device Load .................................................................................................................................. 12 3.3 SAFFIRe Operations ..................................................................................................................... 13 3.3.1 Firmware Protect ................................................................................................................. 13 3.3.2 Configuration Protect .......................................................................................................... 13 3.3.3 Firmware Update ................................................................................................................. 14 3.3.4 Configuration Load .............................................................................................................. 15 3.3.5 Device Boot .......................................................................................................................... 16 3.3.6 Readback .............................................................................................................................. 16 4 Security Requirements ......................................................................................................................... 17 4.1 Confidentiality .............................................................................................................................. 17 4.2 Firmware/Configuration Integrity and Authenticity ................................................................... 17 4.3 Firmware Versioning .................................................................................................................... 17 4.4 Readback Authentication ............................................................................................................ 18
2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Page 3 of 25 5 Attack Phase Operation ....................................................................................................................... 18 5.1 Scenario ....................................................................................................................................... 18 5.2 Design Deployment ...................................................................................................................... 18 6 Scoring ................................................................................................................................................. 19 6.1 Design Phase Flags ....................................................................................................................... 19 6.1.1 Reverse Engineering Challenge ........................................................................................... 20 6.1.2 Side-Channel Analysis Challenge ......................................................................................... 20 6.1.3 Bug Bounty ........................................................................................................................... 20 6.2 Attack Phase Flags ....................................................................................................................... 20 6.2.2 Flag Point Values .................................................................................................................. 22 6.3 Defensive Points .......................................................................................................................... 23 6.4 Documentation Points ................................................................................................................. 23 6.5 Write-Ups ..................................................................................................................................... 23 7 Rules ..................................................................................................................................................... 23 8 Frequently Asked Questions ................................................................................................................ 24
2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Page 4 of 25 1 Challenge Overview 1.1 Motivational Scenario You are part of an elite design and development team at a startup company developing firmware for electronic devices that are used in aircraft (i.e., avionics). The company has had success developing cutting-edge navigation algorithms that will be used worldwide to improve aircraft flight timeliness and cost. However, you have hit a major roadblock during prototyping and testing. Yo u’ve discovered that once your devices ship to airports all over the world you will need to periodically update the in-flight firmware and allow customers to load in flight-specific configurations. How will you support this functionality and ensure that the system is secure? You and your team have been tasked with figuring it out! We need a secure update system the CEO already picked out the name: the Secure Avionics Flight Firmware Installation Routine” (SAFFIRe) . SAFFIRe consists of two parts: 1) the SAFFIRe bootloader for the avionic device and 2) the SAFFIRe host tools. The SAFFIRe bootloader does not run during flight and is instead responsible for installing and launching trustworthy firmware and configurations. Additionally, the bootloader must support a readback mode that lets a legitimate technician request information from the current firmware and configuration. The SAFFIRe host tools allow technicians to package updates and then communicate with the bootloader to install updates and request debug information from the device. Be careful though, as disgruntled employees working in aircraft ground crews may try to install their own malicious firmware and extract your proprietary algorithms, flight configurations, and sensitive device data. Unfortunately, there's one more wrinkle to worry about a recent news article revealed that your hardware manufacturing partner might not be as trustworthy as you’ d like. As a result, some of the hardware that you rely on may contain malicious modifications that impact the security of your system if you aren't careful.
2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Page 5 of 25 1.2 Competition Phases This is a design-build-attack competition with phases for both attack and defense: 1.2.1 Design Phase In the Design Phase, each team must design and implement a system that meets a set of functional requirements and security requirements . Teams will be provided with a reference design that meets the functional requirements but intentionally does not meet any security requirement . Teams may use the reference design as a starting point or build their design from scratch. In either case, the directory structure of the submitted design must match the structure defined in the Technical Specifications Document. During the Design Phase, teams may score points by capturing Design Phase Flags which show that teams are making progress towards a complete design. Flags must be submitted by their deadlines for points to be awarded. New This Year: In addition to the reverse engineering challenges and bug bounty program introduced last year, teams may score points by completing one or more of a series of emulated side-channel analysis challenges. See Section 6.1 for details 1.2.2 Design Handoff Starting March 9 th , each team may submit their completed design to the organizers. The organizers will then verify that their submission meets all functional requirements. If a submitted design passes functional testing, that team moves into the Attack Phase. Therefore, the date and time of transition from Design Phase to Attack Phase may vary between teams. For example: If Team A and Team B both Design Begins January 26th, 2022 Teams design a secure system that meets all the challenge requirements Teams attempt to solve development challenges to retrieve design-phase flags Handoff Begins March 9th, 2022 Teams may submit their designs to the eCTF Organizers Organizers verify that each design has met all the functional requirements Organizers post verified designs for all teams to evaluate during the attack phase Attack Begins immediately after successful completion of Handoff Teams perform a security evaluation of opposing teams' systems Teams demonstrate attacks by retrieving flags Scoreboard closes April 20th, 2022 Awards Ceremony on April 27th, 2022
2022 Collegiate Embedded Capture-The-Flag (eCTF) Challenge Description v1.0 (2022.01.19) © 2022 The MITRE Corporation. All rights reserved. Approved for public release. Distribution unlimited 20-03314-13. Page 6 of 25 submit systems on the Handoff da te, but only Team A’s system passes the tests, t hen only Team A will move into the Attack Phase while Team B remains in the Design Phase until they submit a system that meets all functional requirements. Each submission should include all source code and documentation for the submitted design. This includes all code necessary for building and running the system in accordance with the system functional requirements. The system source code (and optionally the documentation) must reside in a Git repository, and any extra documentation not stored in the repository must be posted along with the submission request on the team’s official MITRE slack channel. Upon receiving a submission, the eCTF organizers will clone and provision the team’s sy stem via their Git repository. Then, the organizers will run a sequence of test cases that validate whether the system meets the functional requirements. Note : The test cases will not check any security requirements . The eCTF organizers will contact the submitting team within two (2) business days after the submission indicating whether the system is accepted or not. 1.2.2.1 Accepted Designs If a system is accepted, the organizers will inform the team and create a Handoff package that includes all source code, all documentation, and all distributed Attack Phase artifacts (See the Technical Specifications Document for more details). The team must approve of the Handoff package before advancing into the Attack Phase. Note: Teams are not allowed to modify their designs after reviewing the Handoff package. The Handoff package serves as the final opportunity for teams to verify that they have not left any sensitive system materials in their repositories that they do not wish to be publicly known. Any changes to the design or functionality of the submission will require going through the full Handoff process (i.e., functional testing) again before moving to the Attack Phase. 1.2.2.2 Rejected Designs If a system is not accepted, the eCTF organizers will inform the team and provide an explanation for why the design did not pass testing. The submitting team must then revise their design and submit a new version to the organizers. 1.2.2.3 Automated Design Testing New This Year! The eCTF organizers will provide teams with access to an automated testing server that they can use to run their systems through test cases before doing a formal submission. This is intended to improve the turnaround time for getting test results and provide teams with a way to better-validate their designs before submitting to the eCTF organizers. More details on how to use the testing server will be provided during the Design Phase. 1.2.3 Attack Phase During the Attack Phase, each design that has been validated during Handoff will be made available to other teams in the Attack Phase for attack. Teams will be able to attack other teams’ designs in two ways: On a physical microcontroller and/or on a server with an emulated microcontroller and aircraft simulation.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help