Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement fuzzing via cargo fuzz #34

Open
00xc opened this issue May 10, 2023 · 1 comment
Open

Implement fuzzing via cargo fuzz #34

00xc opened this issue May 10, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@00xc
Copy link
Member

00xc commented May 10, 2023

Identify interesting interfaces to fuzz, from a security perspective, and implement fuzzing test cases for them. These should ideally include at least data coming from the hypervisor, guest kernel and VMPL0 userspace.

@00xc 00xc added the enhancement New feature or request label May 10, 2023
@joergroedel
Copy link
Member

Thanks for proposing this, fuzzing would be great to have. In addition, stress-tests are also something worth looking into.

@00xc 00xc self-assigned this Sep 14, 2023
00xc added a commit to 00xc/svsm that referenced this issue Oct 2, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

The fuzzing harnesses, much like regular tests, are built as userspace
binaries, which means we need to disable the SVSM allocator in favor
of the standard Rust allocator.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 2, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

The fuzzing harnesses, much like regular tests, are built as userspace
binaries, which means we need to disable the SVSM allocator in favor
of the standard Rust allocator.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 3, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

The fuzzing harnesses, much like regular tests, are built as
userspace binaries, which means we need to enable some conditional
compilation, namely disabling the SVSM allocator in favor of the
standard Rust allocator, as well as enabling certain helper test
functions.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 11, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 12, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 14, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 14, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 14, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 16, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 17, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 17, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
00xc added a commit to 00xc/svsm that referenced this issue Oct 18, 2023
Add fuzzing to the COCONUT SVSM project via cargo-fuzz. This commit
adds the base infrastructure for fuzzing, as well as two harnesses
for testing the fw_meta and ACPI table interfaces respectively.

This works towards issue coconut-svsm#34.

Signed-off-by: Carlos López <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants