ID CVE-2009-4020
Summary Stack-based buffer overflow in the hfs subsystem in the Linux kernel 2.6.32 allows remote attackers to have an unspecified impact via a crafted Hierarchical File System (HFS) filesystem, related to the hfs_readdir function in fs/hfs/dir.c.
References
Vulnerable Configurations
  • cpe:2.3:o:linux:linux_kernel:2.6.32:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:2.6.32:*:*:*:*:*:*:*
CVSS
Base: 7.8 (as of 19-09-2017 - 01:29)
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Buffer Manipulation
    An adversary manipulates an application's interaction with a buffer in an attempt to read or modify data they shouldn't have access to. Buffer attacks are distinguished in that it is the buffer space itself that is the target of the attack rather than any code responsible for interpreting the content of the buffer. In virtually all buffer attacks the content that is placed in the buffer is immaterial. Instead, most buffer attacks involve retrieving or providing more input than can be stored in the allocated buffer, resulting in the reading or overwriting of other unintended program memory.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE COMPLETE
cvss-vector via4 AV:N/AC:L/Au:N/C:N/I:N/A:C
oval via4
  • accepted 2013-04-29T04:01:31.508-04:00
    class vulnerability
    contributors
    • name Aharon Chernin
      organization SCAP.com, LLC
    • name Dragos Prisaca
      organization G2, Inc.
    definition_extensions
    • comment The operating system installed on the system is Red Hat Enterprise Linux 4
      oval oval:org.mitre.oval:def:11831
    • comment CentOS Linux 4.x
      oval oval:org.mitre.oval:def:16636
    • comment Oracle Linux 4.x
      oval oval:org.mitre.oval:def:15990
    • comment The operating system installed on the system is Red Hat Enterprise Linux 5
      oval oval:org.mitre.oval:def:11414
    • comment The operating system installed on the system is CentOS Linux 5.x
      oval oval:org.mitre.oval:def:15802
    • comment Oracle Linux 5.x
      oval oval:org.mitre.oval:def:15459
    description Stack-based buffer overflow in the hfs subsystem in the Linux kernel 2.6.32 allows remote attackers to have an unspecified impact via a crafted Hierarchical File System (HFS) filesystem, related to the hfs_readdir function in fs/hfs/dir.c.
    family unix
    id oval:org.mitre.oval:def:10091
    status accepted
    submitted 2010-07-09T03:56:16-04:00
    title Stack-based buffer overflow in the hfs subsystem in the Linux kernel 2.6.32 allows remote attackers to have an unspecified impact via a crafted Hierarchical File System (HFS) filesystem, related to the hfs_readdir function in fs/hfs/dir.c.
    version 30
  • accepted 2014-01-20T04:01:29.211-05:00
    class vulnerability
    contributors
    • name J. Daniel Brown
      organization DTCC
    • name Chris Coffin
      organization The MITRE Corporation
    definition_extensions
    comment VMware ESX Server 4.0 is installed
    oval oval:org.mitre.oval:def:6293
    description Stack-based buffer overflow in the hfs subsystem in the Linux kernel 2.6.32 allows remote attackers to have an unspecified impact via a crafted Hierarchical File System (HFS) filesystem, related to the hfs_readdir function in fs/hfs/dir.c.
    family unix
    id oval:org.mitre.oval:def:6750
    status accepted
    submitted 2010-06-01T17:30:00.000-05:00
    title hfs Subsystem Stack-based Buffer Overflow Vulnerability
    version 8
