diff options
| author | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
|---|---|---|
| committer | Christian Krinitsin <mail@krinitsin.com> | 2025-07-03 07:27:52 +0000 |
| commit | d0c85e36e4de67af628d54e9ab577cc3fad7796a (patch) | |
| tree | f8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/performance/2946 | |
| parent | 7f4364274750eb8cb39a3e7493132fca1c01232e (diff) | |
| download | qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip | |
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/performance/2946')
| -rw-r--r-- | results/classifier/gemma3:12b/performance/2946 | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/performance/2946 b/results/classifier/gemma3:12b/performance/2946 new file mode 100644 index 000000000..7fa840ba7 --- /dev/null +++ b/results/classifier/gemma3:12b/performance/2946 @@ -0,0 +1,11 @@ + +crypto/aes.c (used for emulating aes instructions) has a timing side-channel +Description of problem: +https://gitlab.com/qemu-project/qemu/-/blob/a9cd5bc6399a80fcf233ed0fffe6067b731227d8/crypto/aes.c#L1021 + +much of the code in crypto/aes.c accesses memory arrays where the array index is based on the secret data being encrypted/decrypted. because of cpu caches and other things that can delay memory accesses based on their address, this is a timing side-channel, potentially allowing leaking secrets over a network based on timing how long cryptography operations take. + +compare to openssl which uses an algorithm where its execution time doesn't depend on the data being processed: +https://github.com/openssl/openssl/commit/0051746e03c65f5970d8ca424579d50f58a877e0 + +I initially reported this as a security issue, but was told that since it's only used by TCG, it isn't a security issue, since TCG isn't considered secure. |