Vulnerabilities > Call CC > Chicken > 4.9.0
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-11-22 | CVE-2014-6310 | Classic Buffer Overflow vulnerability in multiple products Buffer overflow in CHICKEN 4.9.0 and 4.9.0.1 may allow remote attackers to execute arbitrary code via the 'select' function. | 7.5 |
| 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-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 |
| 2017-01-10 | CVE-2016-6830 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Call-Cc Chicken The "process-execute" and "process-spawn" procedures in CHICKEN Scheme used fixed-size buffers for holding the arguments and environment variables to use in its execve() call. | 7.5 |
| 2015-08-28 | CVE-2014-9651 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in Call-Cc Chicken 4.10.0/4.9.0/4.9.0.1 Buffer overflow in CHICKEN 4.9.0.x before 4.9.0.2, 4.9.x before 4.9.1, and before 5.0 allows attackers to have unspecified impact via a positive START argument to the "substring-index[-ci] procedures." | 7.5 |