lowRISC / lowRISC/opentitan

[rom_ext] Setting minimum required BL0 security version should not honor bad request

Open
#21,354 0 comments 0 reactions 0 assignees View on GitHub
prodc-integration SW:ROM_EXT
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

### Description

If the currently active owner firmware image requests a minimum security version that is higher than its current security version, the request to ROM_EXT should be ignored (or return and error). Otherwise, an image could lock itself out of running on the chip.

See also #19585

Contributor guide

Open the contributing guide

Research direction

Trace how ROM_EXT handles the active owner firmware image's requested minimum BL0 security version, then review the related discussion in issue #19585. Done means a request above the image's current security version cannot lock the image out: it is ignored or returns an error, with behavior verified by relevant regression coverage.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.