redhat via4
advisories
  • bugzilla
    id 556406
    title kernel: r8169: straighten out overlength frame detection (improved) [rhel-4.9] [rhel-4.8.z]
    oval
    OR
    • comment Red Hat Enterprise Linux must be installed
      oval oval:com.redhat.rhba:tst:20070304026
    • AND
      • comment Red Hat Enterprise Linux 4 is installed
        oval oval:com.redhat.rhba:tst:20070304025
      • OR
        • comment kernel earlier than 0:2.6.9-89.0.20.EL is currently running
          oval oval:com.redhat.rhsa:tst:20100076023
        • comment kernel earlier than 0:2.6.9-89.0.20.EL is set to boot up on next boot
          oval oval:com.redhat.rhsa:tst:20100076024
      • OR
        • AND
          • comment kernel is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076001
          • comment kernel is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304002
        • AND
          • comment kernel-devel is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076003
          • comment kernel-devel is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304004
        • AND
          • comment kernel-doc is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076005
          • comment kernel-doc is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304006
        • AND
          • comment kernel-hugemem is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076007
          • comment kernel-hugemem is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304008
        • AND
          • comment kernel-hugemem-devel is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076009
          • comment kernel-hugemem-devel is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304010
        • AND
          • comment kernel-largesmp is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076011
          • comment kernel-largesmp is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304012
        • AND
          • comment kernel-largesmp-devel is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076013
          • comment kernel-largesmp-devel is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304014
        • AND
          • comment kernel-smp is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076015
          • comment kernel-smp is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304016
        • AND
          • comment kernel-smp-devel is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076017
          • comment kernel-smp-devel is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304018
        • AND
          • comment kernel-xenU is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076019
          • comment kernel-xenU is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304020
        • AND
          • comment kernel-xenU-devel is earlier than 0:2.6.9-89.0.20.EL
            oval oval:com.redhat.rhsa:tst:20100076021
          • comment kernel-xenU-devel is signed with Red Hat master key
            oval oval:com.redhat.rhba:tst:20070304022
    rhsa
    id RHSA-2010:0076
    released 2010-02-02
    severity Important
    title RHSA-2010:0076: kernel security and bug fix update (Important)
  • rhsa
    id RHSA-2010:0046
  • rhsa
    id RHSA-2010:0095
rpms
  • kernel-0:2.6.18-164.11.1.el5
  • kernel-PAE-0:2.6.18-164.11.1.el5
  • kernel-PAE-debuginfo-0:2.6.18-164.11.1.el5
  • kernel-PAE-devel-0:2.6.18-164.11.1.el5
  • kernel-debug-0:2.6.18-164.11.1.el5
  • kernel-debug-debuginfo-0:2.6.18-164.11.1.el5
  • kernel-debug-devel-0:2.6.18-164.11.1.el5
  • kernel-debuginfo-0:2.6.18-164.11.1.el5
  • kernel-debuginfo-common-0:2.6.18-164.11.1.el5
  • kernel-devel-0:2.6.18-164.11.1.el5
  • kernel-doc-0:2.6.18-164.11.1.el5
  • kernel-headers-0:2.6.18-164.11.1.el5
  • kernel-kdump-0:2.6.18-164.11.1.el5
  • kernel-kdump-debuginfo-0:2.6.18-164.11.1.el5
  • kernel-kdump-devel-0:2.6.18-164.11.1.el5
  • kernel-xen-0:2.6.18-164.11.1.el5
  • kernel-xen-debuginfo-0:2.6.18-164.11.1.el5
  • kernel-xen-devel-0:2.6.18-164.11.1.el5
  • kernel-0:2.6.9-89.0.20.EL
  • kernel-debuginfo-0:2.6.9-89.0.20.EL
  • kernel-devel-0:2.6.9-89.0.20.EL
  • kernel-doc-0:2.6.9-89.0.20.EL
  • kernel-hugemem-0:2.6.9-89.0.20.EL
  • kernel-hugemem-devel-0:2.6.9-89.0.20.EL
  • kernel-largesmp-0:2.6.9-89.0.20.EL
  • kernel-largesmp-devel-0:2.6.9-89.0.20.EL
  • kernel-smp-0:2.6.9-89.0.20.EL
  • kernel-smp-devel-0:2.6.9-89.0.20.EL
  • kernel-xenU-0:2.6.9-89.0.20.EL
  • kernel-xenU-devel-0:2.6.9-89.0.20.EL
refmap via4
confirm
debian DSA-2005
mlist
  • [linux-mm-commits] 20091203 + hfs-fix-a-potential-buffer-overflow.patch added to -mm tree
  • [oss-security] 20091204 CVE-2009-4020 kernel: hfs buffer overflow
secunia
  • 38276
  • 39742
suse
  • SUSE-SA:2010:005
  • SUSE-SA:2010:019
  • SUSE-SA:2010:023
statements via4
contributor Mark J Cox
lastmodified 2010-02-04
organization Red Hat
statement This issue did not affect the version of the Linux kernel as shipped with Red Hat Enterprise MRG as the affected driver is not enabled in this kernel. It was addressed in Red Hat Enterprise Linux 4 and 5 via https://rhn.redhat.com/errata/RHSA-2010-0076.html and https://rhn.redhat.com/errata/RHSA-2010-0046.html respectively. Red Hat Enterprise Linux 3 is now in Production 3 of the maintenance life-cycle, http://www.redhat.com/security/updates/errata, and this issue is rated as having low impact, therefore the fix for this issue is not currently planned to be included in the future updates.
Last major update 19-09-2017 - 01:29
Published 04-12-2009 - 21:30
Last modified 19-09-2017 - 01:29
Back to Top