CVE-2017-6949
published 2017-03-16CVE-2017-6949: 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 unmanaged memory…
PriorityP341high8.1CVSS 3.0
AVNACHPRNUINSUCHIHAH
EPSS
1.47%
71.1th percentile
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 unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| call-cc | chicken | — | — |
| chicken | chicken | >= 0 < 4.12.0-0.2 | 4.12.0-0.2 |
| chicken | chicken | >= 0 < 4.12.0-0.2 | 4.12.0-0.2 |
| chicken | chicken | >= 0 < 4.12.0-0.2 | 4.12.0-0.2 |
| chicken | chicken | >= 0 < 4.12.0-0.2 | 4.12.0-0.2 |
| debian | chicken | < chicken 4.12.0-0.2 (bookworm) | chicken 4.12.0-0.2 (bookworm) |
CVSS provenance
nvdv3.08.1HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.1HIGH
vendor_debian8.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-mg7g-v2j9-85r8: An issue was discovered in CHICKEN Scheme through 4
ghsa_unreviewed·2022-05-17
CVE-2017-6949 [HIGH] CWE-119 GHSA-mg7g-v2j9-85r8: An issue was discovered in CHICKEN Scheme through 4
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 unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow.
OSV
CVE-2017-6949: An issue was discovered in CHICKEN Scheme through 4
osv·2017-03-16·CVSS 8.1
CVE-2017-6949 [HIGH] CVE-2017-6949: An issue was discovered in CHICKEN Scheme through 4
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 unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow.
Debian
CVE-2017-6949: chicken - An issue was discovered in CHICKEN Scheme through 4.12.0. When using a nonstanda...
vendor_debian·2017·CVSS 8.1
CVE-2017-6949 [HIGH] CVE-2017-6949: chicken - An issue was discovered in CHICKEN Scheme through 4.12.0. When using a nonstanda...
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 unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow.
Scope: local
bookworm: resolved (fixed in 4.12.0-0.2)
bullseye: resolved (fixed in 4.12.0-0.2)
forky: resolved (fixed in 4.12.0-0.2)
sid: resolved (fixed in 4.12.0-0.2)
trixie: resolved (fixed in 4.12.0-0.2)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme
bugzilla·2017-03-17·CVSS 8.1
CVE-2017-6949 [HIGH] CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme
CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme
An issue was discovered in CHICKEN Scheme through. When using a nonstandard CHICKEN-specific extension to allocate an SRFI-4 vector in unmanaged memory, the vector size would be used in unsanitised form as an argument to malloc(). With an unexpected size, the impact may have been a segfault or buffer overflow.
References:
http://seclists.org/oss-sec/2017/q1/627
http://lists.gnu.org/archive/html/chicken-announce/2017-03/msg00000.html
Discussion:
Created chicken tracking bugs for this issue:
Affects: epel-all [bug 1433279]
Affects: fedora-all [bug 1433280]
---
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat produ
Bugzilla
CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme [epel-all]
bugzilla·2017-03-17·CVSS 8.1
CVE-2017-6949 [HIGH] CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme [epel-all]
CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported
Bugzilla
CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme [fedora-all]
bugzilla·2017-03-17·CVSS 8.1
CVE-2017-6949 [HIGH] CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme [fedora-all]
CVE-2017-6949 chicken: Unchecked size argument in malloc() in CHICKEN Scheme [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple suppor
2017-03-16
Published