summaryrefslogtreecommitdiffhomepage
path: root/fuzzer-verify.c
diff options
context:
space:
mode:
authorMatt Johnston <matt@ucc.asn.au>2018-02-21 21:49:24 +0800
committerMatt Johnston <matt@ucc.asn.au>2018-02-21 21:49:24 +0800
commit05f4e29a52ff806620b1f80ab59797ac1bc8415d (patch)
tree78653f0534a2bf838fc8c61f5c9821f3fad8b037 /fuzzer-verify.c
parentdbc052099291a313295170c67bb122d85f889be7 (diff)
The fuzzer has managed to generated DSS key/signature pairs that
verify. Avoid false positives from bogus keys that wouldn't be used --HG-- branch : fuzz
Diffstat (limited to 'fuzzer-verify.c')
-rw-r--r--fuzzer-verify.c24
1 files changed, 22 insertions, 2 deletions
diff --git a/fuzzer-verify.c b/fuzzer-verify.c
index ed4a9f7..0aa58df 100644
--- a/fuzzer-verify.c
+++ b/fuzzer-verify.c
@@ -29,8 +29,28 @@ int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) {
sign_key *key = new_sign_key();
enum signkey_type type = DROPBEAR_SIGNKEY_ANY;
if (buf_get_pub_key(fuzz.input, key, &type) == DROPBEAR_SUCCESS) {
- /* Don't expect random fuzz input to verify */
- assert(buf_verify(fuzz.input, key, verifydata) == DROPBEAR_FAILURE);
+ if (buf_verify(fuzz.input, key, verifydata) == DROPBEAR_SUCCESS) {
+ /* The fuzzer is capable of generating keys with a signature to match.
+ We don't want false positives if the key is bogus, since a client/server
+ wouldn't be trusting a bogus key anyway */
+ int boguskey = 0;
+
+ if (type == DROPBEAR_SIGNKEY_DSS) {
+ /* So far have seen dss keys with bad p/q/g domain parameters */
+ int pprime, qprime;
+ assert(mp_prime_is_prime(key->dsskey->p, 5, &pprime) == MP_OKAY);
+ assert(mp_prime_is_prime(key->dsskey->q, 18, &qprime) == MP_OKAY);
+ boguskey = !(pprime && qprime);
+ /* Could also check g**q mod p == 1 */
+ }
+
+ if (!boguskey) {
+ printf("Random key/signature managed to verify!\n");
+ abort();
+ }
+
+
+ }
}
sign_key_free(key);
m_malloc_free_epoch(1, 0);