diff options
Diffstat (limited to 'results/classifier/zero-shot-user-mode/instruction/1661815')
| -rw-r--r-- | results/classifier/zero-shot-user-mode/instruction/1661815 | 32 |
1 files changed, 32 insertions, 0 deletions
diff --git a/results/classifier/zero-shot-user-mode/instruction/1661815 b/results/classifier/zero-shot-user-mode/instruction/1661815 new file mode 100644 index 00000000..29e0b715 --- /dev/null +++ b/results/classifier/zero-shot-user-mode/instruction/1661815 @@ -0,0 +1,32 @@ +instruction: 0.463 +runtime: 0.318 +syscall: 0.219 + + + +Stack address is returned from function translate_one + +The vulnerable version is qemu-2.8.0, and the vulnerable function is in "target-s390x/translate.c". + +The code snippet is as following. + +static ExitStatus translate_one(CPUS390XState *env, DisasContext *s) +{ + const DisasInsn *insn; + ExitStatus ret = NO_EXIT; + DisasFields f; + ... + s->fields = &f; + ... + s->pc = s->next_pc; + return ret; +} + +A stack address, i.e. the address of local variable "f" is returned from current function through the output parameter "s->fields" as a side effect. + +This issue is one kind of undefined behaviors, according the C Standard, 6.2.4 [ISO/IEC 9899:2011] (https://www.securecoding.cert.org/confluence/display/c/DCL30-C.+Declare+objects+with+appropriate+storage+durations) + +This dangerous defect may lead to an exploitable vulnerability. +We suggest sanitizing "s->fields" as null before return. + +Note that this issue is reported by shqking and Zhenwei Zou together. \ No newline at end of file |