Vulnerabilities > Call CC > Chicken > Medium
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-10-31 | CVE-2012-6124 | Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) vulnerability in Call-Cc Chicken A casting error in Chicken before 4.8.0 on 64-bit platform caused the random number generator to return a constant value. | 5.0 |
| 2019-10-31 | CVE-2012-6123 | Improper Input Validation vulnerability in multiple products Chicken before 4.8.0 does not properly handle NUL bytes in certain strings, which allows an attacker to conduct "poisoned NUL byte attack." | 5.0 |
| 2019-10-31 | CVE-2012-6122 | Classic Buffer Overflow vulnerability in Call-Cc Chicken Buffer overflow in the thread scheduler in Chicken before 4.8.0.1 allows attackers to cause a denial of service (crash) by opening a file descriptor with a large integer value. | 5.0 |
| 2017-07-17 | CVE-2017-11343 | Algorithmic Complexity vulnerability in Call-Cc Chicken Due to an incomplete fix for CVE-2012-6125, all versions of CHICKEN Scheme up to and including 4.12.0 are vulnerable to an algorithmic complexity attack. | 5.0 |
| 2017-06-01 | CVE-2017-9334 | Improper Input Validation vulnerability in Call-Cc Chicken An incorrect "pair?" check in the Scheme "length" procedure results in an unsafe pointer dereference in all CHICKEN Scheme versions prior to 4.13, which allows an attacker to cause a denial of service by passing an improper list to an application that calls "length" on it. | 5.0 |
| 2017-03-29 | CVE-2015-4556 | Improper Input Validation vulnerability in Call-Cc Chicken 4.8.0/4.9.0 The string-translate* procedure in the data-structures unit in CHICKEN before 4.10.0 allows remote attackers to cause a denial of service (crash). | 5.0 |
| 2017-03-16 | CVE-2017-6949 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Call-Cc Chicken 4.12.0 An issue was discovered in CHICKEN Scheme through 4.12.0. | 6.8 |
| 2017-01-10 | CVE-2016-6831 | Resource Exhaustion vulnerability in Call-Cc Chicken The "process-execute" and "process-spawn" procedures did not free memory correctly when the execve() call failed, resulting in a memory leak. | 5.0 |