CVE-2008-1367
published 2008-03-17CVE-2008-1367: gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can…
PriorityP431high7.5CVSS 2.0
AVNACLAuNCPIPAP
EPSS
2.79%
84.8th percentile
gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | glibc | < glibc 2.7-8 (bookworm) | glibc 2.7-8 (bookworm) |
| gnu | gcc | — | — |
| gnu | glibc | >= 0 < 2.7-8 | 2.7-8 |
| gnu | glibc | >= 0 < 2.7-8 | 2.7-8 |
| gnu | glibc | >= 0 < 2.7-8 | 2.7-8 |
| gnu | glibc | >= 0 < 2.7-8 | 2.7-8 |
CVSS provenance
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
osv7.5HIGH
vendor_debian7.5HIGH
vendor_redhat7.5HIGH
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-mh8h-6q9x-8j58: gcc 4
ghsa_unreviewed·2022-05-01
CVE-2008-1367 [HIGH] GHSA-mh8h-6q9x-8j58: gcc 4
gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.
OSV
CVE-2008-1367: gcc 4
osv·2008-03-17·CVSS 7.5
CVE-2008-1367 [HIGH] CVE-2008-1367: gcc 4
gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.
Red Hat
Kernel doesn't clear DF for signal handlers
vendor_redhat·2008-03-05·CVSS 7.5
CVE-2008-1367 [HIGH] Kernel doesn't clear DF for signal handlers
Kernel doesn't clear DF for signal handlers
gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.
Debian
CVE-2008-1367: glibc - gcc 4.3.x does not generate a cld instruction while compiling functions used for...
vendor_debian·2008·CVSS 7.5
CVE-2008-1367 [HIGH] CVE-2008-1367: glibc - gcc 4.3.x does not generate a cld instruction while compiling functions used for...
gcc 4.3.x does not generate a cld instruction while compiling functions used for string manipulation such as memcpy and memmove on x86 and i386, which can prevent the direction flag (DF) from being reset in violation of ABI conventions and cause data to be copied in the wrong direction during signal handling in the Linux kernel, which might allow context-dependent attackers to trigger memory corruption. NOTE: this issue was originally reported for CPU consumption in SBCL.
Scope: local
bookworm: resolved (fixed in 2.7-8)
bullseye: resolved (fixed in 2.7-8)
forky: resolved (fixed in 2.7-8)
sid: resolved (fixed in 2.7-8)
trixie: resolved (fixed in 2.7-8)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2008-1367 Kernel doesn't clear DF for signal handlers
bugzilla·2008-03-13·CVSS 7.5
CVE-2008-1367 [HIGH] CVE-2008-1367 Kernel doesn't clear DF for signal handlers
CVE-2008-1367 Kernel doesn't clear DF for signal handlers
Description of problem:
Jake Edge has reported the following gcc kernel related potential
security issue on LWN:
A change to GCC for a recent release coupled with a kernel bug has created a
messy situation, with possible security implications. GCC changed some
assumptions about x86 processor flags, in accordance with the ABI standard, that
can lead to memory corruption for programs built with GCC 4.3.0. No one has come
up with a way to exploit the flaw, at least yet, but it clearly is a problem
that needs to be addressed.
The problem revolves around the x86 direction flag (DF), which governs whether
block memory operations operate forward through memory or backwards. The main
use for the flag is to support overlapping memory co
Bugzilla
CVE-2008-1367 [RHEL5] Kernel doesn't clear DF for signal handlers
bugzilla·2008-03-05·CVSS 7.5
CVE-2008-1367 [HIGH] CVE-2008-1367 [RHEL5] Kernel doesn't clear DF for signal handlers
CVE-2008-1367 [RHEL5] Kernel doesn't clear DF for signal handlers
The debian folks reported that kernel doesn't ensure direction flag is cleared
upon entry to signal handler, which violates both i?86 and x86_64 ABIs.
Old GCCs conservatively used cld anyway before using any instructions that use
that flag, but GCC 4.3 no longer does that, it relies on the ABI guarantees that
on entry to a function the direction flag must be cleared.
See http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00276.html
Anything that uses std instruction must cld again before calling another
function or before returning from function.
Unfortunately, if async signal is sent while a thread has std flag set, kernel
will start a signal handler with DF flag set.
The fix is addition of regs->eflags &= ~X86_EFLAGS_DF; or si
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469058http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00417.htmlhttp://gcc.gnu.org/ml/gcc-patches/2008-03/msg00428.htmlhttp://gcc.gnu.org/ml/gcc-patches/2008-03/msg00432.htmlhttp://gcc.gnu.org/ml/gcc-patches/2008-03/msg00499.htmlhttp://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=e40cd10ccff3d9fbffd57b93780bee4b7b9bff51http://lists.opensuse.org/opensuse-security-announce/2008-06/msg00006.htmlhttp://lists.opensuse.org/opensuse-security-announce/2008-07/msg00000.htmlhttp://lists.opensuse.org/opensuse-security-announce/2008-07/msg00002.htmlhttp://lists.vmware.com/pipermail/security-announce/2008/000023.htmlhttp://lkml.org/lkml/2008/3/5/207http://lwn.net/Articles/272048/#Commentshttp://marc.info/?l=git-commits-head&m=120492000901739&w=2http://rhn.redhat.com/errata/RHSA-2008-0508.htmlhttp://secunia.com/advisories/30110http://secunia.com/advisories/30116http://secunia.com/advisories/30818http://secunia.com/advisories/30850http://secunia.com/advisories/30890http://secunia.com/advisories/30962http://secunia.com/advisories/31246http://www.redhat.com/support/errata/RHSA-2008-0211.htmlhttp://www.redhat.com/support/errata/RHSA-2008-0233.htmlhttp://www.securityfocus.com/bid/29084http://www.vupen.com/english/advisories/2008/2222/referenceshttps://bugzilla.redhat.com/show_bug.cgi?id=437312https://exchange.xforce.ibmcloud.com/vulnerabilities/41340https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11108http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469058http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00417.htmlhttp://gcc.gnu.org/ml/gcc-patches/2008-03/msg00428.htmlhttp://gcc.gnu.org/ml/gcc-patches/2008-03/msg00432.htmlhttp://gcc.gnu.org/ml/gcc-patches/2008-03/msg00499.htmlhttp://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git%3Ba=commit%3Bh=e40cd10ccff3d9fbffd57b93780bee4b7b9bff51http://lists.opensuse.org/opensuse-security-announce/2008-06/msg00006.htmlhttp://lists.opensuse.org/opensuse-security-announce/2008-07/msg00000.htmlhttp://lists.opensuse.org/opensuse-security-announce/2008-07/msg00002.htmlhttp://lists.vmware.com/pipermail/security-announce/2008/000023.htmlhttp://lkml.org/lkml/2008/3/5/207http://lwn.net/Articles/272048/#Commentshttp://marc.info/?l=git-commits-head&m=120492000901739&w=2http://rhn.redhat.com/errata/RHSA-2008-0508.htmlhttp://secunia.com/advisories/30110http://secunia.com/advisories/30116http://secunia.com/advisories/30818http://secunia.com/advisories/30850http://secunia.com/advisories/30890http://secunia.com/advisories/30962http://secunia.com/advisories/31246http://www.redhat.com/support/errata/RHSA-2008-0211.htmlhttp://www.redhat.com/support/errata/RHSA-2008-0233.htmlhttp://www.securityfocus.com/bid/29084http://www.vupen.com/english/advisories/2008/2222/referenceshttps://bugzilla.redhat.com/show_bug.cgi?id=437312https://exchange.xforce.ibmcloud.com/vulnerabilities/41340https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11108
2008-03-17
Published