ID CVE-2016-3075
Summary Stack-based buffer overflow in the nss_dns implementation of the getnetbyname function in GNU C Library (aka glibc) before 2.24 allows context-dependent attackers to cause a denial of service (stack consumption and application crash) via a long name.
Vulnerable Configurations
  • Novell openSUSE 13.2
  • GNU glibc 2.23
  • Fedora Project Fedora 23
  • Canonical Ubuntu Linux 12.04 LTS
  • Canonical Ubuntu Linux 14.04 LTS (Long-Term Support)
  • Canonical Ubuntu Linux 15.10
Base: 5.0 (as of 14-06-2016 - 10:07)
  • 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.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker 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 attackers' choice.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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 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 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 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 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.
redhat via4
id 1346397
title glibc: debug/tst-longjump_chk2 calls printf from a signal handler
  • OR
    • comment Red Hat Enterprise Linux 7 Client is installed
      oval oval:com.redhat.rhsa:tst:20140675001
    • comment Red Hat Enterprise Linux 7 Server is installed
      oval oval:com.redhat.rhsa:tst:20140675002
    • comment Red Hat Enterprise Linux 7 Workstation is installed
      oval oval:com.redhat.rhsa:tst:20140675003
    • comment Red Hat Enterprise Linux 7 ComputeNode is installed
      oval oval:com.redhat.rhsa:tst:20140675004
  • OR
    • AND
      • comment glibc is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573015
      • comment glibc is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872006
    • AND
      • comment glibc-common is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573011
      • comment glibc-common is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872012
    • AND
      • comment glibc-devel is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573007
      • comment glibc-devel is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872018
    • AND
      • comment glibc-headers is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573017
      • comment glibc-headers is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872010
    • AND
      • comment glibc-static is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573013
      • comment glibc-static is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872008
    • AND
      • comment glibc-utils is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573005
      • comment glibc-utils is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872014
    • AND
      • comment nscd is earlier than 0:2.17-157.el7
        oval oval:com.redhat.rhsa:tst:20162573009
      • comment nscd is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20100872016
id RHSA-2016:2573
released 2016-11-03
severity Low
title RHSA-2016:2573: glibc security, bug fix, and enhancement update (Low)
  • glibc-0:2.17-157.el7
  • glibc-common-0:2.17-157.el7
  • glibc-devel-0:2.17-157.el7
  • glibc-headers-0:2.17-157.el7
  • glibc-static-0:2.17-157.el7
  • glibc-utils-0:2.17-157.el7
  • nscd-0:2.17-157.el7
refmap via4
bid 85732
fedora FEDORA-2016-68abc0be35
gentoo GLSA-201702-11
  • openSUSE-SU-2016:1527
  • openSUSE-SU-2016:1779
ubuntu USN-2985-1
Last major update 28-11-2016 - 15:06
Published 01-06-2016 - 16:59
Last modified 30-06-2017 - 21:29
Back to Top