ID CVE-2017-16611
Summary In libXfont before 1.5.4 and libXfont2 before 2.0.3, a local attacker can open (but not read) files on the system as root, triggering tape rewinds, watchdogs, or similar mechanisms that can be triggered by opening files.
References
Vulnerable Configurations
  • Debian Linux 8.0 (Jessie)
    cpe:2.3:o:debian:debian_linux:8.0
  • Debian Linux 9.0
    cpe:2.3:o:debian:debian_linux:9.0
  • Canonical Ubuntu Linux 14.04 LTS (Long-Term Support)
    cpe:2.3:o:canonical:ubuntu_linux:14.04:-:-:-:lts
  • Canonical Ubuntu Linux 16.04 LTS (Long-Term Support)
    cpe:2.3:o:canonical:ubuntu_linux:16.04:-:-:-:lts
  • Canonical Ubuntu Linux 17.04
    cpe:2.3:o:canonical:ubuntu_linux:17.04
  • Canonical Ubuntu Linux 17.10
    cpe:2.3:o:canonical:ubuntu_linux:17.10
  • X.Org LibXFont 1.1.0
    cpe:2.3:a:x:libxfont:1.1.0
  • X.Org LibXFont 1.2.0
    cpe:2.3:a:x:libxfont:1.2.0
  • X.Org LibXFont 1.2.1
    cpe:2.3:a:x:libxfont:1.2.1
  • X.Org LibXFont 1.2.2
    cpe:2.3:a:x:libxfont:1.2.2
  • X.Org LibXFont 1.2.3
    cpe:2.3:a:x:libxfont:1.2.3
  • X.Org LibXFont 1.2.4
    cpe:2.3:a:x:libxfont:1.2.4
  • X.Org LibXFont 1.2.5
    cpe:2.3:a:x:libxfont:1.2.5
  • X.Org LibXFont 1.2.6
    cpe:2.3:a:x:libxfont:1.2.6
  • X.Org LibXFont 1.2.7
    cpe:2.3:a:x:libxfont:1.2.7
  • X.Org LibXFont 1.2.8
    cpe:2.3:a:x:libxfont:1.2.8
  • X.Org LibXFont 1.2.9
    cpe:2.3:a:x:libxfont:1.2.9
  • X.Org LibXFont 1.3.0
    cpe:2.3:a:x:libxfont:1.3.0
  • X.Org LibXFont 1.3.1
    cpe:2.3:a:x:libxfont:1.3.1
  • X.Org LibXFont 1.3.2
    cpe:2.3:a:x:libxfont:1.3.2
  • X.Org LibXFont 1.3.3
    cpe:2.3:a:x:libxfont:1.3.3
  • X.Org LibXFont 1.3.4
    cpe:2.3:a:x:libxfont:1.3.4
  • X.Org LibXFont 1.4.0
    cpe:2.3:a:x:libxfont:1.4.0
  • X.Org LibXFont 1.4.1
    cpe:2.3:a:x:libxfont:1.4.1
  • X.Org LibXFont 1.4.2
    cpe:2.3:a:x:libxfont:1.4.2
  • X.Org LibXFont 1.4.3
    cpe:2.3:a:x:libxfont:1.4.3
  • X.Org LibXFont 1.4.4
    cpe:2.3:a:x:libxfont:1.4.4
  • X.Org LibXFont 1.4.5
    cpe:2.3:a:x:libxfont:1.4.5
  • X.Org LibXFont 1.4.6
    cpe:2.3:a:x:libxfont:1.4.6
  • X.Org LibXFont 1.4.7
    cpe:2.3:a:x:libxfont:1.4.7
  • X.Org LibXFont 1.4.99
    cpe:2.3:a:x:libxfont:1.4.99
  • X.Org LibXFont 1.4.99.901
    cpe:2.3:a:x:libxfont:1.4.99.901
