CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · Vendors

Call-cc
21 vulnerabilities.

All published vulnerabilities with a CVE number in Call-cc products, newest first, with severity and references.

CVESummaryPublishedCVSS
CVE-2022-45145Call-cc Chicken: egg-compile.scm in CHICKEN 5.x before 5.3.1 allows arbitrary OS command execution during package installation via escape characters in a .egg file.2022-12-109.8
CVE-2017-11343Call-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 …2017-07-177.5
CVE-2017-9334Call-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, …2017-06-017.5
CVE-2017-6949Call-cc Chicken: An issue was discovered in CHICKEN Scheme through 4.12.0. When using a nonstandard CHICKEN-specific extension to allocate an SRFI-4 vector in …2017-03-168.1
CVE-2016-6831Call-cc Chicken: The "process-execute" and "process-spawn" procedures did not free memory correctly when the execve() call failed, resulting in a memory leak. This …2017-01-107.5
CVE-2016-6830Call-cc Chicken: The "process-execute" and "process-spawn" procedures in CHICKEN Scheme used fixed-size buffers for holding the arguments and environment variables …2017-01-109.8
CVE-2016-6287Call-cc Http-client: The "http-client" egg always used a HTTP_PROXY environment variable to determine whether HTTP traffic should be routed via a proxy, even when …2017-01-107.5
CVE-2016-6286Call-cc Http-client: The "spiffy-cgi-handlers" egg would convert a nonexistent "Proxy" header to the HTTP_PROXY environment variable, which would allow attackers to …2017-01-107.5
CVE-2015-8235Call-cc Spiffy: Directory traversal vulnerability in Spiffy before 5.4.2017-06-077.5
CVE-2015-4556Call-cc Chicken: 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).2017-03-297.5
CVE-2014-9651Call-cc Chicken: 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 …2015-08-287.5
CVE-2014-6310Call-cc Chicken: Buffer overflow in CHICKEN 4.9.0 and 4.9.0.1 may allow remote attackers to execute arbitrary code via the 'select' function.2019-11-229.8
CVE-2014-3776Call-cc Chicken: Buffer overflow in the "read-u8vector!" procedure in the srfi-4 unit in CHICKEN stable 4.8.0.7 and development snapshots before 4.9.1 allows remote …2014-05-207.5
CVE-2013-4385Call-cc Chicken: Buffer overflow in the "read-string!" procedure in the "extras" unit in CHICKEN stable before 4.8.0.5 and development snapshots before 4.8.3 allows …2013-10-097.5
CVE-2013-2075Call-cc Chicken: Multiple buffer overflows in the (1) R5RS char-ready, (2) tcp-accept-ready, and (3) file-select procedures in Chicken through 4.8.0.3 allows …2019-10-318.8
CVE-2013-2024Call-cc Chicken: OS command injection vulnerability in the "qs" procedure from the "utils" module in Chicken before 4.9.0.2019-10-318.8
CVE-2013-1874Call-cc Chicken: Untrusted search path vulnerability in csi in Chicken before 4.8.2 allows local users to execute arbitrary code via a Trojan horse .csirc in the …2014-09-294.4
CVE-2012-6125Call-cc Chicken: Chicken before 4.8.0 is susceptible to algorithmic complexity attacks related to hash table collisions.2019-10-319.8
CVE-2012-6124Call-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. NOTE: the vendor states …2019-10-315.3
CVE-2012-6123Call-cc Chicken: Chicken before 4.8.0 does not properly handle NUL bytes in certain strings, which allows an attacker to conduct "poisoned NUL byte attack."2019-10-316.5
CVE-2012-6122Call-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 …2019-10-317.5

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.

Too many to
patch at once?

Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.