CVSS
Base: 2.1
Impact:
Exploitability:
CWE CWE-59
CAPEC
  • Symlink Attack
    An attacker positions a symbolic link in such a manner that the targeted user or application accesses the link's endpoint, assuming that it is accessing a file with the link's name. The endpoint file may be either output or input. If the file is output, the result is that the endpoint is modified, instead of a file at the intended location. Modifications to the endpoint file may include appending, overwriting, corrupting, changing permissions, or other modifications. In some variants of this attack the attacker may be able to control the change to a file while in other cases they cannot. The former is especially damaging since the attacker may be able to grant themselves increased privileges or insert false information, but the latter can also be damaging as it can expose sensitive information or corrupt or destroy vital system or application files. Alternatively, the endpoint file may serve as input to the targeted application. This can be used to feed malformed input into the target or to cause the target to process different information, possibly allowing the attacker to control the actions of the target or to cause the target to expose information to the attacker. Moreover, the actions taken on the endpoint file are undertaken with the permissions of the targeted user or application, which may exceed the permissions that the attacker would normally have.
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
nessus via4
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-4F5A3E792F.NASL
    description Security fix for CVE-2017-16611 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-03-07
    plugin id 107164
    published 2018-03-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=107164
    title Fedora 27 : libXfont2 (2018-4f5a3e792f)
  • NASL family Slackware Local Security Checks
    NASL id SLACKWARE_SSA_2017-333-02.NASL
    description New libXfont packages are available for Slackware 13.0, 13.1, 13.37, 14.0, 14.1, and 14.2 to fix a security issue.
    last seen 2019-02-21
    modified 2018-01-26
    plugin id 104859
    published 2017-11-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104859
    title Slackware 13.0 / 13.1 / 13.37 / 14.0 / 14.1 / 14.2 : libXfont (SSA:2017-333-02)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_08A125F3E35A11E7A29354E1AD3D6335.NASL
    description the freedesktop.org project reports : A non-privileged X client can instruct X server running under root to open any file by creating own directory with 'fonts.dir', 'fonts.alias' or any font file being a symbolic link to any other file in the system. X server will then open it. This can be issue with special files such as /dev/watchdog.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 105335
    published 2017-12-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105335
    title FreeBSD : libXfont -- permission bypass when opening files through symlinks (08a125f3-e35a-11e7-a293-54e1ad3d6335)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-E27B435A7F.NASL
    description Security fix for CVE-2017-16611 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-03-07
    plugin id 107177
    published 2018-03-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=107177
    title Fedora 27 : libXfont (2018-e27b435a7f)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-05B078C373.NASL
    description Security fix for CVE-2017-16611 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-03-07
    plugin id 107154
    published 2018-03-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=107154
    title Fedora 26 : libXfont2 (2018-05b078c373)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2018-5A7CD68500.NASL
    description Security fix for CVE-2017-16611 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-03-07
    plugin id 107167
    published 2018-03-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=107167
    title Fedora 26 : libXfont (2018-5a7cd68500)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201801-10.NASL
    description The remote host is affected by the vulnerability described in GLSA-201801-10 (LibXfont, LibXfont2: Arbitrary file access) It was discovered that libXfont incorrectly followed symlinks when opening font files. Impact : A local unprivileged user could use this flaw to cause the X server to access arbitrary files, including special device files. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-01-26
    plugin id 105666
    published 2018-01-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105666
    title GLSA-201801-10 : LibXfont, LibXfont2: Arbitrary file access
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-3500-1.NASL
    description It was discovered that libXfont incorrectly followed symlinks when opening font files. A local unprivileged user could use this issue to cause the X server to access arbitrary files, including special device files. Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-01
    plugin id 104883
    published 2017-11-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104883
    title Ubuntu 14.04 LTS / 16.04 LTS / 17.04 / 17.10 : libxfont, libxfont1, libxfont2 vulnerability (USN-3500-1)
refmap via4
confirm https://bugzilla.suse.com/show_bug.cgi?id=1050459
gentoo GLSA-201801-10
misc http://security.cucumberlinux.com/security/details.php?id=155
mlist
  • [freedesktop-xorg-announce] 20171128 libXfont 1.5.4
  • [freedesktop-xorg-announce] 20171128 libXfont2 2.0.3
  • [oss-security] 20171128 CVE-2017-16611 libXfont Open files with O_NOFOLLOW
ubuntu USN-3500-1
Last major update 01-12-2017 - 12:29
Published 01-12-2017 - 12:29
Last modified 02-10-2019 - 20:03
Back to Top